I think we just
have a terminological issue here. I agree that a telephone number string can certainly
be used as the relative portion
of a UDI (e.g. the phone number in this UDI: https://example.com/contexts/context100.xrds#617-555-1212
that uses an HTTP URI to get to its XRDS document) to identify an Entity. And when
it is prepended with its containing Context’s id (aka ContextId) we now have
that Entity’s absolute UDI.
[It is also true that Entities can have any number of additional attributes any of which can be
used for queries and thus act as identifiers to distinguish one Entity from
others.]
Without
universal data identifiers (UDIs) (formerly called Higgins
identifiers) there is no “global graph” (or “data web”
as some call this kind of thing, or the “linked data” web that the
semweb folks call it) at all. By requiring that every Entity have a UDI that
persistently identifies it, you can create Entity-to-Entity relationships, correlations,
federation, etc.
See also http://en.wikipedia.org/wiki/Linked_Data for closely related ideas.
From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Anthony Nadalin
Sent: Tuesday, April 22, 2008 4:07
PM
To: Higgins
(Trust Framework) Project developer discussions
Cc: higgins-dev-bounces@xxxxxxxxxxx;
'Higgins (Trust Framework) Project
developer discussions'
Subject: Re: [higgins-dev] I've
updated the HGG wiki and PPT
There should be no identifier defined, this is just an
attribute and the attribute does not have to be a URI or a XRI, this is far too
constraining as it can be a telephone number, etc. Note that an identifier is
not the same as the ContextID or EntityID.
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Paul
Trevithick" ---04/22/2008 02:13:43 PM---Jim,

From:
|

"Paul Trevithick"
<paul@xxxxxxxxxxxxxxxxx>
|

To:
|

"'Jim
Sermersheim'" <jimse@xxxxxxxxxx>
|

Cc:
|

"'Higgins \(Trust Framework\) Project developer
discussions'" <higgins-dev@xxxxxxxxxxx>
|

Date:
|

04/22/2008 02:13 PM
|

Subject:
|

[higgins-dev] I've
updated the HGG wiki and PPT
|
Jim,
The wiki
pages rooted at [1] have now been updated per Higgins
1.1 in three ways. First, the sub-pages all have (or should have) a
“Version” section at the top. Second I have eliminated the 1.0
concept of Entity and changed zillions of places where Node was to now read
Entity. Finally, I’ve update a few of them per our decision to simply use
Entities as complex values. I have also edited the PPT here [2] per the latest
HGG 1.1 model.
I also
renamed “Higgins
Identifier” to “UDI” and expanded its coverage from HTTP URIs
and XRIs to also include support for the semweb community’s “Linked
Data” HTTP URIs. We haven’t yet implemented support for Linked Data
URIs but I think that doing so would allow Higgins
IdAS to be used as a gateway to at least some of the emerging Linked Data data
sources. Parity will be contributing resources to implement this stuff. It will
help the IdAS/Higgins cause WRT both
the partially overlapping semweb and the dataportability crowds.
-Paul
[1] http://wiki.eclipse.org/Higgins_Global_Graph_1.1
[2] http://dev.eclipse.org/viewsvn/index.cgi/org.eclipse.higgins/trunk/doc/org.eclipse.higgins.doc/Higgins-Data-Model-Intro.ppt?root=Technology_SVN&view=co
_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev