1 of 7

W3C WG Joint Meetings

WoT WG - DID WG

W3C TPAC 2020

WoT WG - DID WG Joint Meeting

2020-10-13

2 of 7

Agenda

Status Updates

Wot Discovery

WoT Security

Next Steps

W3C TPAC 2020

WoT WG / DID WG Joint Meeting

2020-10-13

3 of 7

WoT WG Status Update

Current status of WoT WG including work items over last 12 months.

Deadlines in next 3 months and needs from the DID WG.

Areas of collaboration over the next 12 months.

Any other areas of discussion, interest, focus for the meeting today?

1

2

3

4

4 of 7

DID WG Status Update

Last 12 months: Focus on DID Core, core cryptographic features (authn, authz, issuance), abstract data model, serialization representations (JSON, JSON-LD, CBOR), and DID Specification Registries (extensibility)

Call to transition to Candidate Recommendation expected in November for DID Core and DID Specification Registries.

Interest in cryptographic features provided by DIDs, VCs, and their use for WoT. Interest in DID Methods for WoT devices.

Other technologies used by both groups: JSON-LD, Linked Data Signatures/Proofs, cryptographic registries that establish trust, Verifiable Credentials, etc.

1

2

3

4

5 of 7

Example of a DID document service endpoint pointing to a TD looks good! Additional data can be added to DID documents as extensions.

Link in TD looks similar to DID document service endpoints. How should we standardize link types / service endpoint types? See wot-discovery#65 and wot-thing-description#902.

resolve() for DIDs is defined as an abstract function, which could be implemented locally or using remote resolution services.

did-core#410 is proposing to add a "type" property to a DID document (there is active discussion on how much data a DID document should expose about the subject).

1

2

3

4

6 of 7

Issue #166: WoT TD Integrity Protection - DID Core removed proof (security provided by ledger), it's optional but can be folded in. Could use DIDs to sign TDs and identify devices?

Issue #166: WoT TD Integrity Protection - Have you considered expressing the information in a Verifiable Credential and then publishing it in a more traditional directory?

Issue #161: Referring to public keys - have you considered did:key? Might work well for constrained environments?

CBOR-LD - Semantically compressed, digitally signed, DID-based TDs and Things?

1

2

3

4

7 of 7

WoT-DID Next Steps

Directory service and type links

Sign TDs/Directory Service - VCs

?

?

1

2

3

4