Dave Longley

I think we've got a tooling problem -- not a spec problem here. We need better tools that make things easier for people to check their vocabularies, figure out what...

`Presenter` (instead of `prover`) may provide a wider scope to capture more use cases and better match with the fact that they are "presenting".

Yes, the value of `cred:verifiableCredential` should be a graph which contains a VC. This is important for containerizing/isolating statements so one can determine their origin and properly recompute their hashes...

@TallTed, > Are you saying that, in RDF Dataset Canonicalization, "the data being signed" is always in the default graph, and not in a named graph? No, this is unrelated...

@TallTed, > "The default graph" seems not to be the correct label for all of the above instances, and even if it were, in Virtuoso (for instance), you cannot "remove...

@sbutterfield, > If the proof graph(s) are always decoupled during signing, then the metadata about the signature generation is not part of the signature? I think responding to individual concerns...

@TallTed, The canonicalized meta data is hashed producing `hash1`. The canonicalized dataset (with any existing proofs in the default graph removed when using "proof sets") is hashed producing `hash2`. The...

>You don't need to re-alias `"id": "@id"` or `"type": "@type"` ... it's already done in the base context, IIRC. No, you *DO* need to realias. The reason is because your...

@David-Chadwick, The example context shouldn't be used by anyone in a production system. It only has terms in it that are "bogus", for lack of a better term. All the...

@agropper, > I can share a link secret or private key with anyone I want. If the reputation associated with the private key is semi-disposable, I can do that without...