W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > October 2011

Linking to @about in RDFa Lite?

From: Sebastian Heath <sebastian.heath@gmail.com>
Date: Mon, 31 Oct 2011 12:11:37 -0400
Message-ID: <CACsb_1paOw+BLbUqRGZXrpmY_Hza13tdi69y-8ntxvQY7AWUJw@mail.gmail.com>
To: RDFa WG <public-rdfa-wg@w3.org>

 Looking at section 2.3 of the new RDFa Lite draft [1], it starts:

If you want people to link to things on your page, you can identify
the thing using a hash and a name. For example:

<p vocab="http://schema.org/" about="#manu" typeof="Person">

Is that correct? I think it implies that the presence of @about is
enough to get a browser to move to that part of the page.

 Should the html be

 <p vocab="http://schema.org/" id="manu" about="#manu" typeof="Person">

 I'm far from filing a bug because I may misunderstand the markup.

Broadening the conversation, having to put both @id and @about on
elements to define RDFa patterns that are "about themselves" has
always struck me as odd. But perhaps it's an inevitable cost of RDFa
being a graph-based, distributed format. Or perhaps we're in the
rabbit hole of information and non-information resources.

 I guess I'm more broadly raising the topic of a convention for
marking @id attributes as visible to an RDFa (lite?) processor. Has
there been any thinking on that? I understand it might mess up
backwards compatibility. But I could really (really!) use it to
simplify my markup.


[1] http://www.w3.org/2010/02/rdfa/drafts/2011/ED-rdfa-lite-20111030/#about
Received on Monday, 31 October 2011 16:12:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:53 UTC