You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly in general I'm not clear why anti-requirement's exist. The list of "anti-requirements" is never ending task to maintain what shouldn't be implemented.
Secondly, it seems that authoirzation history is supported in the API using the /entities/{entityVID}/authorizations endpoint
Thirdly, if it is can a rationale be shared. A history can still be constructed using multiple calls to the TRP
Finally If the working group decides to retain then I think the language can be clarrified as reading through the spec the reference to "history" implied a list of authorizations but its never clearly stated
[AR-1] SHALL NOT support query operations returning a historical list of authorizations for a [registered entity](https://trustoverip.github.io/tswg-trust-registry-protocol/#term:registered-entity).
The text was updated successfully, but these errors were encountered:
Firstly in general I'm not clear why anti-requirement's exist. The list of "anti-requirements" is never ending task to maintain what shouldn't be implemented.
Secondly, it seems that authoirzation history is supported in the API using the
/entities/{entityVID}/authorizations
endpointThirdly, if it is can a rationale be shared. A history can still be constructed using multiple calls to the TRP
Finally If the working group decides to retain then I think the language can be clarrified as reading through the spec the reference to "history" implied a list of authorizations but its never clearly stated
The text was updated successfully, but these errors were encountered: