[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS Standard submission for XRI Syntax 2.0
Mary: On November 14, 2005, the XRI TC unanimously approved XRI Syntax 2.0 Committee Draft 02 as a Committee Specification. On behalf of the XRI TC, we are pleased to submit XRI Syntax 2.0 Committee Specification 01 to the membership of OASIS for consideration as an OASIS Standard. This email serves as our submission and has been copied to the XRI TC mailing list. We list each of item required for submission under the headings in section 3.4 of the OASIS TC process document (http://www.oasis-open.org/committees/process.php#3.4). ********************* a) Links to the approved Committee Specification in the TC's document repository, and any appropriate supplemental documentation for the specification, both of which must be written using the OASIS templates. RESPONSE: PDF format: http://www.oasis-open.org/committees/download.php/15377/xri-syntax-V2.0-cs.p df HTML format: http://www.oasis-open.org/committees/download.php/15376/xri-syntax-V2.0-cs.h tm Word format: http://www.oasis-open.org/committees/download.php/15375/xri-syntax-V2.0-cs.d oc ********************* b) The editable version of all files that are part of the Committee Specification; RESPONSE: Word format: http://www.oasis-open.org/committees/download.php/15375/xri-syntax-V2.0-cs.d oc ********************* c) Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference, including fragments of such, are well formed, and that all expressions are valid; RESPONSE: The XRI Syntax 2.0 specification does not include any XML schemas, only identifier syntax specified using ABNF. To the best of our knowledge, all ABNF productions are well formed and valid. ********************* d) A clear English-language summary of the specification; RESPONSE: XRI Syntax 2.0 specifies the normative syntax for a new type of identifier called an XRI (Extensible Resource Identifier). XRIs are referred to as "abstract identifiers" because they are intended to identify a resource independent of any particular concrete representation of that resource on the network (i.e., a particular network location, domain, directory, website, database, application, etc.) XRIs build on the foundation of interoperable Web identifiers established by URIs (Uniform Resource Identifiers, RFC 3986) and IRIs (Internationalized Resource Identifiers, RFC 3987). Just as the IRI specification created a new identifier by extending the unreserved character set allowed in generic URIs, and defined rules for transforming IRIs into valid URIs, the XRI Syntax 2.0 specification creates a new identifier by extending the syntax of IRIs and defining transformations of XRIs into valid IRIs (which can then be transformed into valid URIs.) The XRI Syntax 2.0 specification extends IRI/URI syntax in four ways: 1) It allows the internal components of an XRI reference to be explicitly designated as either persistent or reassignable. 2) It allows XRIs to contain other XRIs (or IRIs or URIs), a syntactic structure called "cross-referencing" that allows sharing of identifiers, such as generic identifiers or "tags", across multiple authorities and namespaces. 3) It supports two new authority types in addition to the DNS and IP authorities supported in URI/IRI syntax: a) global context symbols (GCS), single characters that establish the abstract global context of an identifier, and b) cross-references, which enable any identifier to be used to specify an XRI authority. 4) It explicitly supports federated identifiers (both persistent and reassignable) at all levels of hierarchy (not just the authority segment). ********************* e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations; RESPONSE: The XRI Syntax 2.0 Committee Specification 01 builds directly on top of the IETF URI specification (RFC 3986) and IRI specification (RFC 3987). Although XRIs may be employed by any OASIS TC that currently uses URIs or IRIs as identifiers (for example the identification of principals or subjects in security-related TCs such as the SSTC), the only explicit relationship to other TCs within OASIS is with the XDI (XRI Data Interchange) TC, which is developing a generalized mediated data sharing protocol based on XRIs. ********************* f) Certification by at least three OASIS member organizations that they are successfully using the specification; RESPONSE: The following OASIS members have submitted certifications of successful usage: Visa International: http://lists.oasis-open.org/archives/xri/200511/msg00071.html NeuStar: http://lists.oasis-open.org/archives/xri/200511/msg00049.html Epok: http://lists.oasis-open.org/archives/xri/200511/msg00054.html AmSoft: http://lists.oasis-open.org/archives/xri/200511/msg00055.html Cordance: http://lists.oasis-open.org/archives/xri/200511/msg00044.html PlaNetwork: http://lists.oasis-open.org/archives/xri/200511/msg00051.html XDI.ORG: http://lists.oasis-open.org/archives/xri/200511/msg00053.html ********************* g) The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a pointer to an account of each of the comments/issues raised during the public review period(s), along with its resolution; RESPONSE: XRI Syntax 2.0 Committee Draft 01 was submitted for a 30-day public review on March 15, 2005, with a 17-day extension on April 13, 2005. The announcement is available at: http://lists.oasis-open.org/archives/tc-announce/200503/msg00005.html XRI Syntax 2.0 Committee Draft 02 was submitted for 15-day public review on 18 October 2005, ending 2 November 2005. The announcement is available at: http://lists.oasis-open.org/archives/tc-announce/200504/msg00004.html The XRI TC published an accounting of the resolution of the comments/issues raised during these comment periods at: http://lists.oasis-open.org/archives/xri/200511/msg00081.html ********************* h) An account of and results of the voting to approve the specification as a Committee Specification, including the date of the ballot and a pointer to the ballot; RESPONSE: The ballot to approve XRI Syntax 2.0 Committee Draft 02 as a Committee Specification was held via an online ballot commencing November 7 and ending November 14, 2005. The vote was unanimously in favor, with 22 of 23 eligible TC members voting. The announcement of the ballot is published at: http://lists.oasis-open.org/archives/xri/200511/msg00037.html ********************* i) An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC's response to each comment; RESPONSE: There have been no earlier attempts to standardize this specification. ********************* j) A pointer to the publicly visible comments archive for the originating TC; RESPONSE: The XRI TC Comment Archives are available at: http://lists.oasis-open.org/archives/xri-comment/ ********************* k) A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the Committee Specification, which report may include statements regarding why the member voted against the specification or that the member believes that Substantive Changes were made which have not gone through public review; or certification by the Chair that no minority reports exist. RESPONSE: No minority reports were submitted. ********************* Respectfully submitted, Gabe Wachob and Drummond Reed Co-Chairs, OASIS XRI TC
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]