Re: Updated Microdata to RDF Working Draft

Hi Gregg and all,

A large work on Vocabulary Expansion described in Section 4 of the 
working draft work [1] is based on some constraints of the Microdata 
specification [7 <#7>]:

/Microdata requires that all values of @itemtype come from the same 
vocabulary. This is required as @itemprop values are resolved relative 
to that vocabulary/

I slightly changed your Example 13 from [1]  to allow two types and two 

<div itemscope itemtype="">
   <link itemprop="additionalType" href="" />
   <p itemprop="|email|"></p>

I would like to use foaf:mbox on the above example and it seems to me 
that following the current spec [7] is difficult if not impossible. 
Possible solutions such as:

<meta content="" itemprop=""/>

may don't work as a processor may relate 
to and not to the "additional type".

  (the original example with GoodRelations was somehow different as any 
GoodRelation Product is subclass of therefore 
the @name property is  inherited by Goodrelations Product)

I kindly ask you, also people from the HTML data task force as well as 
Microdata spec editors about *rationales behind the actual Microdata 
specification* [7 <#7>] . I understand the concern of using namespaces 
but still is not enough clear why @itemtype and @itemprop does not allow 
items from different vocabularies.

Indeed, allowing multiple vocabularies  using only @itemtype and 
@itemprop attributes and no namespaces requires processors to relate to 
schemas of these vocabularies and may also introduce name ambiguity (as 
schema does not provide URI for properties).

In any case adding @additionalType may not be the most elegant solution 
as it appears  not solving the problem of multiple vocabularies.

Thank you,
Adrian Giurca


On 9/20/2012 8:22 AM, Gregg Kellogg wrote:
> I've prepared an updated Microdata to RDF Working Draft for review [1]. Please note that, as this is a Note of the Semantic Web Interest Group, and the HTML Data Task Force is complete, the official place for feedback is
> This update adds support for vocabulary expansion, principally to support features such as schema:additionalType. Microdata vocabulary expansion is a subset of RDFa vocabulary expansion, and is fully compatible with RDFa, such that toolsets which process both RDFa 1.1 and Microdata to RDF can use a single vocabulary expansion algorithm, although its use in Microdata is mandatory, whereas it is optional in RDFa 1.1.
> To support vocabulary expansion, additional features are added to the registry: within a vocabulary, a property can be either specified as "equivalentProperty" of another IRI, or "subPropertyOf" another IRI, to use either owl:equivalentProperty or rdfs:subPropertyOf expansion rules. The default registry has been updated for additionalType as follows:
> {
>    "": {
>      ...
>      "properties": {
>        "additionalType": {"subPropertyOf": ""}
>        ...
>      }
> }
> Note that the current published registry [2] has not been updated. The version of the registry used for this working draft is available in the supplement [3], and in the mercurial repository [4].
> Additionally, when a vocabulary is detected, an rdfa:usesVocabulary triple is generated, which enables the RDFa 1.1 vocabulary expansion toolchain. If at some point includes OWL2 expansion rules supported by RDFa within the vocabulary definition, this will allow full use of this through RDFa tool chains which support Microdata to RDF.
> The draft references the test-suite [5], which now has a number of tests (currently 74) available to help developers check processor conformance. This includes all of the current microdata examples.
> After a reasonable feedback period, this working draft will update the current published note [6].
> Thanks to Ivan for invaluable help in preparing this update.
> Gregg Kellogg
> [1]
> [2]
> [3]
> [4]
> [5]
> [6]

Received on Wednesday, 26 September 2012 13:29:22 UTC