Orie Steele

@mirceanis non ascii domain names cannot be DIDs.... if the spec needs to be updated to support them we need URL safe bidirectional transformations.

imo, `did:web:example.com/foo:bar` -> `https://example.com/foo:bar/did.json`... no problem here.

yes, that example was a did url with a path that contained a colon. today: > The method specific identifier MUST match the common name used in the SSL/TLS certificate,...

I've seen VC embedded in PDFs a view ways. 1. CBOR-LD / optical encoding via QR code (of content) 2. optical encoding via QR code (of link to content) 3....

See this blog post we did on them a while back: https://medium.com/transmute-techtalk/covid-immunity-badges-dd9b8a05fa86

### A Credential with a Status ```json { "@context": [ "https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1" ], "id": "https://example.com/credentials/23894672394", "type": ["VerifiableCredential"], "issuer": "did:example:12345", "issuanceDate": "2021-04-05T14:27:42Z", "credentialStatus": { "id": "https://example.com/credentials/status/3#94567" "type": "StatusList2021Entry", "statusPurpose": "suspension", //...

This our our CD config, if someone can setup something similar we can easily replace `@transmute` with something else in this repo and have the same kind of convenient CD...

also ping @wyc I believe you were trying to setup something like this before, I grant you permission to experiment on this repo / packages.

@kimdhamilton is this done? i think we can maybe close this.

@nissimsan can you outline a proposal for steel product based on this discussion here?