Orie Steele
Orie Steele
``` Header set Access-Control-Allow-Origin * Header set Access-Control-Allow-Headers DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified$ Options +FollowSymLinks RewriteEngine on # DID web via redirect # RewriteRule ^did:web:(.+)$ https://did-web.web.app/api/v1/identifiers/did:web:$1 [R=302,L] # http://localhost:8080/did:web:vc.did.ai RewriteRule ^did:web:([a-zA-Z0-9/.\\-_]+)$ https://$1/.well-known/did.json [R=302,L] #...
https://github.com/w3c-ccg/did-method-web/pull/9#issuecomment-799798249
We need to update the universal resolver driver support did web with path based routes, for example: https://did-web.web.app/api/v1/identifiers/did:web:did.actor:supply-chain:manufacturer:stacy ping @awoie @dmitrizagidulin
https://github.com/w3c/did-test-suite/pull/19 ping @awoie
https://github.com/decentralized-identity/c19-vc.com/issues/4 These were experimental examples, don't take them seriously... see the commit history to see how little effort has gone into them.
https://www.imsglobal.org/activity/digital-badges Please include all the necessary items needed for someone to implement a new Open Badges based Verifiable Credential Data Model compliant VC / VP.
With some introductory text, and a direct link to https://ref.gs1.org/gs1/vc/ We might also want to add GS1 as a participant, and have their credentials listed, under credentials of interest.
Reasoning: We originally developed this syntax to blend JSON-LD into JSON Schema. We've gathered a lot of experience with this, throughout this project. I think we have learned the following:...
Picking on GS1 here, but really this applies to any credential with multiple contexts. Here is the problem: We need to validate `@context` before doing JSON-LD processing. We have to...
OSCAL
Can we align any part of it with this work? Is it relevant to evaluating our profile? Are there policy bits that are relevant to workflows? See also https://github.com/oscal-club/examples/pull/16