[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=25040#action_25040 ] 

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

Re 1: My main concern is that the "cmis:secondaryObjectTypeIds" should be a system property and yet it is updatable by user. How about making it a system property (read only), and adding an input parameter to updateProperties to add/remove secondary types? BTW, a property's queryName needs to be unique across all object types to avoid query ambiquity.

Re 3: That is what I meant. But the proposal said it can be "missing". BTW, this attribute is only for convenience, because the ID attribute of a property is unique in the repository and can therefore indirectly, but uniquely, identify the type it belongs to.

Re 4: Making secondary type mandatory would exclude many repositories from compliance. I would rather allow a repository to use a secondary type to extend a primary type (thereby creating a subtype of the primary type). In that case, every instance of the subtype has both the primary type and the secondary type. Note: if both the primary type and the secondary type are predefined, there is no need to predefine the subtype, i.e. there is no "m x n" type definitions. I'd also propose to add a repository capability to indicate whether adding a secondary type to an object instance is supported by the repository.


> 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