Re: Service at risk? Was: New CR Snapshot

The service property is represented by at least two implementations in the did-test-suite.

did:ion: https://github.com/w3c/did-test-suite/blob/cff8582/packages/did-core-test-server/suites/implementations/did-ion.json#L21-L28
did:orb: https://github.com/w3c/did-test-suite/blob/cff8582/packages/did-core-test-server/suites/implementations/did-orb.json#L132-L148

Browsing https://github.com/w3c/did-test-suite/tree/cff8582/packages/did-core-test-server/suites/implementations, there looks to be more examples as well.

From: Adrian Gropper <agropper@healthurl.com>
Date: Friday, May 28, 2021 at 3:13 PM
To: Brent Zundel <brent.zundel@evernym.com>
Cc: W3C DID Working Group <public-did-wg@w3.org>
Subject: Service at risk? Was: New CR Snapshot
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Apologies for not paying enough attention. Is service at risk for lack of implementations?

Leaving out service might have significant impact on privacy considerations.

Or maybe I’m being stupid…

- Adrian

On Fri, May 28, 2021 at 3:03 PM Brent Zundel <brent.zundel@evernym.com<mailto:brent.zundel@evernym.com>> wrote:
Greeting DID WG Participants,

Feedback from our first CR has shown that it is possible some normative features may not have implementation support in time for them to be included in our final Recommendation.

The chairs have decided to take the following actions:
Add text to DID Core indicating that the service property is at risk,
Add text to DID Core indicating that the relativeRef property is at risk,
Modify the IANA Considerations section to add text indicating that the entire section is at risk for changes,
Publish a draft of the document with these changes as a new CR Snapshot.

We anticipate the following timeline:
A CR draft of the document with the above changes will be made available to the working group before our meeting on June 1, 2021.
A review period of 7 days will begin as soon as the CR draft is shared with the WG.
WG members will quickly provide feedback on the CR draft to the editors.
During our WG call on June 8, 2021, the CR draft will be presented for a vote to publish as a new CR snapshot.
After the vote to publish, a 28 day countdown will begin during which we continue to seek implementations of the now at risk features and to register our mime types.

Thank you,
Dan Burnett, Co-chair DID WG
Brent Zundel, Co-hair DID WG

This email and any attachments are for the sole use of the intended recipients and may be privileged, confidential or otherwise exempt from disclosure under law. Any distribution, printing or other use by anyone other than the intended recipient is prohibited. If you are not an intended recipient, please contact the sender immediately, and permanently delete this email and its attachments.