[OASIS Issue Tracker] Commented: (CMIS-724) Users and Groups

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

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

David Churchland  commented on CMIS-724:
----------------------------------------

An objection raised in the latest TC meeting was brought that users and groups are not exclusive to content management and belong outside the CMIS standard.  Maybe users and groups are the wrong words.  In HP Trim we call them Locations, and the Location of a document is very important to a Trim user.  There are a host of relationships that we track between a piece of content and various locations (which may be 'users' who exist in an external directory).  I know that we are not unique in this and that at least one other repository has mapped these 'Locations' as Documents.

If CMIS is better without this then so be it.  I suppose I am motivated by the vision of a person using a CMIS client who can see that something (a person, a group, an organisation?) has a particular relationship with this Document but, because the CMIS client software has not built a Trim specific add-in to retrieve more information all they can see is a cryptic principalId.

> Users and Groups
> ----------------
>
>                 Key: CMIS-724
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-724
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Schema
>            Reporter: David Churchland 
>
> Issue 723 proposes a way to model objecs other than the current four core types.  A prominent theme within that discussion has become the requirement to model users and groups.  I believe the users and groups issue requires a thread of its own, hence this new issue.
> There are two problems I see driving this request:
> 1) Repositories often have internal groups.  t the moment, if a CMIS consumer wishes to apply an ACL to an internal group there is no way for the CMIS consumer to discover that group.
> 2) Documents often have relationships with not only other documents but also people.  These people can not always be represented by a simple string (e.g. a network ID).  I believe we need a way to model a user in CMIS so that we can relate a Document to the person.  For example the Document 'Parking ticket' was issued to the 'Person' Ralph Bellamy.  I kinow it is possible to use cmis:Document to model a person but I think there are problems with this.

-- 
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