Re: 'Web addresses in HTML 5' for review [IRIEverywhere-27 ISSUE-27]

An editorial concern:  step 3 in section 3 says [1]:

        * If encoding is UTF-16, then change it to UTF-8.

I think this reads two ways:

        1. Go and convert the Web address
           string to UTF-8, then proceed
        2. Don't touch the string, but for
           purposes of the remaining steps,
           assume that "encoding" is
           set to UTF-8.

Whichever it is, I recommend that it be stated more clearly.  Thank you.

Noah

[1] 
http://lists.w3.org/Archives/Public/public-html/2009Mar/att-0444/draft.html#resolving-urls

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------






        Dan Connolly <connolly@w3.org>
        Sent by: www-tag-request@w3.org
        03/18/2009 10:49 AM 
                 To: www-tag@w3.org
                 cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
                 Subject: 'Web addresses in HTML 5' for review 
[IRIEverywhere-27 ISSUE-27]


I worked with MSM to produce a draft; it's attached
to a message to public-html:

'Web addresses in HTML 5' for review (ISSUE-56 urls-webarch) (from
connolly@w3.org on 2009-03-18)
http://www.w3.org/mid/1237384619.7868.1226.camel%2540pav.lan

This is progress on...
ACTION-188 Investigate the URL/IRI/Larry Masinter possible resolution of
the URL/HTML5 issue.

I expect to have a revised draft later this week.


-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
gpg D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E