xoxo-brainstorming

XOXO brainstorming

Authors

• Tantek Çelik
• DimitriGlazkov

Example Uses

XOXO Lists and outlines are used for numerous special purposes across the web. This section is here to document both best practices and recommendations.

Blogrolls

Background: See L.M. Orchard's post "Subscriptions Are Attention But What About Blogrolls".

Nearly all blogrolls are already published as XOXO on blog, but there is no obvious way to distinguish the XOXO blogroll from other lists in the content/header/footer of the blog.

XOXO standardizes (see xoxo-profile) the class name "blogroll" for blogroll lists. E.g.

<ul class="xoxo blogroll">
 <li><a href="...">...</a></li>
 <li><a href="...">...</a></li>
</ul>

Note that a blogroll is a superset of a subscription list.

Subscription information

Some blogrolls contain feed information -- it would be nice if XOXO blogrolls could capture this information also. This, in and of itself, would be a nice step up from OPML.

• An example of OPML to a XOXO list w/ expand/collapse folders

Possible XOXO blogs+feeds markup

Here is one example of how you could publish blogs+feeds in XOXO. Note that since a XOXO parser will only treat the first hyperlink as the info for the list item, the blog names and URLs will be parsed, and the feeds will be ignored. In reality, the blogs themselves should contain the necessary auto-discovery links to their own feeds, which is more reliable anyway.

<ul class="xoxo blogroll">
 <li>
  <a href="blogURL1">Blog Name 1</a>
  <a href=".../index.xml" rel="alternate" type="application/atom+xml">RSS</a>
 </li>
 <li>
  <a href="blogURL2">Blog Name 2</a>
  <a href=".../index.xml" rel="alternate" type="application/rss+xml">RSS</</a>
  <a href=".../index.atom" rel="alternate" type="application/atom+xml">Atom</a>
 </li>
</ul>

CSS styling could make this as pretty or not as desired.

See also blog-info-examples, blog-info-formats, blog-info-brainstorming, XOXO Blogroll Format

Wishlists

Background: See L.M. Orchard's post: "I wish it were in XOXO"

Similar to blogrolls, what if we used the class name "wishlist"?

What are the distinguishing features of wishlists?

Is a wishlist item the same as a listing that is looking for an item? See: listing-examples, listing-formats, listing-brainstorming

Tagged Links

This one seems easier, because you could simply use a list of xFolk items, which is recognizable.

Alternatively we could also use the class name "linkroll".

But how far can we successfully take that method (of adding a new class name for each specific use of XOXO) scale and continue workng?

Parsing Properties

• From HTML spec, the content of both dl, and li can contain block or inline elements.
  • this implies that special properties can include markup.
  • naturally, url, type, and rel properties don't fit into this rule logically, but that's a reasonable exception.
• First a element specifies text, url, title, type and rel properties
  • If these properties are also defined using dl, they:
    • a. override values, specified in hyperlink
    • b. are ignored -- I (DimitriGlazkov) am leaning toward this choice
• First dl is treated as a special property set
  • how to escape in case dl is content, not property set?
    • possibly like this:

<ul>
	<li>
		<dl>
			<a href="http://microformats.org">Microformats</a>
			<dt>text</dt>
			<dd>XOXO</dd>
		</dl>
	</li>
</ul>

Based on preliminary research, all parsers mentioned in xoxo-sample-code use property bag or dictionary to collect properties, which means that last value specified wins (overrides previously specified). This means that this bit of markup:

<ul>
	<li>
		<dl>
			<a href="http://microformats.org">Microformats</a>
			<dt>text</dt>
			<dd>XOXO</dd>
	</li>
</ul>

Will parse the value of text property as XOXO, not Microformats. Not sure yet whether this this th _right thing_.