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

ISSUE-114 (HTML5 @href as URL): HTML5 content model for @href/@src coerces values to URLs [RDFa 1.1 in HTML5]

From: RDF Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 01 Nov 2011 20:38:20 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1RLL6C-0002lj-Ij@barney.w3.org>

ISSUE-114 (HTML5 @href as URL): HTML5 content model for @href/@src coerces values to URLs [RDFa 1.1 in HTML5]

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

Raised by: Gregg Kellogg
On product: RDFa 1.1 in HTML5

HTML5 has DOM access rules for accessing @href/@src values (in addition to others) in "Resolve URLs" [1]. The affect of these is to both require that relative URLs take into consideration xml:base, and that IRI paths are turned into URIs using percent encoding. (Note xml:base is not allowed in HTML5 docs, but it would be in XHTML5).

Step 6 normalizes any _host_ component to UTF-8 and then performs a IDNA ToASCII algorithm [2].

Step 7 normalizes any _path_ component that is not ASCII with the percent-encoded equivalent.

The result of both these steps is that IRIs may be converted to URIs. This means that @href and @src may not safely be used with IRIs that are not URIs. There is no such requirement on DOM access for @about, @typeof or @resource, so these may safely be used for representing IRIs, but may have different relative-IRI resolution algorithms imposed.

[1] http://dev.w3.org/html5/spec/Overview.html#resolve-a-url
[2] http://tools.ietf.org/html/rfc3490#page-10
Received on Tuesday, 1 November 2011 20:40:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:18 GMT