Remove evidence

[OR13]

Remove proposed term from v2 context

Addresses #1090

---

Preview | Diff

[msporny]

-1 for the following reasons:

• This term has already been used as an extension point in the VC Specifications Directory.
• It only impacts JSON-LD implementations (and the cost is a handful of bytes for a context that is permanently cached and never downloaded).
• There is active interest in this extension point (as evidenced by the discussion on the calls and the registration of an extension specification).

[iherman]

-1, see #1093 (comment)

[OR13]

As I stated on the call.

If the working group has agreed to this term, as a normative requirement, it should not be reserved, and it should be defined in the TR AND in the JSON-LD context.

We should avoid bundling non normative stuff into the JSON-LD context, since they are cached, they can be split by normative and non normative easily, and then implementers can more easily signal their intention to use experimental extensions.

[dlongley]

-1 This will lead to mistakes because of @vocab being in the core context.

[David-Chadwick]

-1 from me also

[awoie]

-1 from my end as well since OIDF eKYC folks are using it.

[brentzundel]

There does not seem to be a path toward consensus that would result in merging this PR.
I am adding the pending-close label and will close in 1 week if consensus still seems unlikely.

[OR13]

I thought we had agreement, that we would be reserving this URL and term name, and not defining it or using it in the v2 spec?

[msporny]

I thought we had agreement, that we would be reserving this URL and term name, and not defining it or using it in the v2 spec?

Removing the declaration from the v2 context (what this PR dos) is something that we did not have consensus on, and are unlikely to get consensus on it. It's been a week since being marked pending close. Closing.

[martyr280]

we have 2 different implementations of evidence usage both in an open source project and production product.