We do have some relevant assets: The Open API certifications awarded table can be filtered to show which vendors have certified which Open APIs. The APIs are mapped to ODA Domains (Engaged Party, Customer, Product, Service, Resource…) which typically ...
Thanks Jonathan. Actually I was referring to the AIops specs that referred to Machine being a Party. Nonetheless, do you still plan to refer to the consumer of the permission as a user? PS: Just noticed that you have defined a user as the receiver ...
Hi Dan Machines are not party/party roles. We plan to add resource/resource roles as receivers of permissions, to allow for use cases such as ODA components or home gateways needing rights. If you have access to the project jira repository feel free ...
Hi Jonathan Regarding the review of the v5 Roles & Permissions spec, it seems that the permissionSet resource is using a "user" field instead of "grantee". Presumably the "granter" can assign permissions to other party/party roles including machines ...
Hi John, thank you for your feedback. Several weeks sound like a major changes are being made. However, if major changes will be going to happen, then not only we as the API provider but our API Consumer must also adjust the API-changes. Anyhow, it's ...
#General
To join this Community you need to work for a TM Forum Member company.