Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Entity Authorizations in OpenAPI spec. #68

Open
andorsk opened this issue Sep 9, 2024 · 1 comment
Open

Clarify Entity Authorizations in OpenAPI spec. #68

andorsk opened this issue Sep 9, 2024 · 1 comment
Assignees

Comments

@andorsk
Copy link
Contributor

andorsk commented Sep 9, 2024

Additional language around https://github.com/trustoverip/tswg-trust-registry-protocol/blob/main/api/toip-tswg-trustregistryprotocol-v2.yaml#L74C1-L75C1 and https://github.com/trustoverip/tswg-trust-registry-protocol/blob/main/api/toip-tswg-trustregistryprotocol-v2.yaml#L113 would be appreciated to delineate the differences between the two. They both return AuthorizationResponseListType and the summaries are the same: Determine whether an Entity has a particular Authorization. It is unclear what the purpose of the two endpoints are vs. having a single endpoint.

@andorsk
Copy link
Contributor Author

andorsk commented Nov 7, 2024

Thoughts here that were discovered over IIW: To prevent collisions, I'm leaning toward the authorizations data model MUST be referenced by an globally unique identifier. A DID is sufficient for this, but probably any globally unique identifier is sufficient.

The uniqueness attribute is required to prevent authorization namespacing collisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants