[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=13107#action_13107 ] 

Alison Macmillan  commented on CMIS-324:
----------------------------------------

-1

We see the key-value pair as a useful way for a repo to share info about the principal. The most useful of these is likely to be which store the principal is stored in. Without this hint, a repo specific CMIS client would have to search all the stores till it finds a match.

We could add a concrete suggestion for the key that must be used to show how this particular  value should be specified. For example cmis.userStore as a key for a value which is an address for the user store that holds the given principal..

> 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