[OASIS Issue Tracker] Commented: (CMIS-713) Add secondary objecttypes

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

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

David Choy commented on CMIS-713:
---------------------------------

(1) Apply/remove secondary type by updating cmis:secondaryObjectTypeIds
I would prefer updateProperties not to create any side effect, and instead use dedicated methods to apply/remove secondary type.
(Also, if updateProperties were used, it needs to be able to update the not yet existed properties because they may be "required".)

(2) If we intend to use secondary type to support system properties (e.g. legal hold, workflow, versioning, ...), we can define the notion of "system secondary types" that can only be added/removed by the repository as a result of calling a dedicated method.
If we do so, we may also want to revisit v1.0 base types and move some of the predefined properties to secondary types. For example, content stream properties can be added when setContentStream is called the first time, and versioning properties can be added when checkin is called the first time.

(3) Should the new property attribute "typeDefinitionId" hold the type id for both primary and secondary type?

(4) If we predefine certain secondary types, can we recommend an alternative way for repositories that do not support secondary type to support the predefined properties?

> Add secondary object types
> --------------------------
>
>                 Key: CMIS-713
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-713
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>            Reporter: Florian Mueller
>             Fix For: V1.1
>
>
> We have discussed secondary types/mix-ins/aspects/categories/... for CMIS 1.0 and dismissed them to get the specification out of the door.
> We should take the discussion up again for CMIS 1.1. It would open the door for more applications and simplify others. If I remember correctly, many repositories have native support for secondary types anyway.
> See this document for a more detailed proposal: http://www.oasis-open.org/apps/org/workgroup/cmis/download.php/41368/SecondaryTypesProposal.docx

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