RE: [xri] RE: [xdi] Global Cross-Reference Proposal

["Drummond Reed" <drummond.reed@cordance.net>]

Les, you're right that in both @cordance=drummond and @cordance*(=drummond),
you can infer a semantic relationship between the subsegments (@cordance and
=drummond) and their global XRIs.

However, in the latter case, I think the only interpretation you can infer
is that the entity being referred to by *(=drummond) is being referred to IN
A DIFFERENT CONTEXT than =drummond.

The rationale is the same as the example I gave in natural language on the
wiki page, which is when quotes are used in English to explicitly
communicate that a particular word/phrase is being used in "quotes",
specifically what are called "scare quotes" (thanks to John Bradley for
educating me about that phrase). There's a good Wikipedia article on scare
quotes:

	http://en.wikipedia.org/wiki/Scare_quote

The example I used on the wiki page was:

	Boeing "international" employment contract signature date

In that phrase, the only thing an English reader can interpret about the
word "international" is that it is being used in a different context than
the normal use of the word. I think it's safe to say that in order to
understand what context applies (and therefore what the word really means in
that context), you have to look either at the immediate context of the full
sentence, or the full paragraph, or the full context in which it appears. 

Which is exactly the meaning of "local context symbols" in XRI.

Therefore the following line up nicely:

	Boeing "international" employment contract signature date
	@boeing*(+international)+employment$contract$sig$d

...and...

	Boeing international employment contract signature date
	@boeing+international+employment$contract$sig$d

I don't think there's any more semantics that can be interpreted from the
difference. However I think you can see why the issue is so important to XRI
3.0 -- in XRI 2.0 the _only_ cross-reference that can be expressed in the
"scare quote" version, whereas in normal natural language (as in typical XDI
RDF), it's the global cross-reference version that's needed.

Hope this helps,

=Drummond 

> -----Original Message-----
> From: Chasen, Les [mailto:les.chasen@neustar.biz]
> Sent: Friday, November 07, 2008 8:30 AM
> To: Drummond Reed; OASIS XRI TC
> Cc: OASIS - XDI TC
> Subject: [xri] RE: [xdi] Global Cross-Reference Proposal
> 
> I still do not understand how @cordance=Drummond and
> @cordance*(=Drummond) differ.  I understand you are saying that one is
> global and the other is local but they are both cross references to
> =Drummond.  In both cases the definition behind =Drummond comes from
> @cordance.
> 
> 
> > -----Original Message-----
> > From: Drummond Reed [mailto:drummond.reed@cordance.net]
> > Sent: Friday, November 07, 2008 2:54 AM
> > To: 'OASIS XRI TC'
> > Cc: 'OASIS - XDI TC'
> > Subject: [xdi] Global Cross-Reference Proposal
> >
> > I finally had time tonight to complete the writeup of the Global
> > Cross-Reference proposal for XRI Syntax 3.0. This is based mostly on
> > requirements from the XDI TC that go back to the dawn of the XDI RDF
> > model.
> > We have been discussing them on our last few weekly telecons in order
> > to
> > document them in detail before the XRI TC F2F next week.
> >
> > The full proposal is written up at:
> >
> > 	http://wiki.oasis-open.org/xri/XriThree/GlobalCrossReferences
> >
> > Since this is the proposal with the biggest impact on XRI 3.0 syntax,
> I
> > urge
> > all XRI TC members to read through it and comment on the list.
> >
> > Thanks,
> >
> > =Drummond
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  Follow this link to all your TCs in OASIS at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php