From Microformats Wiki
Revision as of 10:44, 14 January 2008 by AndyMabbett (talk | contribs) ({{issues-format}})
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

XOXO Issues


Add new issues to the *bottom* of this list.

  • 2005-06-21 raised by Hixie
    1. Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how XOXO documents must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
  • 2006-10-11 raised by MikeSchinkel
    1. I don't understand what benefits xoxo provides. Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. MikeSchinkel 21:30, 11 Oct 2006 (PDT)
  • 2007-01-13 raised by Premasagar
    1. I also do not quite understand the dividing line between a bog-standard HTML list and a xoxo list. What is the defining difference? Premasagar
  • 2007-08-07 raised by User:Tantek and User:Kevin_Marks (originally raised sometime in 2005 or 2006, but captured 2007-08-07).
    • [11:31am] KevinMarks: Tantek and I had a big unresolved debate about this a long time ago, involving more 'special' elements to preserve ordered/unordered status
    • [11:31am] KevinMarks: for the ul vs ol distinction
    • [11:31am] tantek: I believe it was the user/web-designer/publisher perspective vs. the scripting-language data-structure perspective.
    • e.g. web designer / HTML / POSH perspective, vs. JSON perspective.


Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2

see also