<608D7D1F-2F2D-4EC8-93E2-C2E1E05CCC53@apple.com>
Current votes: None.
--Boundary_(ID_GFOC1cCt+lBBHEyK6tUApA) Content-type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-transfer-encoding: quoted-printable Thanks for providing the details! And thanks for all the progress on =20 this front in general. I'd appreciate it if HTML Working Group members could study the =20 differences (if any) in normative requirements between this text and =20 the current draft-duerst-iri-bis vs. the old text plus Web Address, so =20= we can determine whether we need to propose changes to IRIbis. (One =20 small one I spotted while skimming: Under the new text, any IRI would =20= count as a "valid URL", even ones that use non-ASCII characters in the =20= query portion and thus would be processed differently under Web =20 Address processing than vanilla IRI processing; while with the old =20 text these would not be valid.). - Maciej On Nov 28, 2009, at 2:16 PM, Larry Masinter wrote: > Regarding ISSUE-56, and applying the results of ACTION-137 (pending =20= > review): > > > Providing specific details for the requested change is a required =20= > part of a Change Proposal, as stated here: > > = <http://dev.w3.org/html5/decision-policy/decision-policy.html#change-propo= sal > > The process does include "With prior permission from the chairs, a =20 > high-level prose description of the changes to be made." > > Lacking this prior permission (which the previous change proposal =20 > had unfortunately assumed), I=92ll offer a more concrete proposed =20 > rewrite (attached). However, I think additional, more extensive =20 > editorial work would be helpful. For example, using the term =93HREF=94 = =20 > instead of =93URL=94 in any normative text of the HTML5 specification =20= > would avoid some of the circumlocutions in the definitions, but =20 > would be a much more extensive editorial task than the edits to =20 > 2.5.1 that I limited myself to in this change proposal. > > In addition, adjusting the documents from HTML5 and the IRI work in =20= > IETF may require maintaining alignment of two different documents, =20 > and if there are any further changes to the [draft-duerst-iri-bis] =20 > document (based on rough consensus of the IRI working group which I =20= > presume would including contributors from this community), then =20 > coordination of the text in HTML5 and text in the IRI document will =20= > be necessary. > > Larry > -- > http://larry.masinter.net > > > <iri-rewrite-draft.html> --Boundary_(ID_GFOC1cCt+lBBHEyK6tUApA) Content-type: text/html; charset=WINDOWS-1252 Content-transfer-encoding: quoted-printable <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; "><div><br></div><div>Thanks for = providing the details! And thanks for all the progress on this front in = general.</div><div><br></div><div>I'd appreciate it if HTML Working = Group members could study the differences (if any) in normative = requirements between this text and the current draft-duerst-iri-bis vs. = the old text plus Web Address, so we can determine whether we need to = propose changes to IRIbis. (One small one I spotted while skimming: = Under the new text, any IRI would count as a "valid URL", even ones that = use non-ASCII characters in the query portion and thus would be = processed differently under Web Address processing than vanilla IRI = processing; while with the old text these would not be = valid.).</div><div><br></div><div> - Maciej</div><br><div><div>On = Nov 28, 2009, at 2:16 PM, Larry Masinter wrote:</div><br = class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span = class=3D"Apple-style-span" style=3D"border-collapse: separate; color: = rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: = normal; font-variant: normal; font-weight: normal; letter-spacing: = normal; line-height: normal; orphans: 2; text-align: auto; text-indent: = 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: = 0px; -webkit-border-horizontal-spacing: 0px; = -webkit-border-vertical-spacing: 0px; = -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: = auto; -webkit-text-stroke-width: 0px; "><div lang=3D"EN-US" link=3D"blue" = vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; = margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: = 10.5pt; font-family: Consolas; ">Regarding ISSUE-56, and applying the = results of ACTION-137 (pending review):<o:p></o:p></div><div = style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; = margin-left: 0in; font-size: 10.5pt; font-family: Consolas; = "><o:p> </o:p></div><div style=3D"margin-top: 0in; margin-right: = 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; = font-family: Consolas; ">> Providing specific details for the = requested change is a required part of a Change Proposal, as stated = here:<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; = margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; = font-family: Consolas; ">> <<a = href=3D"http://dev.w3.org/html5/decision-policy/decision-policy.html#chang= e-proposal" style=3D"color: blue; text-decoration: underline; = ">http://dev.w3.org/html5/decision-policy/decision-policy.html#change-prop= osal</a><o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: = 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; = font-family: Consolas; "><o:p> </o:p></div><div style=3D"margin-top: = 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; = font-size: 10.5pt; font-family: Consolas; ">The process does include = "With prior permission from the chairs, a high-level prose description = of the changes to be made."<o:p></o:p></div><div style=3D"margin-top: = 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; = font-size: 10.5pt; font-family: Consolas; "><o:p> </o:p></div><div = style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; = margin-left: 0in; font-size: 10.5pt; font-family: Consolas; ">Lacking = this prior permission (which the previous change proposal had = unfortunately assumed), I=92ll offer a more concrete proposed rewrite = (attached). However, I think additional, more extensive editorial = work would be helpful. For example, using the term =93HREF=94 instead of = =93URL=94 in any normative text of the HTML5 specification would avoid = some of the circumlocutions in the definitions, but would be a much more = extensive editorial task than the edits to 2.5.1 that I limited myself = to in this change proposal.<o:p></o:p></div><div style=3D"margin-top: = 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; = font-size: 10.5pt; font-family: Consolas; "><o:p> </o:p></div><div = style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; = margin-left: 0in; font-size: 10.5pt; font-family: Consolas; ">In = addition, adjusting the documents from HTML5 and the IRI work in IETF = may require maintaining alignment of two different documents, and if = there are any further changes to the [draft-duerst-iri-bis] document = (based on rough consensus of the IRI working group which I presume would = including contributors from this community), then coordination of the = text in HTML5 and text in the IRI document will be = necessary.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: = 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; = font-family: Consolas; "><o:p> </o:p></div><div style=3D"margin-top: = 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; = font-size: 10.5pt; font-family: Consolas; ">Larry<o:p></o:p></div><div = style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; = margin-left: 0in; font-size: 10.5pt; font-family: Consolas; = ">--<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; = margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; = font-family: Consolas; "><a href=3D"http://larry.masinter.net" = style=3D"color: blue; text-decoration: underline; = ">http://larry.masinter.net</a><o:p></o:p></div><div style=3D"margin-top: = 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; = font-size: 10.5pt; font-family: Consolas; "><o:p> </o:p></div><div = style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; = margin-left: 0in; font-size: 10.5pt; font-family: Consolas; = "><o:p> </o:p></div><span><iri-rewrite-draft.html></span></div>= </div></span></blockquote></div><br></body></html>= --Boundary_(ID_GFOC1cCt+lBBHEyK6tUApA)--