- 1 WebOrganics Talk
- 2 hCollection
- 3 hSpiff
WebOrganics talk is a page where I explore my ideas, you could call this a study page a brainstorm on my own. Anything I put here is not part of any microformats process and not to be regarded as such. Please feel free to email me any comments, criticism, changes that could work better or make more sense, or just to tell me that I am wrong :)
you can download a vcard at the bottom of this page
10 meaningful words
Martin McEvoy WebOrganics 07:47, 12 May 2007 (PDT)
To display visible Keywords similar to invisible Keywords that an author would place in the head of their document e.g
<meta name="keywords" content="your keywords,go here,separated by a comma,but not a space" />
I'm not putting my keywords in the head of the document but in another largely ignored part of a website the footer.
The Idea is to tag your website or blog with 10 meaningful words about your website or more precisely descriptive words about the things that relate to your website the most. A similar idea is used when you are asked to tag your blog when you add a new blog to technorati.
The hope is that if you type these 10 keywords into a search engine or directory then the result will be your website.
Example this is what my website WebOrganics has in the footer:
<ol class="xoxo"> <li> <dl> <dt>10 <a href="http://tantek.com/presentations/2005/09/elements-of-xhtml/">Meaningful</a> Words</dt> <dd class="info"> <a href="http://www.w3.org/2001/sw/" rel="tag">Semantic</a> <a href="http://www.molly.com/2005/11/14/web-standards-and-the-new-professionalism/" rel="tag">Standards</a> <a href="http://www.w3.org/WAI/gettingstarted/Overview.html" rel="tag">Accessibility</a> <a href="http://en.wikipedia.org/wiki/Implementation" rel="tag">Implementation</a> <a href="http://microformats.org/wiki/introduction" rel="tag">Microformats</a> <a href="http://www.adammathes.com/academic/computer-mediated-communication/folksonomies.html" rel="tag">Folksonomy</a> <a href="http://www.rubyonrails.org/" rel="tag">Rails</a> <a href="http://en.wikipedia.org/wiki/Open-source_software" rel="tag">Open</a> <a href="http://en.wikipedia.org/wiki/Organic_search_engine" rel="tag">Organic</a> <a href="http://en.wikipedia.org/wiki/Universal_design" rel="tag">Universal</a> </dd> </dl> </li> </ol>
I have a visible maybe new microformat meaningful in my <dt> tag my description term also a link to an article that explains this , the <a> tag's have similar links to my keywords, all the <a> atributes are paired with the rel="tag" microformat, the idea is that this is simple.
Does it work?
search these 10 keywords. Semantic Standards Accessibility Implementation Microformats Folksonomy Rails Open Organic Universal
- Meaningful words mean something!... do they?
- A good use would be in Tag Clouds
- Can people be taged in a similar way? rel="meaningful" XFN
- Maybe its just a good example of posh in action.
I know the evidence is un-conclusive but it is something to think about eh...
Martin McEvoy WebOrganics 12:05, 13 May 2007 (GMT)
Using DC CD AP Terms to describe a collection.
- hcollection, the root of the collection (dc:collection)
- id attribute, is used as a physical id of a collection
- title, the title of the collection (dc:title)
- type, what type of collection it is. (dc:type)
- url, a link to the collection using <a> with the class attribute "url" (dc:identifier *A URI for the collection*.)
<div class="hcollection" id="h"> <span class="type">Album</span>: <span class="title"> <a class="url" href="http://www.downloadpunk.com/?webaction=AlbumDetail&albumid=13202">Fifty Million People Can't Be Wrong</a> </span> </div>
<div class="hcollection" id="s"> <span class="title"> <span class="type"> <a class="url" href="http://Stamps.com...">Stamp Book</a> </span> </span> </div>
Add to collection
Add a Part to our collection terms are:
- part-of, this is the root element of our collection part. (dcterms:isPartOf)
- part-of-title, This is the collection part title
- part-of-type, what type of part it is.
- url, a link to the collection part with the class attribute "url".
- Class include using the Include Pattern, links the part to a collection
<span class="part-of"> <span class="part-of-type">Track</span> 1 <span class="part-of-title"><a class="url" href="http://track1...>Reason Ain't Our Long Suit</a> <a class="include" href="#h"></a> </span> </span>
Another Example: Minimal
<div class="part-of"> <span class="part-of-title">Penny Black</span> <span class"part-of-type">Stamp</span> <a class="include" href="#s"></a> </div>
hCollection seems to me very verbose I think that this may all be done by using just hcollection and part-of it would be much simpler to use, and easier to adopt.
this may be better to use:
<div class="hcollection" id="s">Stamp Book</div>
<a class="include part-of" href="s">A stamp</a>
does this work?...
- title is a common part of many Microformats, title may not be necessary.
- url is also a common part of many Microformats, url may not be necessary.
- class include has issues see here - Include pattern feedback
Martin McEvoy WebOrganics 08:48, 13 May 2007 (PDT)
Hypertext Shareable Playlist Format
hSpiff is Based on XSPF Version 1 XML Shareable Playlist Format ("spiff")
hSpiff is not intended to reflect hAtom which is used to describe blog posts but more specifically intended as a way to describe media and their order in a playlist.
hSpiff is intended to act as a transport for other media Microformats such as hAudio 0.3
 An XSPF playlist describes a sequence of objects to be rendered.
Objects might be audio, video, text, playlists, or any other media type.
The function of a playlist is to identify the objects and communicate their order.
 There is no XML format for playlists that can measure up to the standards of the formats for web pages (HTML), weblogs (RSS/Atom), and web graphs (RDF/XML). It is evident that there is a need, because XML is the preferred data description language of the moment and as a result the tools and skills to use it are ubiquitous.
