Difference between revisions of "User talk:WebOrganics"

From Microformats Wiki
Jump to navigation Jump to search
Line 85: Line 85:
  
 
My 10 meaningful words now hook in this page too! [[User:WebOrganics|WebOrganics]] 13:37, 15 May 2007 (PDT)
 
My 10 meaningful words now hook in this page too! [[User:WebOrganics|WebOrganics]] 13:37, 15 May 2007 (PDT)
 
 
=hSpiff 0.0.2=
 
 
Martin McEvoy  [http://weborganics.co.uk/ WebOrganics] 08:48, 13 May 2007 (PDT)
 
 
hSpiff is '''not''' part of any [[process|microformats process]] and not to be regarded as such.
 
 
==Abstract==
 
 
'''Hypertext Shareable Playlist Format'''
 
 
hSpiff is Based on [http://xspf.org/xspf-v1.html  XSPF Version 1] XML Shareable Playlist Format ("spiff")
 
 
* hSpiff '''is not''' intended to reflect [[hatom|hAtom]] which is used to describe blog posts.
 
* hSpiff '''is 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 [[audio-info-proposal|hAudio 0.3]]
 
 
===XSPF Description===
 
 
<cite>http://xspf.org/xspf-v1.html#rfc.section.3</cite>
 
 
[1] 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.
 
 
<cite>[http://xspf.org/xspf-v1.html#rfc.section.1 XSPF section 1]</cite>
 
 
[2] 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.
 
 
==Schemata==
 
 
===hSpiff===
 
 
<pre><div class="hspiff"></pre>
 
 
 
====playlist-title====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.1 4.1.1.2.1]
 
 
A human-readable title for the playlist.
 
 
xspf:playlist elements MAY contain exactly one.
 
 
<pre><h1 class="playlist-title">Title</h1></pre>
 
 
Decided not to add the root <nowiki>class="playlist"</nowiki> as playlist is already defined with the prefix
 
playlist-
 
 
[http://xspf.org/xspf-v1.html#rfc.section.4.1.1 4.1.1 Playlist]
 
 
====creator====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.2 4.1.1.2.2]
 
 
Human-readable name of the entity (author, authors, group, company, etc) that authored the playlist.
 
 
xspf:playlist elements MAY contain exactly one.
 
 
<pre><span class="creator">Name</span></pre>
 
 
 
====playlist-annotation====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.3 4.1.1.2.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.
 
 
<pre><div class="playlist-annotation">Text and html here only text will be phrased</div></pre>
 
 
 
====playlist-info====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.4 4.1.1.2.4]
 
 
Removed this as playlist-title with <nowiki>class="url"</nowiki> 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.
 
 
 
====url====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.5 4.1.1.2.5]
 
 
Source URI for this playlist.
 
 
xspf:playlist elements MAY contain exactly one.
 
 
<pre><h1 class="playlist-title"><a class="url" href="http://yourweb.whatever/html">Title</a></h1></pre>
 
 
 
====id====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.6 4.1.1.2.6]
 
 
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.
 
 
<pre><h1 class="playlist-title"><a id="album" class="url" href="http://yourweb.whatever/html">Title</a></h1></pre>
 
 
 
====image====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.7 4.1.1.2.7]
 
 
URI of an image to display in the absence of a //playlist/trackList/image element.
 
 
xspf:playlist elements MAY contain exactly one.
 
 
<pre><img class="image" src="http://yourweb.whatever/image/image.jpeg" alt="Image"/></pre>
 
 
class="photo" is more "microformaty"
 
 
 
====playlist-date====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.8 4.1.1.2.8]
 
 
Creation date (not last-modified date) of the playlist, formatted as a XML schema dateTime.
 
 
xspf:playlist elements MAY contain exactly one.
 
 
<pre><abbr class="playlist-date" title="20070106">6th January, 2007</abbr></pre>
 
 
===playlist-track===
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1 4.1.1.2.14.1.1]
 
 
<pre><div class="playlist-track"></pre>
 
 
 
====track-title====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.3 4.1.1.2.14.1.1.1.3]
 
 
<pre><h2 class="track-title">Track</h2></pre>
 
 
-- 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
 
 
 
====track-url====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.2 4.1.1.2.14.1.1.1.2]
 
 
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.
 
 
<pre><h2 class="track-title"><a class="track-url" href="http://yourweb.whatever/tracks/track1.mp3">Track</a></h2></pre>
 
 
 
====album====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.8 4.1.1.2.14.1.1.1.8]
 
 
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.
 
 
<pre><a class="include" href="#album"></a></pre>
 
 
Class include using the [[include | Include Pattern]], links the track to an Album playlist
 
 
or...
 
 
Should we use [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.10 Attribution] here instead of include.
 
 
<pre><a class="album" href="#album" rel="attribution">Playlist Title</a></pre>
 
 
Does this have the meaning this track is attributed to this album?
 
 
====track-num====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.9 4.1.1.2.14.1.1.1.9]
 
 
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.
 
 
<pre><span class="track-num">1</span></pre>
 
 
====track-duration====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.10 4.1.1.2.14.1.1.1.10]
 
 
The time to render a resource, in milliseconds. It MUST be a valid XML Schema [http://www.w3.org/TR/xmlschema-2/#dt-nonNegativeInteger 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.
 
 
<pre><abbr class="track-duration" title="210">3 minutes 30 seconds</abbr></pre>
 
 
 
===attributes===
 
* [http://xspf.org/xspf-v1.html#rfc.section.1.1.2.14.1.1.1.11.1 1.1.2.14.1.1.1.11.1]
 
 
 
====rel====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.11.1.1 4.1.1.2.14.1.1.1.11.1.1]
 
 
URI of a resource type.
 
 
A link to the original source of a playlist with the rel value of attribution
 
 
<pre><a class="album" href="#album" rel="attribution">Playlist Title</a></pre>
 
 
 
====type====
 
* [http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.12.2 4.1.1.2.14.1.1.1.12.2]
 
 
Value of the metadata element. This is character data, not HTML, and it may not contain markup.
 
 
xspf:track elements MAY contain exactly one.
 
 
<pre>
 
<h1 class="track-title">
 
<a class="url" href="http://yourweb.whatever/tracks/track1.mp3" type="application/mp3">Track</a>
 
</h1>
 
</pre>
 
 
 
====track-clip====
 
*[http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.13 4.1.1.2.14.1.1.1.13]
 
 
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
 
<pre><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></pre>
 
 
* hspiff
 
 
<pre><span class="track-clip">
 
<abbr class="start" title="210">3.30</abbr>
 
<abbr class="end" title="345">5.75</abbr>
 
</span></pre>
 
 
==hSpiff using hSet==
 
 
* Based on hSet [[grouping-brainstorming#Option_3:_Explicit_class-based_grouping | Explicit Class based Grouping]]
 
 
I dont know if hSet fits into the microformats way, but it is useful for cramming all your data into one string.
 
 
for example the date time abbr issues can be fixed by using this:
 
<pre>
 
<abbr class="updated.20070513" title="Sunday, May the 13th, 2007">17 05 2007</abbr>
 
</pre>
 
 
All the machine data is in a class where it belongs and NOT interfering with Human data.
 
We wouldn't have to declare hset here because its implied by the string and ("." breadcrumb).
 
 
'''More complex example''' of strings and ("." breadcrumb)s.
 
<pre>
 
<div class="hspiff">
 
 
<h1 class="playlist">
 
<a class="url" href="http://yourweb.whatever/playlist.html">Playlist</a>
 
</h1>
 
<span class="playlist.creator">Name</span>
 
<div class="playlist.annotation">
 
<p>Text and html here only text will be phrased</p>
 
</div>
 
<img class="playlist.image" src="http://yourweb.whatever/image/jpeg" alt="image.jpeg" /><br />
 
<abbr class="playlist.date.20070106" title="The 6Th of January 2007">06 01 2007</abbr>
 
 
<h2 class="playlist.track_1">
 
<a class="url" href="http://yourweb.whatever/tracks/track_1.mp3" type="application/mp3">Track 1</a>
 
</h2>
 
<div class="playlist.track_1.annotation">
 
<p>Text and html here only text will be phrased</p>
 
</div>
 
<abbr class="playlist.track_1.duration.198" title="3 minutes 30 seconds">3 30</abbr>
 
 
<h2 class="playlist.track_2">
 
<a class="url" href="http://yourweb.whatever/tracks/track_2.mp3" type="application/mp3">Track 2</a>
 
</h2>
 
<div class="playlist.track_2.annotation">
 
<p>Text and html here only text will be phrased</p>
 
</div>
 
<abbr class="playlist.track_2.duration.241" title="4 minutes 2 seconds">4 02</abbr>
 
 
<h2 class="playlist.track_3">
 
<a class="url" href="http://yourweb.whatever/tracks/track_3.mp3" type="application/mp3">Track 3</a>
 
</h2>
 
<div class="playlist.track_3.annotation">
 
<p>Text and html here only text will be phrased</p>
 
</div>
 
<abbr class="playlist.track_3.duration.132" title="2 minutes 20 seconds">2 20</abbr>
 
 
<span class="playlist.clip">
 
<p>Playlist Clip:
 
(Start: <abbr class="clip.start.210" title="3 minutes 30 seconds">3 30</abbr>)
 
(End: <abbr class="clip.end.345" title="5 minutes 75 seconds">5 75</abbr>)
 
</p>
 
</span>
 
 
</div>
 
</pre>
 
 
== Further Reading ==
 
 
* [http://xspf.org/xspf-v1.html  XSPF Version 1]
 
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
 
  
 
== Contact or get involved ==
 
== Contact or get involved ==

Revision as of 15:48, 22 May 2007

WebOrganics Talk

Editor
Martin McEvoy, WebOrganics


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)

The Idea

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="description">  
<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


Summary

Interesting points:

  • 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...

Update

My 10 meaningful words now hook in this page too! WebOrganics 13:37, 15 May 2007 (PDT)

Contact or get involved

Martin McEvoy

WebOrganics.

icon-hcard-download.png Download vCard

Want to talk more about this or maybe something new?