W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > September 2009

ISSUE-233: use other URI-carrying attributes in HTML+RDFa

From: SWD Issue Tracker <dean+cgi@w3.org>
Date: Wed, 2 Sep 2009 23:53:31 +0000 (GMT)
To: public-swd-wg@w3.org,public-rdf-in-xhtml-tf@w3.org
Message-Id: <20090902235331.89F367F46F@otto.w3.org>

ISSUE-233: use other URI-carrying attributes in HTML+RDFa


Raised by: Ben Adida
On product: RDFa

Dorian Taylor:


existing attributes in the markup intended to carry URIs, specifically
@data in <object> and @cite in <q>, <blockquote>, <ins> and <del>. Now
that I think of it, however, a similar protocol may apply to
attributes like @longdesc in <img>, <frame> and <iframe> and @action
in <form>.

What these attributes have in common is that they follow the pattern
of specifying resource objects like @href or @resource, with the
exception of object/@data which I read to be equivalent to @src (or
@about). While the bulk of them have additional meaning than just a
URI reference (I excluded @usemap because its meaning is extremely
narrow), I am optimistic that they could be used in lieu of
RDFa-specific attributes without any ambiguity. The purpose of doing
so (as I read the purpose of RDFa itself) use a document's existing
data to express additional (not conflicting) semantics.

As such, it would be totally reasonable to say:

<q rel="dcterms:references" cite="#benjamin-franklin"
property="rdf:value">Remember that time is money.</q>

to mean:

<> rdf:value "Remember that time is money."; dcterms:references
<#benjamin-franklin> .


Received on Wednesday, 2 September 2009 23:53:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:04 UTC