URI -> IRI for JSON-LD Processing about ssi HOT 2 CLOSED

Our JSON-LD code uses IRIs. But our VC and DID code uses mostly URIs and URLs, reflecting vc-data-model and did-core. It's not clear to me if/when conversion should be done between URIs and URLs. The only mention I find of this is in the context of JSON-LD is regarding the profile parameter of the application/ld+json media type. That profile parameter is used in did-resolution but only in a hard-coded way. I did a quick test with two other verifiers using a VC with percent-encoding in the credential subject id, and both verified. This leads me to believe that the implementations are not converting the URI to an IRI (which would remove the percent encoding) but using it as a an IRI as-is, or that it was actually an IRI to begin with, and maybe would only be converted to a URI when resolving it (e.g. over HTTP(S)).

from ssi.

I'm okay leaving this implementation-supported peculiarity for now. We can revisit if we run into encoding issues in the future, or as we factor out the Linked Data functionality into its own project. Thanks for the comprehensive answer.

from ssi.