Closed decentralgabe closed 2 years ago
Short answer would seem to be that object can be extended.
When writing specs with JSON, prefer objects to arrays or strings, since you can add properties to fix issues that might arise in the future.
eh, premature optimization. it's a similar amount of work either way.
I vaguely recall the conversations that resulted in the value being an object with a directive
property than simply a value, but I can't recall the exact reasoning why that decision was made.
I'm fine either way.
The reasoning here was that it was likely that you would need to specify which mechanisms you would accept for status checks, not just the actual high-level status value they must be. The addition of which mechanisms are acceptable, with any annotation required to note them, would require at least one additional property. This is admittedly a forward looking structure, but I don't know how else you would do this without allowing for more props as methods for revocation checks become common enough to distinguish between.
Discussed on the call today: we will extend the field to add a type
property a-la StatusList2021
Fixed in #328
https://identity.foundation/presentation-exchange/#credential-status-constraint-feature
The spec says:
Why objects if they contain a single key and a single value? What about...