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 Notes: Monday 2018-03-12


XDI TC Notes


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

Date: Monday, 12 March 2018 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.

ATTENDING

Drummond Reed
Markus Sabadello
Phil Windley
Joseph Boyle

NOTES

AGENDA

Use of DIDs and DID Documents in XDI

After the Rebooting the Web of Trust #6 conference in Santa Barbara last week, Markus wants to discuss new thoughts about how DIDs and DID Documents can be used with XDI.


We considered the following example DID document:


{
 "@context": "https://w3id.org/did/v1",
 "id": "did:sov:WRfXPg8dantKVubE3HX8pw",
 "authentication": {
   "type": "Ed25519SignatureAuthentication2018",
   "publicKey": "did:sov:WRfXPg8dantKVubE3HX8pw#key-1"
 },
 "publicKey": [
   {
     "id": "did:sov:WRfXPg8dantKVubE3HX8pw#key-1",
     "type": "Ed25519VerificationKey2018",
     "publicKeyBase58": "H3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV"
   }
 ]
}


The "publicKey" object could be expressed as follows in XDI:


=!:did:sov:WRfXPg8dantKVubE3HX8pw<#public>[<#key>]<@~0>/&/"H3C2A..."


We discussed several options how the "authentication" object would then reference the "publicKey" object:


Option #1 (Using a #public#key relational arc):


=!:did:sov:WRfXPg8dantKVubE3HX8pw[#authentication]@~0/#public#key/=!:did:sov:WRfXPg8dantKVubE3HX8pw<#public>[<#key>]<@~0>


Option #2 (Using $ref):


=!:did:sov:WRfXPg8dantKVubE3HX8pw[#authentication]@~0<#public><#key>/$ref/=!:did:sov:WRfXPg8dantKVubE3HX8pw<#public>[<#key>]<@~0>


Option #3 (Using $has):


=!:did:sov:WRfXPg8dantKVubE3HX8pw[#authentication]@~0/$has/=!:did:sov:WRfXPg8dantKVubE3HX8pw<#public>[<#key>]<@~0>


We agreed that the first option most closely mirrors the JSON-LD/RDF pattern, but that the reference pattern and aggregation pattern could also be used.

Spring Conference Reports and Planning

In addition to Rebooting the Web of Trust, Drummond just attended the second RegTech@Wharton event in Philadelphia, and later this month is KNOW Identity Conference in Washington D.C. followed by Internet Identity Workshop in Mountain View the first week of April. We’ll recap what we’ve learned so far and plan for XDI at those next conferences.

NEXT REGULAR CALL

The next call will be next week at the usual time (Monday 9AM PT). The link 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]