- From: Benjamin Nowack <bn@kasabi.com>
- Date: Fri, 21 Oct 2011 19:03:50 +0200
- To: public-html-data-tf@w3.org
Hi, Looking at the influence angles this TF has on RDFa vs. MD editors, I wonder if it might be worth looking in the other direction, too, to check if some of RDFa's features could be directly applied to MD if certain criteria are met. (This could even be interesting for the RDFa community, marketing-wise). To give some examples: * MD doesn't support multi-type items. * Current solution/workaround: Use the rdf:type URI in an @itemprop. * Feature request: Authors targeting MD/RDF parsers should have a more convenient syntax for this. * Potential approach: Use RDFa's @typeof on itemscope'd node. (TF would have to investigate/document potential compatibility issues with RDFa 1.1.) * As a W3C TF, we cannot safely propose an algorithm to generate typical RDF predicate URIs from short property names and unknown itemtypes, due to potential "Namespace squatting", no matter how smart our URI generation mechanism may be. * Current W3C/RDF-compliant solution/workaround: For RDF triples to be generated, you have to always use URIs in @itemprop, unless the itemtype is from a "well-known" RDF vocabulary/namespace and somehow supported by the targeted MD/RDF parser. * Feature request: Authors (or vocabulary maintainers?) should be able to declare a target URI space for their MD markup and/or MD/RDF parsers should be able to safely generate predicate URIs without prior knowledge about the itemtype encountered. * Potential approach: Use RDFa's @vocab to define an RDF target namespace. * RDF generated from pure MD cannot have datatyped literals (including markup). * Current solution: None * Feature request: Authors (or vocabulary maintainers?) should be able to declare datatypes or hints for markup preservation. * Potential existing solution: Use RDFa's @vocab to point at a formal description of the intended datatypes (would need network access). Or use RDFa's @datatype. If there are none of these "RDF interpretation allowed" triggers, a parser would simply stay in the MD-restricted model. Just an idea while we're dancing on opinion minefields ;-) Benji -- Benjamin Nowack Software Engineer, Kasabi, Talis Systems Ltd http://kasabi.com/ http://twitter.com/bengee http://bnode.org/ Talis Systems Ltd is registered in England and Wales as 07196440.
Received on Friday, 21 October 2011 17:04:21 UTC