Microformats Wiki - User contributions [en]

group-brainstorming

2006-07-14T14:38:52Z

Josh: /* Real World Examples */

= Group Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]
* [http://tantek.com/ Tantek Çelik]

== Problem ==

See [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original thoughts] on microformats-discuss.

Not every page belongs to one user. We need a microformat to define a group of people.

There are two distinct problems here though.

The problem that Chris's proposal describes is actually just one of tagging. By tagging people with the same tag, you "place" them into a group as defined by that tag. That's the model presented by Chris's ASCII art diagram.

The simpler problem to solve is perhaps the Group equivalent of [http://gmpg.org/xfn/ XFN]

How does a person indicate that they belong to of a group?

How does a group indicate that a person is a member of that group?

== Purposed Structure ==

From [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original post]

--Group Name
| Description
| Tags
|
+--+ Members
| |
| +-- Member 1 (hcard)
| |
| +-- Member 2 (hcard)
|
+--+ Pool
|
+--+ Topic
|
+-- Post 1 (hatom)
|
+-- Post 2 (hatom)

This model is totally overdesigned. A groups microformat should start as simple as possible, meaning, nothing but the idea of a group and members. That's the 80% in common case across various systems. People in a group. A group with people. Nothing more. -Tantek

<s>Add optional roles. Groups may have "admins", "moderators", or "members". Or if you were marking up a contributes page, you could have "programmers", "designers", etc.</s> Is this what you mean by tags? - Josh

No, those are roles. I mean the very *name* of a group could be interpreted simply as a tag on a person.

For example a named group of bookmarks are nothing more than a tag that all those bookmarks share.

Any taxonomy of group roles (admins, moderators, etc.) should be postponed.

-Tantek

To keep it simple, could we say that hGroup is just a container for other microformats. That would cover members (hcards) and topics (atom). - Josh

No. Both (a) naming and (b) proposing a structure (container) are both premature for a microformat, until the proper research has been done and documented on the wiki. Please follow the [[process]].

-Tantek

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.
* [http://ma.gnolia.com/groups/microformats Ma.gnolia Groups]
* [http://flickr.com/groups/microformats/ Flickr Groups]
* [http://forum.textdrive.com/userlist.php Forum Userlists]
* [http://groups.myspace.com/index.cfm?fuseaction=groups.categories Myspace Groups]

== Possible Implementations ==

Groups could define there members on their own homepage. Social web sites could pick up the group list from the groups site instead. You'd instantly have your group on every (dreaming) social web service.

== See Also ==
* [[hcard]]
* [http://gmpg.org/xfn/ XFN]

group-brainstorming

2006-07-14T14:36:40Z

Josh: /* Real World Examples */

= Group Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]
* [http://tantek.com/ Tantek Çelik]

== Problem ==

See [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original thoughts] on microformats-discuss.

Not every page belongs to one user. We need a microformat to define a group of people.

There are two distinct problems here though.

The problem that Chris's proposal describes is actually just one of tagging. By tagging people with the same tag, you "place" them into a group as defined by that tag. That's the model presented by Chris's ASCII art diagram.

The simpler problem to solve is perhaps the Group equivalent of [http://gmpg.org/xfn/ XFN]

How does a person indicate that they belong to of a group?

How does a group indicate that a person is a member of that group?

== Purposed Structure ==

From [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original post]

--Group Name
| Description
| Tags
|
+--+ Members
| |
| +-- Member 1 (hcard)
| |
| +-- Member 2 (hcard)
|
+--+ Pool
|
+--+ Topic
|
+-- Post 1 (hatom)
|
+-- Post 2 (hatom)

This model is totally overdesigned. A groups microformat should start as simple as possible, meaning, nothing but the idea of a group and members. That's the 80% in common case across various systems. People in a group. A group with people. Nothing more. -Tantek

<s>Add optional roles. Groups may have "admins", "moderators", or "members". Or if you were marking up a contributes page, you could have "programmers", "designers", etc.</s> Is this what you mean by tags? - Josh

No, those are roles. I mean the very *name* of a group could be interpreted simply as a tag on a person.

For example a named group of bookmarks are nothing more than a tag that all those bookmarks share.

Any taxonomy of group roles (admins, moderators, etc.) should be postponed.

-Tantek

To keep it simple, could we say that hGroup is just a container for other microformats. That would cover members (hcards) and topics (atom). - Josh

No. Both (a) naming and (b) proposing a structure (container) are both premature for a microformat, until the proper research has been done and documented on the wiki. Please follow the [[process]].

-Tantek

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.
* [http://ma.gnolia.com/groups/microformats Ma.gnolia Groups]
* [http://flickr.com/groups/microformats/ Flickr Groups]
* [http://forum.textdrive.com/userlist.php Forum Userlists]

== Possible Implementations ==

Groups could define there members on their own homepage. Social web sites could pick up the group list from the groups site instead. You'd instantly have your group on every (dreaming) social web service.

== See Also ==
* [[hcard]]
* [http://gmpg.org/xfn/ XFN]

group-brainstorming

2006-07-14T05:21:07Z

Josh: /* Purposed Structure */

= Group Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]
* [http://tantek.com/ Tantek Çelik]

== Problem ==

See [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original thoughts] on microformats-discuss.

Not every page belongs to one user. We need a microformat to define a group of people.

There are two distinct problems here though.

The problem that Chris's proposal describes is actually just one of tagging. By tagging people with the same tag, you "place" them into a group as defined by that tag. That's the model presented by Chris's ASCII art diagram.

The simpler problem to solve is perhaps the Group equivalent of [http://gmpg.org/xfn/ XFN]

How does a person indicate that they belong to of a group?

How does a group indicate that a person is a member of that group?

== Purposed Structure ==

From [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original post]

--Group Name
| Description
| Tags
|
+--+ Members
| |
| +-- Member 1 (hcard)
| |
| +-- Member 2 (hcard)
|
+--+ Pool
|
+--+ Topic
|
+-- Post 1 (hatom)
|
+-- Post 2 (hatom)

This model is totally overdesigned. A groups microformat should start as simple as possible, meaning, nothing but the idea of a group and members. That's the 80% in common case across various systems. People in a group. A group with people. Nothing more. -Tantek

<s>Add optional roles. Groups may have "admins", "moderators", or "members". Or if you were marking up a contributes page, you could have "programmers", "designers", etc.</s> Is this what you mean by tags? - Josh

No, those are roles. I mean the very *name* of a group could be interpreted simply as a tag on a person.

For example a named group of bookmarks are nothing more than a tag that all those bookmarks share.

Any taxonomy of group roles (admins, moderators, etc.) should be postponed.

-Tantek

To keep it simple, could we say that hGroup is just a container for other microformats. That would cover members (hcards) and topics (atom). - Josh

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.
* [http://ma.gnolia.com/groups/microformats Ma.gnolia Groups]
* [http://flickr.com/groups/microformats/ Flickr Groups]

== Possible Implementations ==

Groups could define there members on their own homepage. Social web sites could pick up the group list from the groups site instead. You'd instantly have your group on every (dreaming) social web service.

== See Also ==
* [[hcard]]
* [http://gmpg.org/xfn/ XFN]

group-brainstorming

2006-07-14T05:10:09Z

Josh: /* Purposed Structure */

= Group Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]
* [http://tantek.com/ Tantek Çelik]

== Problem ==

See [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original thoughts] on microformats-discuss.

Not every page belongs to one user. We need a microformat to define a group of people.

There are two distinct problems here though.

The problem that Chris's proposal describes is actually just one of tagging. By tagging people with the same tag, you "place" them into a group as defined by that tag. That's the model presented by Chris's ASCII art diagram.

The simpler problem to solve is perhaps the Group equivalent of [http://gmpg.org/xfn/ XFN]

How does a person indicate that they belong to of a group?

How does a group indicate that a person is a member of that group?

== Purposed Structure ==

From [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Chris Messina's original post]

--Group Name
| Description
| Tags
|
+--+ Members
| |
| +-- Member 1 (hcard)
| |
| +-- Member 2 (hcard)
|
+--+ Pool
|
+--+ Topic
|
+-- Post 1 (hatom)
|
+-- Post 2 (hatom)

This model is totally overdesigned. A groups microformat should start as simple as possible, meaning, nothing but the idea of a group and members. That's the 80% in common case across various systems. People in a group. A group with people. Nothing more. -Tantek

<s>Add optional roles. Groups may have "admins", "moderators", or "members". Or if you were marking up a contributes page, you could have "programmers", "designers", etc.</s> Is this what you mean by tags? - Josh

No, those are roles. I mean the very *name* of a group could be interpreted simply as a tag on a person.

For example a named group of bookmarks are nothing more than a tag that all those bookmarks share.

Any taxonomy of group roles (admins, moderators, etc.) should be postponed.

-Tantek

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.
* [http://ma.gnolia.com/groups/microformats Ma.gnolia Groups]
* [http://flickr.com/groups/microformats/ Flickr Groups]

== Possible Implementations ==

Groups could define there members on their own homepage. Social web sites could pick up the group list from the groups site instead. You'd instantly have your group on every (dreaming) social web service.

== See Also ==
* [[hcard]]
* [http://gmpg.org/xfn/ XFN]

group-brainstorming

2006-07-14T04:30:19Z

Josh: /* Purposed Structure */

group-brainstorming

2006-07-14T04:17:14Z

Josh: /* Possible Implementations */

group-brainstorming

2006-07-14T04:13:59Z

Josh: /* Group Brainstorming */

group-brainstorming

2006-07-14T04:11:23Z

Josh: /* Purposed Structure */

group-brainstorming

2006-07-14T04:08:37Z

Josh: /* Purposed Structure */

group-brainstorming

2006-07-14T04:08:11Z

Josh: /* Purposed Structure */

group-brainstorming

2006-07-14T04:06:58Z

Josh: /* Group Brainstorming */

group-brainstorming

2006-07-14T04:02:07Z

Josh: /* Real World Examples */

= Attention Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]

== Problem ==

Not every page belongs to one user. We need a microformat to define a group of people.

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.
* [http://ma.gnolia.com/groups/microformats Ma.gnolia Groups]
* [http://flickr.com/groups/microformats/ Flickr Groups]

== See Also ==
* [[hcard]]
* [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Original proposal] on microformats-discuss.

group-brainstorming

2006-07-14T03:58:21Z

Josh: /* Real World Examples */

= Attention Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]

== Problem ==

Not every page belongs to one user. We need a microformat to define a group of people.

== Real World Examples ==

* [http://microformats.org/about/people/ microformats | People] - Contributers to a project should be marked up.

== See Also ==
* [[hcard]]
* [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Original proposal] on microformats-discuss.

group-brainstorming

2006-07-14T03:55:59Z

Josh: /* Attention Brainstorming */

group-brainstorming

2006-07-14T03:55:11Z

Josh: /* Attention Brainstorming */

group-brainstorming

2006-07-14T03:54:57Z

Josh: /* Attention Brainstorming */

User:Josh

2006-07-14T03:52:36Z

Josh: /* Josh Peek */

==Josh Peek==

I think I broke the rules by making my username just my first name.

* [http://claimid.com/josh claimID profile]
* [http://joshpeek.com/ Website]

User:Josh

2006-07-14T03:52:12Z

Josh:

==Josh Peek==

I think I broke the rules by making my username just my first name.

[http://claimid.com/josh claimID profile]
[http://joshpeek.com/ Website]

group-brainstorming

2006-07-14T03:50:20Z

Josh: /* Authors */

= Attention Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a Groups microformat.

== Authors ==

* [[User:ChrisMessina | Chris Messina]]
* [[User:Josh | Josh Peek]]

== See Also ==
* [[hcard]]
* [http://microformats.org/discuss/mail/microformats-discuss/2006-February/003181.html Original proposal] on microformats-discuss.

parsing-microformats

2006-07-08T05:14:42Z

Josh: /* XSLT example */

= Microformat Parsing =

Microformat parsing mechanisms that depend on documents having even minimal xml properties like well-formedness may fail when consuming non-well-formed content. [http://tidy.sourceforge.net/ Tidy] or even better [http://people.apache.org/~andyc/neko/doc/html/ CyberNeko] may be a useful work around.
In particular [http://suda.co.uk/projects/X2V/ Brian Suda's frequently cited X2V hCard and hCalendar discovery and transformation prototypes] use XSLT, and "tidy" any non-well-formed input before processing it.

Most microformats tend to be agnostic about things like exact element type used.

Developers can use tools like XPATH that assume well-formedness on well-formed content (from the web or by using tidy). Mark Pilgrim's example [http://sourceforge.net/projects/feedparser/ universal feed parser] suggests that it may be possible to sanitize user html to an extent that it is suitable for later processing as xml.

== Parsing class values ==

When parsing class values care must be taken:
# Class attributes may contain multiple class names, e.g: <code>class="foo vcard bar"</code>
# Class attributes may contain class names which contain the class name used by a microformat, e.g: <code>class="foovcardbar"</code> <code>class="foovcard"</code>, <code>class="vcardbar"</code>.
# Multiple class names are seperated by one or more whitespace charchters.
# Class names are case sensitive.

See http://www.w3.org/TR/html401/struct/global.html#h-7.5.2.

=== JavaScript example ===

<code>
if (elemenent.className.match(/\bvcard\b/)) ...
</code>

=== XSLT example ===
<code>
<xsl:if test="contains(
concat (
' ',
concat(normalize-whitespace(@class),' ')
),
' vcard '
)" > ...
</code>

[http://balloon.hobix.com/xpath-generator xpath generator], to help you generate those long ugly xpath queries.

== Parsing rel/rev values ==

Parsing rel and rev values is similar to parsing class values except for the following differences:

# rel and rev values should be seperated by one space.
# rel and rev values are case insensetive.

See http://www.w3.org/TR/html401/types.html#type-links.

== See Also ==

* [[xmdp-brainstorming]]

xfn-implementations

2006-07-08T01:58:05Z

Josh: /* XFN Implementations */

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the top of this list.

* [http://xfngraph.sourceforge.net XFN Graph] — a multi-platform Java-based tool which creates spider diagrams of XFN relationships from any given starting URL.

* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.

* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].

* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.

* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.

* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.

* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.

* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])

* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.

* [http://xfnsearch.joshpeek.com/ XFN Search]

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]

xoxo

2006-07-05T16:45:59Z

Josh: /* Implementations */

<h1> XOXO 1.0: Extensible Open XHTML Outlines </h1>

XOXO is a simple, open outline format written in standard XHTML and suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. XOXO is one of several [[microformats|microformat]] open standards.

__TOC__

== Draft Specification 2004-10-01 ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== Authors ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc] (formerly of [http://microsoft.com/ Microsoft Corporation])
* [http://diveintomark.org/ Mark Pilgrim], [http://ibm.com IBM]
* [http://www.blogologue.com/ Morten W. Petersen]

=== Copyright ===
{{MicroFormatCopyrightStatement2003}}

=== Patents ===
{{MicroFormatPatentStatement}}

== Preamble ==
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.

=== Name ===
XOXO stands for eXtensible Open XHTML Outlines, and is pronounced variously as 'ecks oh ecks oh', 'zho-zho', or 'sho-sho'.

== Abstract ==
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.

== The XOXO Document Type ==
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".

[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]
body, head, html, title
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]
a
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]
dl, dt, dd, ol, ul, li
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]
meta
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]
style element
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]
style attribute
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]
link
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]
Attribute compact on ol and ul

=== The XOXO Profile ===

See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.

== Simple XOXO Fragment ==

=== Markup ===

<pre><nowiki><ol class='xoxo'>
<li>Subject 1
<ol>
<li>subpoint a</li>
<li>subpoint b</li>
</ol>
</li>
<li>Subject 2
<ol compact="compact">
<li>subpoint c</li>
<li>subpoint d</li>
</ol>
</li>
<li>Subject 3
<ol>
<li>subpoint e</li>
</ol>
</li>
</ol>
</nowiki></pre>

=== Sample Rendering ===
<pre><nowiki>
1. Subject 1
a. subpoint a
b. subpoint b
2. Subject 2
3. Subject 3
a. subpoint e
</nowiki></pre>
=== Usage of 'compact' attribute ===

Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.

=== Possible Default Style Rules for Sample Rendering ===

<pre><nowiki>
ol.xoxo { list-style:decimal; }
ol.xoxo ol { list-style:lower-latin; }
ol[compact="compact"] { display:none; }
</nowiki></pre>

== More Simple Examples ==

MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:

* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".

== Properties of Outline Items ==
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:
* text
* description
* url (often called xmlurl or htmlurl; sometimes called permalink)
* title
* type (hint of the MIME type of the resource indicated by the URL)

In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki><ul></nowiki></code>, or <code><li></code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).

<pre><nowiki>
<ol class='xoxo'>
<li>item 1
<dl>
<dt>description</dt>
<dd>This item represents the main point we're trying to make.</dd>
</dl>
<ol>
<li>subpoint a</li>
<li>subpoint b</li>
</ol>
</li>
</nowiki></pre>

=== Special Properties ===
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:
* text, url, title, type, and rel (short for relationship)

If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:

Example for the sake of discussion only / not a canonical XOXO example:

<pre><nowiki>
<ol class='xoxo'>
<li>
<dl>
<dt>text</dt>
<dd>item 1</dd>
<dt>description</dt>
<dd> This item represents the main point we're trying to make.</dd>
<dt>url</dt>
<dd>http://example.com/more.xoxo</dd>
<dt>title</dt>
<dd>title of item 1</dd>
<dt>type</dt>
<dd>text/xml</dd>
<dt>rel</dt>
<dd>help</dd>
</dl>
</li>
</nowiki></pre>

However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki><li></nowiki></code>.

Actual XOXO Example:

<pre><nowiki>
<ol class='xoxo'>
<li><a href="http://example.com/more.xoxo"
title="title of item 1"
type="text/xml"
rel="help">item 1</a>

<dl>
<dt>description</dt>
<dd>This item represents the main point we're trying to make.</dd>
</dl>
</li>
</nowiki></pre>

Any other properties are simply added to the definition list in the same way as the "description" property.

== Publishing XOXO ==

XOXO may be published in two forms, valid XHTML, and simple well-formed XML.

=== Valid XHTML XOXO ===

A valid XHTML XOXO page is a complete XHTML document.

<pre><nowiki>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>XOXO page</title>
</head>
<body>
<ol class="xoxo">
<li><a href="URL-one">TEXT-one</a</li>
<li><a href="URL-two">TEXT-two</a></li>
...
</ol>
</body>
</html>
</nowiki></pre>

==== Content-Type ====

Valid XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.

<pre><nowiki>
Content-Type: text/html; charset=utf-8
</nowiki></pre>

It MUST be served with one of these Content-Type headers:

<pre><nowiki>
Content-Type: text/html; charset=utf-8
Content-Type: application/xhtml+xml
</nowiki></pre>

=== Simple well-formed XML XOXO ===

The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].

<pre><nowiki>
<ol class="xoxo">
<li><a href="URL-one">TEXT-one</a</li>
<li><a href="URL-two">TEXT-two</a></li>
...
</ol>
</nowiki></pre>

==== Content-Type ====

Simple well-formed XML XOXO SHOULD be served with this Content-Type header:
<pre><nowiki>
Content-Type: text/xml; charset=utf-8
</nowiki></pre>

It MUST be served with one of these Content-Type headers:

<pre><nowiki>
Content-Type: text/xml; charset=utf-8
Content-Type: application/xml
Content-Type: application/xml; charset=utf-8
</nowiki></pre>

== Examples in the Wild ==
This section is '''informative'''.

Too numerous to document thoroughly. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile.

== Implementations ==
This section is '''informative'''.

* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]
* [http://techno-weenie.net/blog/main/261/if-i-had-a-tumblelog single line of rails to convert XOXO to HTML]

=== Sample Code ===

* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.

== XOXO Schemas ==
This section is informative.

Note: these may be out of date and require updating to reflect the use of <dl> for annotating XOXO items with arbitrary properties.
* [[DTDs]]
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]

== References ==
=== Normative References ===
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]
* [http://gmpg.org/xmdp/ XMDP]
* [http://gmpg.org/xfn/ XFN]

=== Informative References ===
This section is '''informative'''.
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[VoteLinks]]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://opml.scripting.com/spec OPML 1.0]
* Contributed from http://developers.technorati.com/wiki/XOXO

=== Similar Work ===
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)

=== Related Reading ===
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].
* [http://raybenchen.blogspot.com/2005/11/is-crappy-format-worth-saving.html Dr. Tao Chen on why it is better to use XOXO than OPML going forward]

=== Unrelated Reading ===
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.

=== Promotional Materials / Schwag ===
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].

== Discussions ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to XOXO:

* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
** [http://blogxoxo.blogspot.com/ XOXO Blog]

=== Q&A ===
* If you have any questions about XOXO, check the [[xoxo-faq]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[xoxo-issues]] document.

User:Josh

2006-06-19T19:28:39Z

Josh: Added Josh's claimID profile

[http://claimid.com/josh claimID profile]

xfn-implementations

2006-06-19T19:27:19Z

Josh: /* XFN Implementations */

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the top of this list.

* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.

* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].

* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.

* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.

* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.

* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.

* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])

* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.

* [http://xaddemo.joshpeek.com/ XFN Auto Discover (XAD) Demo]

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]

xfn-implementations

2006-06-19T19:26:53Z

Josh: /* XFN Implementations */

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the top of this list.

* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.

* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].

* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.

* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.

* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.

* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.

* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])

* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.

* [http://xaddemo.joshpeek.com/ XFN Auto Discover (XAD) Demo]

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]