Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "UDI"
(→Description) |
(→Changes required in UDI spex for CDM 2.0 =) |
||
Line 10: | Line 10: | ||
* For more information see: http://www.azigo.com/company/dev/udi/ | * For more information see: http://www.azigo.com/company/dev/udi/ | ||
− | == Changes required in UDI spex for CDM 2.0 === | + | === Changes required in UDI spex for CDM 2.0 === |
* Need to eliminate non HTTP(S) scheme XRIs | * Need to eliminate non HTTP(S) scheme XRIs | ||
* Need to "profile" UDIs Global graph conforming UDIs MUST be either: | * Need to "profile" UDIs Global graph conforming UDIs MUST be either: |
Revision as of 12:09, 6 April 2010
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Version
This page describes the concept of UDI as used in the Context Data Model 2.0.
Description
- The datatype of EntityIds, ContextIds and Attributes
- A kind of string.
- May be a URI or XRI.
- For more information see: http://www.azigo.com/company/dev/udi/
Changes required in UDI spex for CDM 2.0
- Need to eliminate non HTTP(S) scheme XRIs
- Need to "profile" UDIs Global graph conforming UDIs MUST be either:
- Absolute (and potentially dereferenceable) or
- Relative to a Context (and thus NOT dereferenceeable).
- (Note: It is currently impossible to tell by inspection whether or not a given entityID is absolute or relative)