[OASIS Issue Tracker] Commented: (CMIS-324) Remove bag of key-valuepairs from ACE.Principal

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13111#action_13111 ] 

Florent Guillaume commented on CMIS-324:
----------------------------------------

A simple namespace or prefix seems enough to distinguish between users:
  repo1:bob vs repo2:bob.

Requiring a whole key/value map just to distinguish the provenance of users seems a really heavy weight to put on a client and server implementations. Especially if it has to be sent every time the principal id is sent.

To me having the map seems like a halfway measure because we don't have a principal service that could give out that information. So let's keep it out of the spec until 2.0 where we could define a principal service.


> Remove bag of key-value pairs from ACE.Principal
> ------------------------------------------------
>
>                 Key: CMIS-324
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-324
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> Currently, the ACE construct defined in 2.7.3 includes a key-value pair on each principal in every ACE.  It's use isn't well-defined (e.g. unclear if it's set-able or read-only, or how it's used).
> We should keep things simpler in V1 and not have these. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira