proposed update to IRI document posted

[Larry Masinter-3]

(bcc tag@... and public-html@...
to fulfill action items for both groups.)

http://larry.masinter.net/iribis-hack.html
http://tools.ietf.org/rfcdiff?url1=draft-duerst-iri-bis.txt&url2=http://larry.masinter.net/iribis-hack.txt 

My goal for this version was to address
Martin's concerns, add a section on open
issues, and start to integrate some of
the "Web Address" changes (like single
percent and # in fragments) directly into
the IRI specification itself (rather than
leave it as a preprocessing step.)

I added an "open issues" section.


If I can't get the other principal's
to agree this is going in the right
direction, then we'll need another
fall-back plan, so I'd like to see
if we can hash-out the overall direction.

On the other hand, nits expressed
as simple edits would be great.

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

["Martin J. Dürst"]

Hello Larry,

On 2009/09/22 5:52, Larry Masinter wrote:

> (bcc tag@... and public-html@...
> to fulfill action items for both groups.)
>
> http://larry.masinter.net/iribis-hack.html
> http://tools.ietf.org/rfcdiff?url1=draft-duerst-iri-bis.txt&url2=http://larry.masinter.net/iribis-hack.txt
>
> My goal for this version was to address
> Martin's concerns, add a section on open
> issues, and start to integrate some of
> the "Web Address" changes (like single
> percent and # in fragments) directly into
> the IRI specification itself (rather than
> leave it as a preprocessing step.)

I think that the discussion in the thread with the Subject "Proposed
Charter and Agenda for IRI BOF at IETF 76" concluded that the HTML5
references preprocessing should be a clearly separate piece in the IRI
spec (or be defined somewhere else).

If you  encountered problems when doing that, it would be good to share
these, so that we all can help getting there.

Regards,   Martin.

> I added an "open issues" section.
>
>
> If I can't get the other principal's
> to agree this is going in the right
> direction, then we'll need another
> fall-back plan, so I'd like to see
> if we can hash-out the overall direction.
>
> On the other hand, nits expressed
> as simple edits would be great.
>
> Larry
> --
> http://larry.masinter.net
>

--
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@...