Tobias Looker

Interested in feedback and thoughts from @msporny @dlongley @OR13

Another option we discussed, is for the default vocab to be defined as a security term that in present in both the credentials and security context and therefore making it...

@peacekeeper I understand that it appears as a contradiction. To be clear I think in general JSON-LD processors SHOULD at least emit a warning when any property is expanded with...

This issue goes right to the core of the extensibility model for verifiable credentials. If we look at neighbouring technologies such as JWT they support what are known as [public...

I also dont think a signed property that has been expanded to an IRI of `https://www.w3.org/2018/credentials/undefinedTerm#someClaim` that when dereferenced clearly states to the user "Hey this property is not formally...

> I do think making changes to the VC Data Model in this regard would be helpful, but I would formally object to swallowing undefined terms by adding @vocab without...

Ok so can we clarify the intended behaviour here, e.g in ANY case of using `@vocab` for expansion, whether it be the default one (or not as people are saying...

> If you want to address this in a secure way, you should consider doing something like X.509 with its critical extension feature. With this feature, every attribute at the...

Or better still `if (term.type == https://www.w3.org/2018/credentials/undefinedTerm)` its unknown

> All defined schema terms are implicitly critical. This is the current implied meaning of the W3C recommendation. So in this model you are saying that all properties in a...