Re: [Moderator Action] Re: [ISSUE-2] Re: Strawman microdata proposal

Hi Fabien,

a clarification question: do you also disagree with this part of Jirka's
statement:

> Which is of no use for ITS usage scenarios. ITS data categories are
> providing metadata about particular elements in XML and this relation
> is very important. In your example triplets are completely disconnected
> from the original HTML document. It's not possible to track back on
> which element respective its:* properties should be applied.

And if you disagree, how would in the example the triplets be connected to
the original HTML document? I am really just trying to understand how that
would work technically, in as much detail as possible. The RDFa primer
doesn't give information about that it seems.

Thanks,

Felix

Am 21. März 2012 10:31 schrieb Fabien Gandon <fabien.gandon@inria.fr>:

> Hello,
>
> > Which is of no use for ITS usage scenarios. ITS data categories are
> > providing metadata about particular elements in XML and this relation
> > is very important. In your example triplets are completely disconnected
> > from the original HTML document. It's not possible to track back on
> > which element respective its:* properties should be applied.
> >
> > You will have to assign unique URI to each element with ITS data
> > categories applied and then use about="URI" to replace blank node in
> > your RDF graph with subject representing. Of course resulting syntax
> > and complexity of processing will be by magnitude more complex then just
> > using normal attributes.
>
> I disagree with this statement.
>
> Many RDFa tools actually use the RDFa Syntax to augment the document
> processing e.g. augment browser functionalities directly on top of the
> document visualization.
>
> The fact that standalone triples can be extracted from an RDFa and
> represented in Turtle, RDF/XML etc. does not mean an RDFa Parser cannot
> directly exploit the HTML+RDFa document and the coupling of the original
> document to its metadata. Many RDFa, and microformat applications use that
> ability for instance to offer functionalities on the annotated pieces of
> the rendered document.
>
> Their is absolutely no obligation to add a URL to each and every element
> to be able to use RDFa and its links to the document, only if you require
> the processing to be on the extracted RDF alone wich is not mandatory and
> certainly not what was recommended here.
>
> I believe the RDFa primer makes this point very clearly in its
> introduction:
> "Using a few simple HTML attributes, authors can mark up human-readable
> data with machine-readable indicators for browsers and other programs to
> interpret."
> http://www.w3.org/2010/02/rdfa/sources/rdfa-primer/#introduction
>
> Best regards,
> --
> fabien, inria, @fabien_gandon, http://fabien.info
>
>
>
>
>


-- 
Felix Sasaki
DFKI / W3C Fellow