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 Notes Unofficial Telecon Monday 2016-08-22

XDI TC Notes

Following are the notes of the unofficial telecon of the XDI TC held on:

Date: Monday, 22 August 2016 USA
Time: 10:00AM - 11:30AM Pacific Time (17:00-18:30 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.


Drummond Reed
Markus Sabadello



Github Repository Support

We did not discuss this topic due to limited call attendance.

XDI Android App

Markus reported that he continues to make progress on the XDI Android app he has been working on, which demonstrates the functionality of XDI link contracts, data sharing, and messaging. Markus is currently focusing on improving the app’s user interface.

DIDs (Decentralized Identifiers), DID Objects, and their Relevance to XDI

We did not discuss this topic due to limited call attendance.

RDF / XDI Compatibility

Markus explored an idea about how to adapt the XDI graph model to RDF in cases where the constraint is to start with the RDF graph model. Markus pointed out that we have always assumed that the mapping of an XDI graph to an RDF graph is:

Markus had the idea that if the constraint is that an implementation must use the RDF graph model, then the XDI graph model could be implemented “on top” of the XDI graph model.

For example, =markus would be a resource and <#email> would be a resource and then the literal would be the email value.

Markus suggested that you can define a profile of RDF that consisted of several key mappings:

  1. A constraint that an RDF graph could have only one predicate for a literal (to maintain the unique addressability).

  2. A single URI representing context.

  3. A single URI representing unique instances (to replace blank nodes).

The end result of this thought process could be a graph model that is 100% compatible with RDF but still makes it possible to use XDI identifiers and XDI syntax.


The next call will be the following week at the usual time (Monday 10AM 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]