[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=25042#action_25042 ] 

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

Re 1: Understood. If we add input parameters to updateProperties we also have to add input parameters to checkIn. But it might break backwards compatibility to 1.0.

Re 3: Yes, it's convenience and I have no strong opinion if we really need it. Maybe it is simpler not to include it. If a client needs the property definition it can iterate through all assigned secondary types to find the property.

Re 4: My original proposal was formulated with backwards compatibility in mind. If we make secondary types mandatory, we would have CMIS 1.0 compliant and CMIS 1.1 compliant repositories. It doesn't exclude repositories, but it splits them up into two groups. Personally, I would like to avoid that but that is up to debate and a broader discussion.

I'm not sure I understand your idea of extending a primary type with secondary types. Could you please elaborate a bit more on that?!

Do we really need a new capability? The presents or absence of the Mixin base type could indicate if secondary types are supported. We do the same with relationships and policies in CMIS 1.0.


> 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