ISSUE-114: HTML5 content model for @href/@src coerces values to URLs
HTML5 @href as URL
HTML5 content model for @href/@src coerces values to URLs
- State:
- CLOSED
- Product:
- RDFa 1.1 in HTML5
- Raised by:
- Gregg Kellogg
- Opened on:
- 2011-11-01
- Description:
- 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 - Related Actions Items:
- No related actions
- Related emails:
- Re: Official Response to ISSUE-114 from RDF Web Apps WG (from gregg@kellogg-assoc.com on 2012-01-28)
- Official Response to ISSUE-114 from RDF Web Apps WG (from msporny@digitalbazaar.com on 2012-01-28)
- Re: Telecon Agenda - December 8th 2011, 1400 UTC (from scorlosquet@gmail.com on 2011-12-08)
- Re: Telecon Agenda - December 8th 2011, 1400 UTC (from ivan@w3.org on 2011-12-08)
- Telecon Agenda - December 8th 2011, 1400 UTC (from msporny@digitalbazaar.com on 2011-12-07)
- Almost belated regrets (was Re: Telecon Agenda - December 1st 2011, 1400 UTC (from Steven.Pemberton@cwi.nl on 2011-12-01)
- Telecon Agenda - December 1st 2011, 1400 UTC (from msporny@digitalbazaar.com on 2011-11-28)
- My opinions on the remaining issues (ISSUE-108, ISSUE-114, ISSUE-115, ISSUE-117, ISSUE-119, ISSUE-121) (from ivan@w3.org on 2011-11-22)
- Fwd: Parsing Microdata into RDF Graphs: URI Comparison (relevant to ISSUE-114) (from ivan@w3.org on 2011-11-16)
- Just checking out where we are with RDFa issues (from ivan@w3.org on 2011-11-15)
- Telecon Agenda - November 10th 2011, 1400 UTC (from msporny@digitalbazaar.com on 2011-11-09)
- Re: Telecon Agenda - November 3rd 2011, 1400 UTC (from ivan@w3.org on 2011-11-03)
- Telecon Agenda - November 3rd 2011, 1400 UTC (from msporny@digitalbazaar.com on 2011-11-02)
- ISSUE-114 (HTML5 @href as URL): HTML5 content model for @href/@src coerces values to URLs [RDFa 1.1 in HTML5] (from sysbot+tracker@w3.org on 2011-11-01)
Related notes:
RESOLVED: Place a note in the HTML+RDFa specification notifying authors that IRIs placed into @href, @src and @data could be transformed if access via the DOM.
http://www.w3.org/2010/02/rdfa/meetings/2011-12-08#resolution_1
Display change log