OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xri] [Fwd: Fwd: Protocol Action: 'InternationalizedResourceIdentifiers (IRIs)' to Proposed Standard]


yes.

but it should not take _that_ long for it's issuance, afaics.

--- peterd

On Wed, 2004-12-08 at 16:51, Drummond Reed wrote:
> At what point does this become referenceable, i.e., does the RFC have to
> issue first?
> 
> =Drummond 
> 
> -----Original Message-----
> From: Davis, Peter [mailto:peter.davis@neustar.biz] 
> Sent: Wednesday, December 08, 2004 10:16 AM
> To: XRI List
> Subject: [xri] [Fwd: Fwd: Protocol Action: 'Internationalized
> ResourceIdentifiers (IRIs)' to Proposed Standard]
> 
> FYI... IRI now RFC status
> 
> --- peterd
> 
> -----Forwarded Message-----
> > From: Paul Hoffman / IMC <phoffman@imc.org>
> > To: public-iri@w3.org
> > Subject: Fwd: Protocol Action: 'Internationalized Resource Identifiers
> (IRIs)' to Proposed Standard
> > Date: Wed, 08 Dec 2004 08:36:47 -0800
> > 
> > 
> > OK, now it's "really real". It will take many months for an RFC to 
> > issue, but it is now a standard. Congrats to all.
> > 
> > --Paul Hoffman
> > 
> > >X-test-idtracker: no
> > >From: The IESG <iesg-secretary@ietf.org>
> > >To: IETF-Announce <ietf-announce@ietf.org>
> > >Date: Wed, 08 Dec 2004 09:55:16 -0500
> > >X-Spam-Score: 0.0 (/)
> > >X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
> > >Cc: Internet Architecture Board <iab@iab.org>,
> > >         RFC Editor <rfc-editor@rfc-editor.org>
> > >Subject: Protocol Action: 'Internationalized Resource Identifiers
> > >  (IRIs)' to Proposed Standard
> > >X-BeenThere: ietf-announce@ietf.org
> > >X-Mailman-Version: 2.1.5
> > >List-Id: ietf-announce.ietf.org
> > >List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
> > >	<mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
> > >List-Post: <mailto:ietf-announce@ietf.org>
> > >List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
> > >List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
> > >	<mailto:ietf-announce-request@ietf.org?subject=subscribe>
> > >Sender: ietf-announce-bounces@ietf.org
> > >
> > >The IESG has approved the following document:
> > >
> > >- 'Internationalized Resource Identifiers (IRIs) '
> > >    <draft-duerst-iri-11.txt> as a Proposed Standard
> > >
> > >This document has been reviewed in the IETF but is not the product of an
> > >IETF Working Group.
> > >
> > >The IESG contact person is Ted Hardie.
> > >
> > >Technical Summary
> > >
> > >This document describes Internationalized Resource Identifiers and their
> > >relationship to URIs.     While the character limitations of URIs are not
> > >usually an issue for protocol processing, they may restrict the
> usefulness of
> > >the identifiers presented to end users or systems expecting a 
> > >different range of
> > >characters.  Rather than extend URIs, this document introduces a 
> > >new identifier
> > >type and a describes a relationship to URIs.    Within an IETF context,
> IRIs
> > >will likely be  used as presentation elements.  There are cases, such as
> XML
> > >namespaces, in which an IRI may be used as a token, because
> > >character-by-character equivalence is the only property used for protocol
> > >processing.  In no case should an implementor assume that an IRI may be
> > >substituted for a URI in an existing protocol grammar; either the
> generative
> > >grammar associated with the protocol must be updated to specify IRIs or
> the
> > >implementation must transform an IRI into a URI before use.
> > >
> > >Working Group Summary
> > >
> > >This work was initiated in the W3C, and it has been broadly accepted in
> that
> > >context.  It has also been discussed on the URI mailing list and a 
> > >public, open
> > >list (public-iri@w3.org) dedicated to the topic.  Considerable care has
> been
> > >taken to keep this specification well-synchronized with the URI
> specification.
> > >There were issues raised during IETF Last Call, and a new document
> version
> > >resolving those issues was submitted.
> > >
> > >
> > >_______________________________________________
> > >IETF-Announce mailing list
> > >IETF-Announce@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/ietf-announce
> > 
> > 
> > --Paul
> > 
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the
> OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/xri/members/leave_workgroup.php
> .
> 
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xri/members/leave_workgroup.php.
> 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]