- From: Markus Sabadello <markus@danubetech.com>
- Date: Tue, 10 Nov 2020 10:10:25 +0100
- To: public-did-wg@w3.org
This is great, thanks Amy and others for your efforts..! It seems there is a small difference in how the JSON-LD terms are defined in the DID and AS contexts: https://github.com/w3c/did-spec-registries/pull/133/files https://github.com/w3c/activitystreams/pull/512/files The former explicitly sets "@container": "@set". I know that unordered arrays are the default in JSON-LD anyway, but I wonder if there are edge cases where a JSON-LD processor would behave differently? Markus On 09.11.20 17:41, rhiaro wrote: > Hi all, > > The DID WG had an opportunity to collaborate recently with the Social > Web Incubator Community Group, and I'm happy to report that our joint > mission has been a success. > > This is with respect to the `alsoKnownAs` property, something which has > been in use by various ActivityPub implementations for some time, but > was an extension rather than a core part of their stack of RECs. Members > of the DID WG and implementers from the ActivityPub community worked > together to refine the definition of `alsoKnownAs` that appears in the > DID Core spec to make sure it is suitable for both communities, and at > the weekend the Social Web Incubator CG passed a formal resolution to > add `alsoKnownAs` into the ActivityStreams 2.0 namespace (and > corresponding JSON-LD context) with a link out to the human-readable > definition in DID Core [1]. > > It's always nice when groups with similar goals and interests can work > together to share a vocabulary and reduce redundancy in the space. > > Thanks everyone! > > Amy > > [1] https://www.w3.org/ns/activitystreams > > >
Received on Tuesday, 10 November 2020 09:10:42 UTC