== Permission & Ownership object ==
We need a generic permission & ownership object which can be added to all service creation and modification requests. The following points needs to be clarified:
* Shall the roles be set during the service creation / modification or on the users resource?
* Is this object always mandatory, or can the roles be defined via some clever inherited default values if missing.
* Which roles are available and can be set on which level
* Do we want to reference the location URI or the UID of a role
* Does anyone have a better name for the <code>roles</code> object? :)
<source lang="javascript">
"roles":
[
{
/* The user 3000000 has the Admin role for this service */
"location": "https://api.example.com/v1/users/3000000",
"role": "Admin"
},
{
/* The user 3000001 has the Admin role for this service */
"location": "https://api.example.com/v1/users/3000001",
"role": "Admin"
},
{
/* The user 3000002 has the User role for this service */
"location": "https://api.example.com/v1/users/3000002",
"role": "User"
The opposite while querying a users resource, for example https://api.example.com/v1/users/3000000
<source lang="javascript">
"roles":
{
[