Add issue marker for extension point reservation discussion

[OR13]

---

Preview | Diff

[OR13]

See #1142

[TallTed]

"Holder binding." The misnomer that will not die.

[msporny]

I thought the WG agreed to reserve confidenceMethod and point to the CCG work item? This issue marker deviates from how all of the other properties are being reserved (in that, confidenceMethod is not being reserved and the issue marker text makes a broad declaration about how properties are being reserved -- lowering the bar for property reservation). To be clear, I'd be fine w/ a lower bar, but this lower bar isn't where the WG landed.

Specific changes requested: align the way confidenceMethod is being reserved to the same way that the other properties are being reserved. (or, specify why confidenceMethod is being treated differently).

EDIT: It looks like PR #1141 is doing this, which obviates the need for this PR?

[decentralgabe]

agree with @msporny I thought we had consensus on confidenceMethod. is there an anti-reserve list 🙃

[TallTed]

Maybe we can agree to change all mentions of the misnamed holder binding, because it doesn't do any such thing, to something like authorized presenter list, which would do exactly what it says on the tin, i.e., it would provide verifiers with a list of holder identifiers against which the presenting holder's identifier could be tested, which I'm confident could be implemented in a privacy-preserving, crypto-involving manner?

[iherman]

The issue was discussed in a meeting on 2023-06-14

• no resolutions were taken

View the transcript

1.1. Add issue marker for holder binding (pr vc-data-model#1141)

See github pull request vc-data-model#1141.

Michael Prorock: suggest we merge first, bikeshed naming and properties second.

Dave Longley: this is not bike shedding, its data modeling... in the information graph.
… id is a special property that has specific behavior.
… because of JSON-LD this could impact selective disclosure.
… its not just about picking a name.

Kristina Yasuda: ask for a special topic call if you need it.

Manu Sporny: its not bikeshedding, there are design considerations that effect JSON-LD selective disclosure.
… the SRI format is different, its not what SRI does... we should either align with SRI or align with something else.
… there are design considerations that effect selective disclosure in JSON-LD nquads.

Ivan Herman: See Subresource integrity spec:.

Manu Sporny: I am reviewing the PR now.
… people are requesting discussion.

Orie Steele: You're open to open a PR to follow best practice.

Orie Steele: AFAIK there is no bar, right now.

Orie Steele: no consensus on any bar afaik.

[OR13]

@msporny please re-review, I have merged your change suggestion.

[msporny]

Editorial, multiple reviews, changes requested and made, no objections, merging.