-
Notifications
You must be signed in to change notification settings - Fork 14
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
Organize at least W3C Recommendations in their own section #27
Comments
I'd be fine for this, but the URL or flare in the table row, seems like they would be enough. |
FWIW, the goal was to improve the understanding about what specifications are W3C vetted. |
The issue was discussed in a meeting on 2023-08-09
View the transcript2.5. Refer to VC-SPECS-DIR for proof types. (pr vc-data-model#1212)See github pull request vc-data-model#1212. Manu Sporny: PR 1212 examples of securing mechanisms in spec. Point to specifications or directory? Need PR about media types? Orie Steele: VCs with some securing mechanisms, with DI proofs; two specs; or media types; This or that language in DM spec. Joe Andrieu: this establishes related specs into a privileged position...
Manu Sporny: securing mechanisms we have vetted here and those not. Anyone can add to specs dir. No review...
Manu Sporny: very dangerous thing; any mechanism...
Joe Andrieu: I think anything does go; people can come up with new crypto; a directory is okay; our mechanisms are published as recs. Sebastian Crane: be careful, don't devalue our (WG) opinion. Kristina Yasuda: safely change to MAY... Manu Sporny: we don't say what has/hasn't been vetted in registry? The VC DM doesn't say what has been vetted.
Manu Sporny: what sections/where to put? Orie Steele: if media types is merge is will be obvious;. See github pull request vc-specs-dir#14.
Manu Sporny: blocking on Kristina PR 14; create media type in specs dir; then merge.
Joe Andrieu: avoid that directory is a registry.
See github issue vc-specs-dir#27. |
Sections for other organizations may also be appropriate.
The text was updated successfully, but these errors were encountered: