Skip to content

Getting to a REC #135

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.

Sign up for GitHub

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

Jump to bottom
Closed
decentralgabe opened this issue May 3, 2023 · 0 comments
Closed

Getting to a REC #135

decentralgabe opened this issue May 3, 2023 · 0 comments
Assignees
@decentralgabe @OR13

Comments

@decentralgabe
Copy link
Collaborator

We're on the W3C Recommendation Track.

This issue serves as a place to plan to get from our current state (ED) to a REC.

Action Items

  • Progress the spec to maturity (all other open issues)
    • Move to FPWD. As of today (May 3 2023) we are close, and probably 1-2 PRs away
    • Move CR and CRD. After some time (let's say a month) at FPWD we can try to move to CR.
    • Move to PR. This step requires formal review from the W3C AC.
    • Move to REC
  • Have two independent implementations. We have one at TBD. Another is being built by Transmute, so we're good here.
  • Have a test suite. Need work here: Test suite #134
  • We need to be able to normatively reference JSON Schema Being able to normatively reference JSON Schema #133
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@decentralgabe decentralgabe

@OR13 OR13

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@decentralgabe @OR13