- From: Ivan Herman <ivan@w3.org>
- Date: Wed, 15 Sep 2010 11:04:03 +0200
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: RDFa WG <public-rdfa-wg@w3.org>, Sebastian Heath <sebastian.heath@gmail.com>
- Message-Id: <DE3254E9-48B9-4FB0-BA25-5E16786183F1@w3.org>
(Copying Sebastian explicitly) Well... I think having a document that states very clearly how the microdata information can be turned into RDF would be very good. That means that, on the API level, a parser can be used for microdata. I have no idea who would write such a document, though. If there was a possibility to map an HTML5+Microdata file to a HTML5+RDFa file or, to put it another way, a DOM->DOM type transformation then that would of course be useful. This falls back to the conceptual hGRDDL approach of Ben, ie, defining preprocessing steps before running the RDFa processing; this may be then relatively simple to implement on top of existing RDFa processors. But I have no idea whether it is possible. Ivan On Sep 15, 2010, at 05:19 , Manu Sporny wrote: > Here's an interesting idea from Sebastian Heath via Twitter: > >> sebastianheath: Has anybody thought about merging rdfa and microdata > > via @itemprop? So that itemprop/property are interchangeable. #rdfa >> #microdata > > It's interesting because I can almost see an alternative document that > tells RDFa processors how to interpret Microdata markup via the RDFa > Processing rules. Note that this would be a document that is completely > external to RDFa Core, XHTML+RDFa, and HTML+RDFa. > > The preliminary updates to the processing rules in an external document > that would allow this to happen are below. Here is the translation table > from Microdata to RDFa: > > Microdata RDFa > --------- ---- > itemscope typeof="" > itemref about="#ITEMREF_VALUE" or about="FULL_URI" > itemtype typeof="ITEMTYPE_VALUE" (OVERRIDES itemscope) > itemprop property="FULL_URI" or property="MODDED_ITEMPROP_VAL" > > where MODDED_ITEMPROP_VAL is "http://www.w3.org/1999/xhtml/vocab#" + > attribute value of itemprop. > > There are still problems with nesting itemprops/itemscopes and the types > that Microdata has specified for vcard, vevent and work... don't know if > anybody else has looked at this yet. Just throwing it out there. > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny) > President/CEO - Digital Bazaar, Inc. > blog: Saving Journalism - The PaySwarm Developer API > http://digitalbazaar.com/2010/09/12/payswarm-api/ > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Wednesday, 15 September 2010 09:01:18 UTC