[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=26757#action_26757 ]
David Choy commented on CMIS-724:
---------------------------------
Can "document" objects be used for this purpose? While the terminology may be misleading, the "document" type was intended to represent generic, independent information entities, not just documents in the conventional sense. (There was a big debate on the terminology in the early days but no one was able to come up with an ideal name for this type. In the end, the choice was semi-arbitrary.)
Granted, the document type is a bit heavy. But with secondary types, maybe some of the document type's properties can be redefined as secondary types so that the document primary type can be lighter. This is probably a v2.0 discussion.
For the four root types in 1.0, each exhibits a different behavior (a different set of methods), while no new method is allowed for subtype. Is there a need for new methods for users and groups?
> 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]