Re: Linking to @about in RDFa Lite? (ISSUE-115)

Sebastian,


On Nov 5, 2011, at 21:29 , Sebastian Heath wrote:

> I hope this conversation hasn't ended. I see two things that still
> need to be hashed out:
> 
> 1: Section 2.3 of the RDFa Lite Documentation is incorrect in using
> the language "If you want people to link to things on your page..." in
> reference to the functionality of @about.
> 
> The implication of "to link to things on your page" seems clear. "to
> link" is reasonably understood as using a browser to arrive at "things
> on your page." The characters 'about="#manu"' will not achieve that
> goal.

I agree this formulation may lead to conclusion. I have added an explicit issue to the tracker (ISSUE-115), referring to your mail.


> So I suggest one of two corrections:
> 
>  a: change the html to read '<p id="manu" vocab="http://schema.org/"
> about="#manu" typeof="Person">'
> 
>  b: change the introductory sentence of the section to read to
> something hopefully less technical than:
> 
>    "If you want an RDFa processor to produce a triple with
> "http://example.org/people#manu" you can use @about with a value of
> "#manu".'
> 
> I prefer a. But it's incorrect as is.
> 

I would strongly disagree with (a): there is no requirement, when creating URI-s in RDF, that this must refer to a specific anchor in the containing HTML text. So I would go with something like (b). It may go along a line like:

[[[
If you want an RDFa processor to create a URI with a fragment ID bound to the address of your page, you may use the '#' syntax, eg, @about="#manu"
]]]

but I let Manu have the final word on the formulation.


> 
> 2: implementing an analog to rdf:ID either in RDFa 1.1 core or in the
> HTML+RDFa 1.1 specification .
> 

I do not see the necessity for this. The combination of @id and @about provides the same functionality, I do not think we should introduce yet another attribute for this.

> I'll file this as a bug. If anybody has thoughts about where that's
> best done, I'd welcome input.

As I said, I did it for you:

http://www.w3.org/2010/02/rdfa/track/issues/115

Sincerely

Ivan


> 
> -Sebastian
> 
> 
> On Wed, Nov 2, 2011 at 12:04 PM, Ivan Herman <ivan@w3.org> wrote:
>> 
>> On Nov 2, 2011, at 16:35 , Toby Inkster wrote:
>> 
>>> On Wed, 2 Nov 2011 10:03:32 +0100
>>> Ivan Herman <ivan@w3.org> wrote:
>>> 
>>>> We could, of course, discuss the possibility for @id to be _accepted_
>>>> by an RDFa processor as an @about
>>> 
>>> eRDF (Ian Davis' pre-RDFa experiment in embedding RDF in HTML) does
>>> precisely this: uses @id to set the subject for triples.
>>> 
>>> It's quite possibly the single most horrible feature of eRDF.
>>> 
>> 
>> :-)
>> 
>>> Just because you add id="heading_block" to a <div> element, odoesn't
>>> mean you want the <h1 property="dc:title"> nested inside there to stop
>>> referring to the document as a whole.
>> 
>> You are right. I hereby withdraw what I said:-)
>> 
>> Ivan
>> 
>> 
>>> 
>>> --
>>> Toby A Inkster
>>> <mailto:mail@tobyinkster.co.uk>
>>> <http://tobyinkster.co.uk>
>>> 
>> 
>> 
>> ----
>> Ivan Herman, W3C Semantic Web Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> PGP Key: http://www.ivan-herman.net/pgpkey.html
>> FOAF: http://www.ivan-herman.net/foaf.rdf
>> 
>> 
>> 
>> 
>> 
>> 
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf