[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=25035#action_25035 ] 

Florian Mueller commented on CMIS-713:
--------------------------------------

Re 1: I understand your concerns. But the important advantage of using updateProperties is that adding a secondary type and setting primary and secondary type properties would be one atomic operation. That's not only interesting from a performance perspective but it might also be necessary to satisfy consistency rules.
Additionally, we have to be able to set secondary types when an object is created. Doing that via properties would be similar to what we do today already with the primary type. It would be beneficial if create*(), checkIn() and updateProperties() would use the same pattern.

Re 2: That sounds like an interesting idea. Can we gather a list of potential system types to get a clearer picture of how that would look like?

Re 3: The "typeDefinitionId" attribute should be on each property tag and indicates the type in which this property is defined. If the property is defined in a secondary type, this attribute would only hold the secondary type id.

Re 4: If we define really mandatory secondary types (e.g. a content stream secondary type) than secondary types shouldn't be optional. But a repository might choose only to expose those system secondary types and not to provide repository specific ones.

> 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