- From: Orie Steele <orie@transmute.industries>
- Date: Wed, 21 Oct 2020 09:31:08 -0500
- To: Kostas Karasavvas <kkarasavvas@gmail.com>
- Cc: Credentials Community Group <public-credentials@w3.org>
Received on Wednesday, 21 October 2020 14:31:33 UTC
Open an issue like this: https://github.com/w3c-ccg/community/issues/156 If 2 or more companies sign on to support the item, a repo will be created, and then you essentially need to populate that repo with a spec, I prefer to use ReSpec to do that, here is an example: https://github.com/w3c-ccg/traceability-vocab https://w3c-ccg.github.io/traceability-vocab/ OS On Wed, Oct 21, 2020 at 9:25 AM Kostas Karasavvas <kkarasavvas@gmail.com> wrote: > > [skip] > > >>> What is the process of creating such a document (e.g. >>> https://w3c-ccg.github.io/vc-status-rl-2020/). Is it supposed to be >>> stored somewhere globally (e.g. under the VC spec) so that people can >>> easily find them? >>> >> >> Yes, you should describe your revocation mechanism in a spec, so that >> people can implement it themselves, otherwise it's just another vendor >> specific revocation system, I'd recommend doing so in the W3C CCG or some >> other IPR protected space, so that other companies can safely contribute >> and assist. >> >> > What would the process be for a W3C CCG document? (question for anyone > that knows :) > > [skip] > <https://twitter.com/kkarasavvas> > Thanks! > -- *ORIE STEELE* Chief Technical Officer www.transmute.industries <https://www.transmute.industries>
Received on Wednesday, 21 October 2020 14:31:33 UTC