- From: Benjamin Nowack <bnowack@semsol.com>
- Date: Fri, 22 Jan 2010 10:12:47 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: public-html@w3.org, "Philip Jägenstedt" <philipj@opera.com>
P.S. as I just saw Ian's comment on IRC[1]:
This algorithm ignores non-RDF structures such as
<div itemscope itemtype="http://example.com/">
<span itemprop="a/b"/>
</div>
or
<div itemscope itemtype="http://example.com/a/">
<span itemprop="b"/>
</div>
because common RDF vocabularies simply don't use URI patterns
like "http://example.com/" or "http://example.com/a/" to
declare resource types.
Requiring OWL magic to convert Microdata to its target
RDF vocabulary makes Microdata even more complex to understand
than RDFa. OWL is well beyond what a Microdata-to-RDF parser
writer should need to know.
Cheers,
Benji
[1] http://krijnhoetmer.nl/irc-logs/whatwg/20100122#l-168
On 21.01.2010 16:56:39, Tab Atkins Jr. wrote:
>On Thu, Jan 21, 2010 at 3:36 PM, Benjamin Nowack <bnowack@semsol.com> wrote:
>> * The parser finds itemtype=http://xmlns.com/foaf/0.1/Person
>> * In common RDF practice, this (slash-)URI represents an RDF
>> Â Class called "Person" from an RDF vocabulary identified by
>> Â "http://xmlns.com/foaf/0.1/" (The other case are hash-URIs,
>> Â where the term name is separated from the vocabulary URI
>> Â by a #, e.g. as in "http://rdfs.org/sioc/ns#User").
>
>Is it possible to relatively reliably distinguish between slash and
>hash uri structures based on the itemtype? If so, can your algorithm
>be extended to also handle the common hash-uri structure?
Received on Friday, 22 January 2010 09:13:20 UTC