RE: [xri] Groups - Draft XRI 2.0 CD02 Revision Proposal (draft-xri-2-cd02-abnf-v1.doc) uploaded

["Lindelsee, Mike " <mlindels@visa.com>]

I just took a look at the requirements listed for this issue.  They are:

    * To allow empty segments of the path at all levels.
    * To better align XRI with IRI and URI path syntax. 

At the beginning of the year as we were working on XRI 2.0, Gabe and I
argued for exactly these requirements and for allowing empty path
segments in the ABNF.  What I'd like to understand is why these are
requirements now when they were shot down earlier this year.

Mike

>-----Original Message-----
>From: drummond.reed@cordance.net [mailto:drummond.reed@cordance.net] 
>Sent: Thursday, September 15, 2005 11:47 PM
>To: xri@lists.oasis-open.org
>Subject: [xri] Groups - Draft XRI 2.0 CD02 Revision Proposal 
>(draft-xri-2-cd02-abnf-v1.doc) uploaded
>
>This document is referenced by Syntax Issue #2 and #3 on the 
>Syntax change
>management page on the XRI TC wiki at
>http://wiki.oasis-open.org/xri/Xri2Cd02/SynTax/I2ProposedAbnf. 
>Requirements
>are discussed in the document.
>
> -- Mr Drummond Reed
>
>The document named Draft XRI 2.0 CD02 Revision Proposal
>(draft-xri-2-cd02-abnf-v1.doc) has been submitted by Mr 
>Drummond Reed to
>the OASIS Extensible Resource Identifier (XRI) TC document repository.
>
>Document Description:
>This document contains two proposals (including requirements 
>and analysis)
>for revision to the current XRI 2.0 CD01 ABNF. The first aligns XRI and
>IRI/URI ABNF by allowing empty path segments at all levels of 
>the path. The
>second proposes a production to use in the Resolution 
>specification section
>on HTTP proxy resolution for an XRI in HTTP format (HXRI).
>
>View Document Details:
>http://www.oasis-open.org/apps/org/workgroup/xri/document.php?d
ocument_id=14487
>
>Download Document:  
>http://www.oasis-open.org/apps/org/workgroup/xri/download.php/1
4487/draft-xri-2-cd02-abnf-v1.doc
>
>
>PLEASE NOTE:  If the above links do not work for you, your 
>email application
>may be breaking the link into two pieces.  You may be able to 
>copy and paste
>the entire link address into the address field of your web browser.
>
>-OASIS Open Administration
>