Anthony Nadalin
Anthony Nadalin
@David-Chadwick There is no processing requirements of the @context statement, thus there will not be any name clashes unless you are using JSON-LD processing
@David-Chadwick There is absolutely no requirement to understand or do anything with the @conttext per the specification and there are also no "security considerations" listed in the specification that state...
There does not seem to be a clear proposed way to solve the security issues. Need a clear scenario(s) and a PR that we can undestand.
@jcayzac Can you propose a draft specification so we can discuss ?
@Firstyear Can I suggest that you take this over to WebAuthen Adoption Community CG
We have discussed this several times now and have chosen not to proceed down this path.
@emlun To look to see if this is still in play
I don't understand this test " verifiable credential ... To encode a verifiable credential as a JWT, specific properties introduced by thisspecification MUST be either ...3) contained in the JWS...
@David-Chadwick Why do the claim names have to be registered as it's not at all clear in the test that this only applies to the claims that are transformed. It's...
> I don't understand this test > " verifiable credential ... To encode a verifiable credential as a JWT, specific properties introduced by thisspecification MUST be either ...3) contained in...