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] XRI Names and XRI Addresses


Does this beg the question of what XRI Non-permanent addresses are? By adding the modifier in there, you imply that this phrase is a subset of a larger set (ie addresses, both permanent and non-permanent).

I'm not totally convinced the use of permanent in the middle is more confusing than helpful. 

If you want to connote permanentness, ID is the correct phrase (as had been in XNS). If you want to connote machine routability, then address is probably the correct phrase. 

You want to suggest that XRI URNs are both. I'd argue that the routing part is slightly more important if you had to focus on emphasizing one feature over the other (ie without the modifier in the middle). This is because the routability/resolvability is a unique feature in the URN space, whereas permanence isn't. 

So I guess I'm -1 on the proposal to add "permanent" in the middle. 

	-Gabe

> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@onename.com]
> Sent: Monday, May 05, 2003 11:37 AM
> To: xri@lists.oasis-open.org
> Subject: [xri] XRI Names and XRI Addresses
> 
> 
> I had an action item to raise the issue in the v4 Requirements doc of
> the introduction of the terms "XRI Name" and "XRI Address". In this
> draft we only used these terms in the first half of the Motivations
> section, but in the final draft (and most importantly, in the spec
> itself), we should use them consistently throughout.
>  
> These terms were proposed by Dave Wentker as "human-friendly
> identifiers" for what we have been referring to technically 
> as XRI-URIs
> and XRI-URNs. The reason is that with coming of a formal spec, we will
> need to begin communicating with a much larger audience about 
> the major
> features of XRIs, and one of them is that XRIs provide a 
> standard syntax
> for both reassignable, human-friendly abstract identifiers and
> persistent, machine-friendly abstract identifiers. So we need clear,
> consistent, understandable terms for both layers.
>  
> Please post any thoughts you have about standardizing on these terms.
>  
> My one suggestion after chewing on this over the weekend is that we
> might want to use the modifier "persistent" when talking about XRI
> addresses because that is what so significantly distinguishes 
> them from
> IP addresses (or any form of name, whether a DNS name or an XRI name).
> So from an Internet resolution standpoint the four possible 
> layers would
> be:
>  
> * XRI name
> * XRI persistent address
> * DNS name
> * IP address
>  
> You can skip a layer any time a resource doesn't need the features of
> that layer, i.e., an XRI name can refer directly to a URI or an IP
> address if the resource does not need a persistent 
> identifier, or an XRI
> persistent address can refer directly to an IP address if it doesn't
> need a DNS name.
>  
> =Drummond 
>  
> 


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