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
It's a bit of an advanced feature, but: shoulders exist to effectively namespace concerns within a NAAN.
In the use case I have, I have largely independent teams maintaining ARKs for different concerns. Therefore it would make sense to restrict authorization to manage ARKs to one or more shoulders within a NAAN.
The text was updated successfully, but these errors were encountered:
It's a bit of an advanced feature, but: shoulders exist to effectively namespace concerns within a NAAN.
In the use case I have, I have largely independent teams maintaining ARKs for different concerns. Therefore it would make sense to restrict authorization to manage ARKs to one or more shoulders within a NAAN.
The text was updated successfully, but these errors were encountered: