XOXO (A Semantic Weblog)
Posted on
Please note that no template is ever 100% hAtom compatible on Blogger. There are those that come really close, but datetime-design-pattern dates cannot be generated on Blogger and thus the ‘updated’ field is always invalid.
Posted on
It seems that another feedreading project is recognising XOXO! According to this post Plagger has, if I understand correctly, added the ability to import subscriptions from an XOXO reading list and also to export that as OPML. Not recognising XOXO enough to provide an export mechanism for it yet, but a step forward nevertheless!
Posted on
Standard RSS is a tool which takes any RSS, ATOM, hAtom, or XOXO Blog Format feed and turns it into a standard RSS 2.0 core. More information is available on the tool’s home page. There is also a YubNub command to go with it.
Posted on
A reading list is the organised list of all feeds that a person reads using their feed reader. There are two primary file formats for reading lists, XOXO and OPML (see What is XOXO?). Reading lists are popularly used as an import/export format for moving subscriptions between feed readers. If they are made available online they can also be used as dynamic reading lists.
Dynamic reading lists are reading lists that are aggregated by a feed reader. One folder or module is always updated to contain the most current subscriptions from the reading list. This allows users to subscribe to other users’ reading lists to see what other’s are reading, for example. Directory sites like Share Your OPML (which, as the name indicates, is anti-XOXO) also allow users to share their subscriptions en masse.
Feed readers currently supporting the dynamic reading list concept are:
Dynamic reading lists can be previewed or included as a widget in a webpage using Grazr. Grazr currently only supports OPML, but XOXO is on the todo list.
If you know of any other programs that support dynamic reading lists or other interesting uses for reading lists, please leave a comment below.
If you have any suggestions on how this introduction to reading lists could be clarified, please leave a comment below.
Posted on
If you combine S5 with XOXO you get a format you can use to build simple slideshows for the internet and that makes sense to microformats parsers. S5 is a simple slideshow system with many features that can pull the data for slides right out of an XOXO block. To use S5 you will have to download the JavaScript and CSS files from the homepage and then build a page with slide content that links in these files. While there is a quite adequate S5-with-XOXO reference, the format will be summarised here for completeness.
Notes
S5 documents must be DOCTYPE XHTML 1.0 Strict, and there are certain <meta> tags that are required. See the specification for more details.
Meta Data
Meta data in S5 is encapsulated in a set of <meta> tags. This means that the data will not be available to XOXO-only processors. The page <title> must be the title of the presentation and the <meta name=”version” content=”S5 1.1″ /> element is also required, along with the tags to include the JavaScript and basic CSS.
There is also a controls/header/footer section that must be present first in the <body> tag before the XOXO data. The code for this section follows:
Where SLIDESHOW HEADER and SLIDESHOW FOOTER are the contents for the header and footer of the slideshow, respectively.
Classes
In order for the S5 code to interface with your data properly the class ‘presentation’ must be present on the main <ol> or <ul> tag. The class ‘xoxo’ is also reccomended in accordance with the XOXO specification.
Nodes
Each root node in the XOXO tree for the slides must have the class ‘slide’. The direct contents of the node (along with any XHTML markup) are considered to be the text (/images etc.) of the slide. If the first element in the node is an <h1> element the contents of that tag are considred the title of the slide. Subnodes are rendered as points in the presentation. If the <ul> or <ol> root tag for the subpoints has the class ‘incremental’ the points will be introduced one at a time. Additionally a <div> element of class ‘handout’ will not be rendered on-screen but only when the presentation is printed.