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] polyarchical -vs- hierarchal


You are still not distinguishing very well the difference between local and global subsegments.  The descriptions you are providing in both cases are local delegations in the context of a parent.  So as Steve keeps asking why doesn’t @ootao*(+west) satisfy the requirement?  If the meaning is different it is unclear how so?  I thought today you were saying that @ootao+west is not a hierarchy but a polyarchy. 

 

 

contact: =les

sip: =les/(+phone)

chat: =les/skype/chat

 

 


From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Thursday, May 03, 2007 12:48 AM
To: Chasen, Les; xri@lists.oasis-open.org
Subject: RE: [xri] polyarchical -vs- hierarchal

 

Les,

 

Actually, in XDI (both the ATI and RDF models), all link relationships are represented as delegations (either *! delegation, or =@+$ delegation) inside a single XRI segment. All hierarchical parent/child relationships are represented as forward-slashes (different segments).

 

When you create a link between two resources, you are naming the arc that connects the two nodes. So for @ootao, you first need a starting node, which is @ (the “arc from nowhere”), and then “ootao” is the link to the next node. The same goes for +west -- + is the starting node, and “west” is the link (arc) to the next node.

 

In @ootao+west, @ is the starting node, “ootao” is the link/arc to the second node, and “+west” is the link/arc to the third node. It is true that + may point “west” to a different node (and different XRD) that @ootao points “+west”. That’s the difference between their contexts. However the purpose of the + namespace is to provide common context (generic identifiers), so the idea is that both +west and @ootao+west point to resources that serve as THEIR representations of the generic subject “west”. In the + dictionary space, this representation should be a definition. In the @ootao space, it could be any resource that @ootao identifies (and wishes others to be able to generically identify) as “west”. Note that if using “+west” all by itself might be ambiguous, @ootao can do the same thing Wikipedia does and add more context (Wikipedia refers to this as “disambiguation” – see http://en.wikipedia.org/wiki/Wikipedia:Disambiguation for a great summary of this.) To do this, @ootao could create XRIs such as:

 

            @ootao+office+west

            @ootao+division+west

 

Hope this helps,

 

=Drummond

 


From: Chasen, Les [mailto:les.chasen@neustar.biz]
Sent: Wednesday, May 02, 2007 8:54 PM
To: xri@lists.oasis-open.org
Subject: [xri] polyarchical -vs- hierarchal

 

Drummond –

 

In a conversation today, you stated, I think, that we need global subsegments so that we can move from simply a hierarchical relationship to a polyarchical one.  I think this means that with the advent of global subsegs we now can move from one hierarchy to another one.   I think in XDI you call these things links.   I thought we support this today through the use of REFs in the XRDS.  Now, I suppose, that you are proposing that we move this notion into the syntax layer.

 

These examples of hierarchical XRIs truly show local delegations.

 

@ootao*west

@ootao*(+west)

 

These examples of polyarchical XRIs demonstrate a global relationship (link)

 

@ootao+west

@ootao+west*steve

 

Is this accurate?  If so, my main heartburn is that since +west in @ootao+west as currently proposed is in the context of @ootao.  This means it could be completely different then the view from +.  If we are really linking to another namespace, +west, we should get +’s view of west not @ootao.

 

Thoughts?

 

 

contact: =les

sip: =les/(+phone)           

chat: =les/skype/chat

 

 



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