RE: closing IRIEverywhere

http://tools.ietf.org/html/draft-ietf-iri-3987bis-00#section-1.3

contains a definition in section 1.3 on "LEIRI proessing" which should
in fact be a definition of LEIRI:

     LEIRI:  This term was used in
      various XML specifications to refer to strings that, although
not
      valid IRIs, were acceptable input to the processing rules in
      Section 7.1.


where Section 7.1 of the same document is intended to contain an
algorithm that will convert an LEIRI to an IRI.


If that's adequate for XML Core to change its reference for LEIRI,
fine, and if you need more, please say so, preferably by opening
a bug on the IRI spec at 

http://trac.tools.ietf.org/wg/iri/trac/report/1


Larry


-----Original Message-----
From: Grosso, Paul [mailto:pgrosso@ptc.com] 
Sent: Monday, May 03, 2010 7:14 AM
To: Henry S. Thompson; Julian Reschke
Cc: Larry Masinter; www-tag@w3.org
Subject: RE: closing IRIEverywhere

The XML Core WG awaits a more definitive response.

paul

> -----Original Message-----
> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On
Behalf
> Of Henry S. Thompson
> Sent: Wednesday, 2010 April 21 10:45
> To: Julian Reschke
> Cc: Larry Masinter; www-tag@w3.org
> Subject: Re: closing IRIEverywhere
> 
> Julian Reschke writes:
> 
> > On 21.04.2010 17:23, Henry S. Thompson wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Larry Masinter writes:
> >>
> >>> 1.  Develop a draft of what a replacement to [LEIRI] would look
> like,
> >>> given the current content of IRI-BIS. Coordinate with IRI-WG if
any
> >>> changes are needed to IRI-BIS, and continue to track IRI-WG.
> >>
> >> What specific document should we be looking at?  It is not
obvious
> >> - From your message.
> >> ...
> >
> > <http://tools.ietf.org/html/draft-ietf-iri-3987bis-00> would be my
> guess.
> 
> That was my guess, but that has not changed much if at all from the
> version LEIRIs was based on, and my understanding was that the
IRI-WG
> had moved rather further since then.  If that is the case, there is
no
> point starting from an about-to-be-superseded document. . .

Received on Tuesday, 4 May 2010 05:57:20 UTC