A human-readable title for the playlist. xspf:playlist elements MAY contain exactly one.
Decided not to add the root class="playlist" as playlist is already defined with the prefix
Human-readable name of the entity (author, authors, group, company, etc) that authored the playlist. xspf:playlist elements MAY contain exactly one.
- 126.96.36.199.3 annotation
A human-readable comment on the playlist. This is character data, not HTML, and it may not contain markup. xspf:playlist elements MAY contain exactly one.
<div class="playlist-note">Text and html here only text will be phrased</div>
Remove this as playlist-title with class="url" serves the same purpose
URI of a web page to find out more about this playlist. Likely to be homepage of the author, and would be used to find out more about the author and to find more playlists by the author. xspf:playlist elements MAY contain exactly one.
Source URI for this playlist. xspf:playlist elements MAY contain exactly one.
<h1 class="playlist-title"><a class="url" href="http://yourweb.whatever/html">Title</a></h1>
Canonical ID for this playlist. Likely to be a hash or other location-independent name. MUST be a legal URI. xspf:playlist elements MAY contain exactly one.
<h1 class="playlist-title"><a id="album" class="url" href="http://yourweb.whatever/html">Title</a></h1>
URI of an image to display in the absence of a //playlist/trackList/image element. xspf:playlist elements MAY contain exactly one.
<img class="image" scr="http://yourweb.whatever/image/jpeg" />
class="photo" is more "microformaty"
Creation date (not last-modified date) of the playlist, formatted as a XML schema dateTime. xspf:playlist elements MAY contain exactly one.
<abbr class="playlist-date" title="2007-01-06">6th January, 2007</abbr>
-- Should this be an h2 tag? Semantic HTML indicates only one h1 tag per document. Maybe I'm barking up the wrong tree - I'm a microformats novice and perhaps this spec allows the use of h1, h2, h3 etc in this place. -- JChris
Semanticly Correct changed to h2 --Martin McEvoy
Canonical ID for this resource. Likely to be a hash or other location-independent name, such as a MusicBrainz identifier.
MUST be a legal URI. xspf:track elements MAY contain zero or more identifier elements.
<h2 class="track-title"><a class="track-url" href="http://yourweb.whatever/tracks/track1.mp3">Track</a></h2>
Human-readable name of the collection from which the resource which defines the duration of track rendering comes.
For a song originally published as a part of a CD or LP, this would be the title of the original release.
This value is primarily for fuzzy lookups, though a user-agent may display it. xspf:track elements MAY contain exactly one.
<a class="include" href="#album"></a>
Class include using the Include Pattern, links the track to a playlist
Should we use Attribution here instead of include.
<a class="attribution" href="#album"></a>
<a class="album-attribution" href="#album"></a>
or thinking outside the "box" a little.
CITE: Contains a citation or a reference to other sources.CITE: html4.1 spec
<cite class="attribution" url="http://yourweb.whatever/html">Track Title here</cite>
does this have the meaning this track is attributed to this album
Integer with value greater than zero giving the ordinal position of the media on the xspf:album.
This value is primarily for fuzzy lookups, though a user-agent may display it.
xspf:track elements MAY contain exactly one. It MUST be a valid XML Schema nonNegativeInteger.
The time to render a resource, in milliseconds. It MUST be a valid XML Schema nonNegativeInteger. This value is only a hint -- different XSPF generators will generate slightly different values. A user-agent MUST NOT use this value to determine the rendering duration, since the data will likely be low quality. xspf:track elements MAY contain exactly one duration element
Do we do this in milliseconds 210000?, I say no not friendly to humans, prasers can add "000" to the second value.
<abbr class="track-duration" title="210">3 minutes 30 seconds</abbr>
- removed rel value has no meaning here 188.8.131.52.184.108.40.206.11.1.1 rel Martin McEvoy - 05:36, 14 May 2007 (PDT)
Value of the metadata element. This is character data, not HTML, and it may not contain markup. xspf:track elements MAY contain exactly one.
<h1 class="track-title"> <a class="url" href="http://yourweb.whatever/tracks/track1.mp3" type="application/mp3">Track</a> </h1>
The extension element allows non-XSPF XML to be included in XSPF documents.
The purpose is to allow nested XML, which the meta and link elements do not. xspf:track elements MAY contain zero or more extension elements.
- xspf example
<playlist version="1" xmlns="http://xspf.org/ns/0/" xmlns:cl="http://example.com"> <trackList> <track> <extension application="http://example.com"> <cl:clip start="25000" end="34500"/> </extension> </track> </trackList> </playlist>
<span class="track-clip"> <abbr class="start" title="210">3.30</abbr> <abbr class="end" title="345">5.75</abbr> </span>
This document and specification is distributed under a Creative Commons Attribution 3.0 license. It is licensed and can be used royalty-free for any purpose.
The authors intend to submit this specification to a standards body with a liberal copyright/licensing policy such as the GMPG (http://gmpg.org/), IETF (http://ietf.org/), and/or W3C (http://w3.org). Anyone wishing to contribute should read each organizations copyright principles, policies and licenses (e.g. the GMPG Principles (http://gmpg.org/principles)) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 (http://creativecommons.org/licenses/by/1.0/) and later), before contributing.
The authors of this Microformat have not and will not apply for patents covering any invention covering this Microformat in part or as a whole. There are no claims to any patent in this document. Each author is required to report any known patent issues immediately under this section.
This document and specification is distributed under a royalty free patent policy, e.g. per the W3C Patent Policy (http://www.w3.org/Consortium/Patent-Policy-20040205/), and IETF RFC3667 (http://www.ietf.org/rfc/rfc3667.txt) & RFC3668 (http://www.ietf.org/rfc/rfc3668.txt).
Contact or get involved
Want to talk more about this or maybe something new?
- Join microformats-new mailing list.