W3C home > Mailing lists > Public > www-tag@w3.org > November 2009

Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 24 Nov 2009 20:12:20 -0800
Cc: "public-html@w3.org" <public-html@w3.org>, "PUBLIC-IRI@W3.ORG" <PUBLIC-IRI@w3.org>, "www-tag@w3.org" <www-tag@w3.org>
Message-id: <D1E87BEA-5871-433B-94C5-DD3540D09DF9@apple.com>
To: Larry Masinter <masinter@adobe.com>

I'm assuming this is intended as a Change Proposal for ISSUE-56 urls- 
webarch (mentioning that so the tracker finds it).

My understanding of this proposal is that you'd like the proposed  
changes to be made once the IRI Working Group forms and has a draft  
with all the necessary definitions. If that understanding is correct,  
then I think we should take up this proposal once those preconditions  
have been met. If I have misunderstood, then please clarify.

Speaking in a personal capacity, the draft charter looks good.


On Nov 5, 2009, at 12:20 PM, Larry Masinter wrote:

> I have updated the proposed draft charter for IRI work in IETF:
> http://trac.tools.ietf.org/area/app/trac/wiki/DraftIriCharter
> to explicitly calls for the resulting document as being
> suitable as a normative reference from HTML, and points
> to a draft of HTML Editor Requirements at the end of
> http://trac.tools.ietf.org/area/app/trac/wiki/IriWorkGoals.
> Please review, accept, or update as necessary, the "HTML
> Editor Requirements" prior to IETF chartering of the
> working group next Tuesday Nov 10.
> Assuming the liaison and requirements are acceptable as
> part of the IETF IRI working group charter and we find
> sufficient volunteers for editing, reviewing nad chairing,
> I offer a (vague, but I think workable)
> Based on assuming
> that those requirements are met: please replace the
> definition of URL in the HTML5 specification and all
> descriptions of URL processing in the HTML5 specification
> with specific references to the [IRIBIS] document.
> I think this includes sections such as
> * Determine whether a string best matches Relative
>  or Absolute, e.g., one might say:
>  "Determine whether Absolute or Relative as per [IRIBIS]"
> * Determine whether a string is or isn't valid an IRI
>  "Determine whether valid as per [IRIBIS]"
> * Offer heuristics for interpreting a user input
>  or other unvalidated string as an IRI
>  "User agents MAY interpret invalid strings as if
>  they were valid in cases where the input is
>  not otherwise validated, as per [IRIBIS]"
> * Resolve a relative IRI against a base
> As far as timing goes:
> Whenever you have a normative specification to another
> specification which is, itself, under development,
> there is some coordination necessary, but this request
> is based on the assumption that it isn't necessary
> to wait for the IRIBIS process to complete in order
> for HTML5 to go to last call prior to its publication
> as Proposed Recommendation.
> If there is not an IETF working group to update these
> documents such that they are suitable for reference
> by the HTML working group, then an appropriate change
> proposal would be to put back in the HTML5-only
> URL parsing algorithm that was there before the
> [WEBADDRESS] specification was split out.
> Larry
> -- 
> http://larry.masinter.net
Received on Wednesday, 25 November 2009 04:13:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:31 UTC