w3c / w3c/json-ld-api

Recommend a way for dependent specs to call into this one, that's not WebIDL

Open
#627 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ms:future-work substantive:class 3
Dominant language
HTML
Stars
106
Forks
40
PR merge metrics
No merged PRs in 30d

Description

In https://github.com/w3c/vc-di-eddsa/issues/100#issuecomment-2607803930, the Verifiable Credentials WG rejected the idea of depending on the JSON-LD spec via its WebIDL interface. To be useful, "library" specifications need a clear way for other specs to depend on them, which those depending specs are willing to use. I think that means that JSON-LD needs to produce such an acceptable interface by the time the AC votes to publish the next version of its REC.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked vc-di-eddsa issue comment and the JSON-LD API specification's current interface documentation. Compare the rejected WebIDL approach with the needs of dependent specifications. Done means the Working Group has an agreed recommendation for an acceptable alternative interface and the issue records it.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.