Orie Steele

thanks @brentzundel I agree.... I propose we handle this as follows: 1. create a ccg work item that works to unify verifiable credentials and https://github.com/w3c-ccg/zcap-ld 2. setup a w3id.org namespace...

I would love to see this happen... forcing term redefinition is an act of strategic sabotage :) Developers who first encounter linked data will spend years trying to figure out...

+1 for a call, this is blocking a number of thing I care deeply about :)

@VladimirAlexiev I am not suggesting nobody use `@version 1.1` :) I am suggesting that the base v2 context not use it.. and let EPCIS or trace or schema.org decide if...

@VladimirAlexiev I think I completely agree, but let me restate in my own words. DID and VC contexts should not require 1.1 since they just define terms and don't bundle...

> The `@protected` feature from 1.1 is a hard requirement. It ensures that you can do a simple string comparison on context URLs without having to do processing -- and...

I think defaulting is probably slightly better than dropping properties, but throwing an error remains the best thing to do here. The question remains, why would you sign anything you...

@tplooker and I had a chat about this... I can see the advantage of "making the tent bigger" by welcoming folks who don't understand why signing unknown properties might not...

If we are talking about a spec where we get to make normative requirements, I would repeat my assertions: 1. JSON-LD Processors SHOULD throw an ERROR 2. JSON-LD Processors MUST...

1. `@vocab` being used indicates a potential security issue that at least should yield a warning. 2. `@vocab` is useful for folks who like seeing warnings instead of errors in...