[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] RE: [xdi] Global Cross-Reference Proposal
Does @cordance=Drummond and @cordance*(=Drummond) have different
XDI RDF statements. In other emails you seemed to indicate that
@cordance=Drummond has the XDI RDF of @cordance/$has/=Drummond. Does
@cordance*(=Drummond) say something else? I think that introducing this nuanced semantic view into XRI is
confusing. From: Drummond Reed
[mailto:drummond.reed@cordance.net] The distinction between @cordance=drummond and
@cordance*(=drummond) is not purely an aesthetic difference. It is exactly (no
more and no less) than the semantics expressed by the XRI delimiters
themselves: 1) = is a Global Context Symbol. It is an assertion that the
following subsegment is assigned in a global context (specifically, a personal
authority context). 2) * is a Local Context Symbol. It is an assertion that the
following subsegment is assigned in a local context (specifically, a
reassignable local identifier context). 3) ( ) is an encapsulated cross-reference. It is an assertion that
an identifier assigned in one context that is being reused in another context. When presented JUST AS XRIs (meaning outside of an XDI context),
the semantics represented by @cordance=drummond are:
=drummond is a reassignable XRI assigned in a global personal context that is
being reused in the context of @cordance which is a reassignable XRI assigned
in an global organizational context. By contrast the semantics represented by @cordance*(=drummond) are:
(=drummond) is a reassignable XRI cross-reference being reused in the local
context of @cordance which is a reassignable XRI assigned in an global
organizational context. I understand that this distinction may appear to be a small one.
However in the context of XDI it is anything but – it is a completely
different XDI RDF statement. Since XDI RDF is, like all RDF, extremely precise
(for complete machine processability), it is very important to be able to make
each of these statements precisely. =Drummond From: Chasen, Les
[mailto:les.chasen@neustar.biz] I see this as two ways to say the same thing. In both
cases =Drummond is a cross reference to @xpinion. In
Drummond’s proposal I guess one of them refers to =Drummond in scary
quotes and the other doesn’t. Do we really need that? The original reason (and AFAICT the only reason) for this syntax
was aesthetics. I agree it is easier to read and type the more compact
syntax of @xpinion=Drummond. However, inventing a distinction between the
two cross references creates confusion. From: Barnhill, William
[USA] [mailto:barnhill_william@bah.com] So here's a use case that's near and dear to me: Let's say someone has a site that is an XRI/XDI enabled version of
Epinions.com, @xpinions. @xpinions wants to make an assertion about =Drummond
that they control, not that =Drummond controls. Let's say that Drummond is
communitive => @xpionions*(=Drummond)/$is/(+communitive) [Btw, <-
correct? shorter way of stating?] Let's say they also want to reference/pt to a statement that
=Drummond says he's open => @xpinions=Drummond/$is/(+open) Does the above make sense and show need for both? Also is syntax
correct for v3, and is there a more concise way to express it? Thanks, =Bill.Barnhill From: Chasen, Les [mailto:les.chasen@neustar.biz]
I don't see the importance here. You are
introducing a semantic "scare quote" difference between the current
"local" cross references and the proposed "global" cross
references. I find that distinction so very nuanced that it is
confusing. I don't understand why we want to introduce this into XRI. From: Giovanni Bartolomeo
[mailto:giovanni.bartolomeo@uniroma2.it] Thanks Drummond, it clarifies
indeed! Wow, that's a very powerful mechanism! Giovanni, |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]