-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add alsoKnownAs property to AS vocabulary #511
Comments
I think the most feasible path forward for this is to:
If it turns out that a lot of the AP community are interested in pushing this forward, we could move the definition from the DID Core spec to the ED of the ActivityStreams Vocab spec, but a timeline on that seems longer and getting it into a new version of the REC even longer still as I think we'd need a new WG for that and nothing like that is on the horizon for SocialCG as far as I know. |
Awesome, thanks for the concrete suggestion @rhiaro -- we'll pass this plan by the W3C DID WG on an upcoming call. |
Should this be documented as a Fediverse Enhancement Proposal even though it is already merged? Additionally, how are changes to the JSON-LD versioned, and relating to the W3C spec? I see people reading the spec and searching for the |
Please Indicate One:
Please Describe the Issue:
The W3C DID WG would like to include the
alsoKnownAs
property to its JSON-LD Context and has heard thatalsoKnownAs
is being actively used in Mastodon for the same purpose as what the DID WG would like to use it for. The issue is that the term has not been registered in the AS Vocabulary. The W3C DID WG PR that is concerned with this issue is here:w3c/did-core#355
We are currently trying to determine if we should mint our own
alsoKnownAs
or build on top of AS 2.0. There is a strong desire to build on top of AS 2.0.The ask would be to add the term to the AS 2.0 vocabulary. We are specifically NOT asking for any changes to the ActivityStreams JSON-LD Context file (nothing disruptive).
If the Vocabulary isn't updated/pushed out as a new TR, we're fine with that as long as there is an ED available via the Web that lists the term (and a future iteration includes the term in the vocabulary).
How can we resolve this issue within a few weeks/months? What's the path forward?
The text was updated successfully, but these errors were encountered: