[OASIS Issue Tracker] (CMIS-781) CMIS Extension: Tags

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

    [ https://issues.oasis-open.org/browse/CMIS-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44845#comment-44845 ] 

David Choy commented on CMIS-781:
---------------------------------

My notes from today's discussion. Feel free to correct/add.

While a full discussion is deferred until we have a chance to understand Eric’s proposal, the following questions were brought up regarding the two different approaches.
- Semantics questions: Is a tag considered an integral part of the object that it associates with? (Is adding a tag considered updating the target object? Does this require a Write privilege on the target object? etc.) If tags are not integral parts of an object, then perhaps the Dependent Object approach is more appropriate than the Secondary Type approach.
- Implementation questions: Some repositories have tag implementation constraints that they might not be able to support rigid requirements.
If we ever want to support tag cloud, would a Dependent Object approach be easier?
- Ease of use and efficiency questions: Would a Secondary Type approach be easier/faster for a client to find children?


> CMIS Extension:  Tags
> ---------------------
>
>                 Key: CMIS-781
>                 URL: https://issues.oasis-open.org/browse/CMIS-781
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
>
> Forked from CMIS-759 
> Specification
> We define a tag as having the following characteristics:
> ­ a tag is a simple string that is associated with a document or other object and has no content, metadata or security of its own
> ­ an object can be associated with any number of tags
> ­ the set of tags on a document is represented by a simple multi­value string property



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)