OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

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

Subject: XDI TC Unofficial Telecon Agenda: Tuesday 9:00 - 10:00AM PT 2016-12-06

XDI TC Agenda

Following is the agenda for the unofficial telecon of the XDI TC held on:

Date: Tuesday, 06 December 2016 USA
Time: 9:00AM - 10:00AM Pacific Time (16:00-17:00 UTC)

The TC operates under a standing rule approved 17 July 2008 under which the TC does not hold regular official meetings and conducts all business by electronic ballot only. Unofficial weekly meetings are held to enable discussion among members but no business is conducted nor actions taken.



Link to join from PC, Mac, iOS or Android:


Or join by phone:

   +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)

   Meeting ID: 925 461 490

   International numbers available:


IRC Channel: irc://irc.freenode.net:6667/xdi


XDI Link Contracts

Drummond has had a number of recent conversations in the emerging self-sovereign identity space about the need for interoperable link contracts. This may an area where the time the TC has spent developing the requirements and semantic design can really pay off. We will discuss the prospect of accelerating the XDI Link Contract spec.

Adding a Fifth Instance Type: Undefined

XDI Core 1.0 Committee Draft 01 currently defines four entity instance types (section 4.2):

  1. Person

  2. Group

  3. Thing

  4. Ordinal (number)

Note that these four categories of entities are completely disjoint, i.e., it is semantically invalid for an XDI entity of one of these types to have an equivalence relation to an XDI entity of a different type.

As Drummond has studied new use cases in connecting XDI to legacy systems as well as to entities identified in RDF graphs, it has emerged that there are many cases where the XDI type of an entity is unknown or undefined, at least at the time of initial integration. Yet such an XDI entity still needs to be identified with an XDI address.

In addition, the entity type may emerge over time, and thus a node established prior to the knowing the type needs to be able to have an equivalence statement to a node created before the type was known.

Therefore Drummond would like to discuss a proposal to create a fifth entity type, “Unknown” or “Undefined”:


The next call will be the following week at the usual time (Tuesday 9AM PT). The link to where agenda items can be posted for the next meeting is: https://docs.google.com/document/d/19oDl0lbb56Grehx2a5flZnhrgnua5l8cVvC_dJ8fTXk/edit?usp=sharing

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