Re: RDFa Lite and non-RDFa @rel values

Perhaps the way to address unwanted @rel terms expanding because of @vocab is simply to say that, for HTML+RDFa, @vocab is not used to turn terms into IRIs, and so anything that's not a defined term causes the @rel to be dropped.

This only affects HTML+RDFa 1.1, so does not address a CR change to RDFa 1.1 Core.


On Apr 24, 2012, at 10:59 AM, Alex Milowski wrote:

> On Tue, Apr 24, 2012 at 10:50 AM, Stéphane Corlosquet
> <> wrote:
>> I'm not sure what you're trying to achieve here. @resource behaves the same
>> way whether its element include a @typeof or not. the only difference is
>> that the new subject is typed. my point is that without @typeof you would
>> also get the same triple with the @href value a new subject:
>>   <> dc:title "W3C's Home Page"
>> Expressing triples with the @href as new subject is not an issue with the
>> current processing steps, you just have to nest your markup inside the a
>> element.
>> But maybe I missed your point?
> Yes, true.  The point was about getting something similar to the triple:
> <> <...homepage> <>
> that you lose with you have both @property and @rel on the same link.
> With @typeof, the link target gains a type triple.  It isn't the same
> graph but you are able to have the relationship of the document to the
> linked page via @rel and the "kind" of the link via @typeof generating
> an rdf:type predicate.  So, the loss of the @property generating a
> homepage predicate isn't a big deal because it generates a different
> triple that can be used to gain similar information.
> In the end, it may justify the status quo.
> -- 
> --Alex Milowski
> "The excellence of grammar as a guide is proportional to the paucity of the
> inflexions, i.e. to the degree of analysis effected by the language
> considered."
> Bertrand Russell in a footnote of Principles of Mathematics

Received on Tuesday, 24 April 2012 18:23:51 UTC