decentralized-identity / presentation-exchange

Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission)
https://identity.foundation/presentation-exchange
Apache License 2.0
82 stars 37 forks source link

input descriptor object with no fields? #429

Closed brentzundel closed 9 months ago

brentzundel commented 1 year ago

currently the input descriptor object must contain a constraints object with one of a fields object or a limit_disclosure object. Is there a use case for a presentation definition that only has a limit_disclosure object and no fields? or should this language be updated to make the fields object a MUST?

See https://identity.foundation/presentation-exchange/spec/v2.0.0/#input-descriptor-object

andorsk commented 1 year ago

Discussed on DIF call:

Reasonable point of clarification. Might need some refactoring or different verbiage. There's a few different ways to handle this.

Should try to revisit this by the next milestone.

May shift to Future as we discuss further. Anchoring to milestone 2.1 for now, just to keep things anchored and make sure this is addressed in a reasonable timeframe.

brentzundel commented 10 months ago

since even the type and issuer are represented by fields, it seems that even to show ownership of a certain type of credential without revealing the personal data would still require at least one field. Meeting on 8/24 recommends clarifying that you need at least one field, or at least clarifying the language.

csuwildcat commented 9 months ago

Wording adjusted in https://github.com/decentralized-identity/presentation-exchange/commit/50b335dc28468ac32ad2145bdec71662a20d4504