RE: [xri-editors] Action item on $ text

["Wachob, Gabe" <gwachob@visa.com>]

Its not "for free" - you still have to manage the @ namespace and grant
@ietf to the organization we know as the Internet Engineering Task
Force. But it is reuse and means we only have to keep track of one
registration.

As I said to Dave on the phone - I really don't have a strong
preference, so I'm fine with $(@ietf)

	-Gabe 

> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@cordance.net] 
> Sent: Monday, January 24, 2005 12:47 PM
> To: 'Dave McAlpin'; Wachob, Gabe; xri-editors@lists.oasis-open.org
> Subject: RE: [xri-editors] Action item on $ text
> 
> Dave's got a good point. The beauty of cross-references is 
> that they just
> work. Nobody has to govern them. If IETF wants to have their own $
> (standards-body-specified XRI) branch, they can "just do it". 
> Neither OASIS
> or anyone else has to "govern" it. (Which strikes home with 
> me - I'm writing
> a paper on XRI registry governance right now.)
> 
> I like Dave's example so much I'd suggest we replace the current text
> explaining how GCS symbols can be used for xrefs (that Dave 
> was moving to
> the Primer) with this one.
> 
> Gabe, do you agree, or are we missing something?
> 
> =Drummond 
> 
> -----Original Message-----
> From: Dave McAlpin [mailto:Dave.McAlpin@epok.net] 
> Sent: Monday, January 24, 2005 9:57 AM
> To: Wachob, Gabe; Drummond Reed; xri-editors@lists.oasis-open.org
> Subject: RE: [xri-editors] Action item on $ text
> 
> But the nice thing about $(@ietf) is that we don't have to 
> maintain some
> kind of external registry of standards group. Don't we just 
> get $(@ietf)
> for free?
> 
> Dave
> 
> -----Original Message-----
> From: Wachob, Gabe [mailto:gwachob@visa.com] 
> Sent: Monday, January 24, 2005 9:52 AM
> To: Drummond Reed; xri-editors@lists.oasis-open.org
> Subject: RE: [xri-editors] Action item on $ text
> 
> This sounds fine to me. 
> 
> Only thing I'd possible change is not using the xref for the standards
> body. We certainly *can* do that, and it has a sort of intellectual
> beauty to it, but as a practical matter I don't see a big advantage of
> $(@ietf) over $ietf 
> 
> 	-Gabe
> 
> > -----Original Message-----
> > From: Drummond Reed [mailto:drummond.reed@cordance.net] 
> > Sent: Friday, January 21, 2005 10:39 PM
> > To: xri-editors@lists.oasis-open.org
> > Subject: [xri-editors] Action item on $ text
> > 
> > I had an action item to propose new text defining the $ GCS 
> > character (and
> > the handling of the $ space).
> > 
> > The following text is in the revised draft I just sent to Dave:
> > 
> > Symbol Character: $
> > 
> > Authority Type: Standards body
> > 
> > Establishes Global Context For: Identifiers established by 
> > other XRI TC
> > specifications (such as the XRI Resolution Specification and 
> > XRI Metadata
> > Specification), other OASIS specifications, or (using 
> > cross-references)
> > other standards bodies.
> > 
> > This is as precise a way as I can find to state following policy for
> > managing the $ namespace:
> > 
> > 1) It is intended for standards bodies - really a special 
> > subset of the "+"
> > space where identifiers are specified intentionally rather 
> > than organically.
> > 
> > 2) OASIS Technical Committees may create specifications that 
> > "register"
> > identifiers in the $ space directly. This means that OASIS is 
> > "informally"
> > responsible for managing the native $ space on a "first-come, 
> > first-served"
> > basis, but only to the extent that two or more OASIS 
> > specifications propose
> > to register the same $ identifiers at the same time (a pretty remote
> > possibility to begin with, and one that is very easily 
> handled anyway
> > through the lengthy specification review process). Management 
> > of this space
> > gets even easier since the XRI Metadata spec will reserve all
> > single-character identifiers for the XRI TC.
> > 
> > 2) The $ space is also available to any other standards body 
> > simply by using
> > the standard extensibility mechanism for all XRIs: 
> > cross-references. For
> > example, "$(@OMG)", "$(@IETF)", etc.
> > 
> > I believely this cleanly handles the entire issue.
> > 
> > =Drummond 
> > 
> > 
> > 
> > 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-editors/membe
> > rs/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-editors/membe
> rs/leave_w
> orkgroup.php.
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.302 / Virus Database: 265.7.2 - Release Date: 1/21/2005
>  
> 
> 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-editors/membe
> rs/leave_workg
> roup.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-editors/membe
> rs/leave_workgroup.php.
> 
>