W3C home > Mailing lists > Public > public-iri@w3.org > May 2011

RE: requesting feedback regarding HTML5 and RFC 3987

From: Larry Masinter <masinter@adobe.com>
Date: Thu, 26 May 2011 11:28:53 -0700
To: Chris Weber <chris@lookout.net>, "public-iri@w3.org" <public-iri@w3.org>
CC: "'Mark Nottingham'" <mnot@mnot.net>, "'Thomas Roessler'" <tlr@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D05CAA58EAF@nambxv01a.corp.adobe.com>
The change proposal http://lists.w3.org/Archives/Public/public-html/2010Feb/0882.html gave explicit text for how the HTML document could reference RFC 3987bis. I thought it accomplished all of the requirements.

The objections to that change proposal (as well as one of the other change proposals) were procedural and not technical, that is, the objectors had no confidence that IETF would complete in time.

Larry
--
http://larry.masinter.net


-----Original Message-----
From: public-iri-request@w3.org [mailto:public-iri-request@w3.org] On Behalf Of Chris Weber
Sent: Tuesday, May 24, 2011 11:03 AM
To: public-iri@w3.org
Cc: 'Mark Nottingham'; 'Thomas Roessler'
Subject: requesting feedback regarding HTML5 and RFC 3987

In March 2011, the W3C's HTML WG made a decision to close ISSUE-56
when the parties involved could not come to agreement on aligning
HTML5 with the IRI WG's revisions to RFC 3987:

http://lists.w3.org/Archives/Public/public-html/2011Mar/0404.html

That decision effectively removed the HTML5 specification's
dependency on rfc3987bis.  It appears that this was done so that
the HTML5 specification could define how to translate input strings
contained in text/html documents into URIs.

However, our understanding is that ISSUE-56 can be reopened if new
information emerges, such as "IETF completing production of a
document suitable as a formal reference".  And of course as chairs
of the IRI WG we would like to deliver such a document.

Here is the minimum baseline that we understand is necessary in order
to meet the needs of the W3C's HTML WG:

1) The IRI specification will provide "MUST" language and normative
   algorithms for parsing arbitrary Unicode strings as IRI against
   an absolute base URL.

2) The IRI specification will define how to extract the hostname out
   of an IRI for proper resolution and application of the same origin
   policy.

3) The IRI specification will define how base URI referencing would
   be performed for hierarchical schemes.

The chairs would like to request feedback from the group, especially
those who are also participants in the HTML WG, about whether the
those three deliverables would be sufficient to meet the needs of
the W3C's HTML WG.  If so, we will follow up with more
detailed suggestions for moving toward resolution of those issues.

Marc Blanchet & Chris Weber, co-chairs, IRI WG
Received on Thursday, 26 May 2011 18:29:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:52:01 GMT