W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > August 2007

Display values for RDFa object URLs

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Mon, 06 Aug 2007 21:29:20 -0400
Message-ID: <46B7CAF0.2010408@digitalbazaar.com>
To: RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>

While working on the hAudio RDFa test cases using Operator, we ran into
a problem that we are currently having in the Microformats community.
That is - when using rel, how do you denote a display value to the
browser? A full description of the problem can be found here:

http://microformats.org/wiki/audio-info-issues#Problem:_Display_properties_of_rel-patterns

and here:

http://microformats.org/wiki/audio-info-issues#Problem:_Peeking_into_child_elements_to_display_rel-patterns

For example, for the following XHTML:

<div instanceof="hmedia:Audio" about="#song">
   <a rel="hmedia:sample"
      href="http://www.bitmunk.com/sample/6011101">
      Listen to a Sample
   </a>
</div>

generates the following triple (I think, please correct me):

#song rdf:type hmedia:Audio
   hmedia:sample <http://www.bitmunk.com/sample/6011101>

The browser has no choice but to display the URL, as the text value is
not a part of the gleaned information. If we wanted to associate a text
value with the URL, we'd have to do something like so:

<div instanceof="hmedia:Audio" about="#song">
   <span instanceof="hmedia:Sample" about="#song_sample"
   <a rel="hmedia:uri" about="#song_sample"
      href="http://www.bitmunk.com/sample/6011101">
      <span property="dc:title">Listen to a Sample</span>
   </a>
</div>

generates the following triples (again, please correct if incorrect):

#song rdf:type hmedia:Audio
   #song_sample rdf:type hmedia:Sample
   #song_sample hmedia:uri http://www.bitmunk.com/sample/6011101
   #song_sample dc_title Listen to a Sample

The example above would get what we want accomplished, but at the cost
of making the XHTML very complicated and requiring us to create a class
for every "rel" type that uses a URL as it's object.

Any suggestions on making the XHTML cleaner? Or are we stuck with the
latter method of getting display values up to Operator?

-- manu
Received on Tuesday, 7 August 2007 01:29:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:09 GMT