[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-724) Users and Groups
[ http://tools.oasis-open.org/issues/browse/CMIS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26722#action_26722 ]
David Churchland commented on CMIS-724:
----------------------------------------
Maybe some scenarios will clarify my thinking...
Using the browser binding and I wish to display the document owner name, I would rather not contemplate consuming LDAP from a web browser.
In a Local council implementation I wish to define a relationship between a resident and a document sent to them. If there was a standard 'cmis:person', which inherited from cmis:custom, then the resident could be defined as a cmis:person.
Irrespective of best practice our customers routinely create groups internal to HP Trim. I would like to be able to do a SELECT * FROM cmis:group. Then use the id of the cmis:group to apply ACLs for that group.
As I said in the last call I initiated this topic in response to the proposal for a custom object type (JIRA 723). If it was possible to create custom object types I would be very tempted to create person.
So my question is, would any other repository even be tempted to create a custom person object type if JIRA 723 made it viable? If yes shall we discuss a standard approach, if no then I will wait to see what comes of JIRA 723 and make my choices then.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]