[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=24993#action_24993 ] 

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

Re 1: That would be the object type id of the mixin type. There is no standalone mixin instance.

Re 2: Yes, like any other type.
Re 2.1: If a required property is not set, the repository has to return an error. The behavior doesn't differ from primary types.

Re 3&4: The proposal doesn't mention that case. We could either leave it repository specific or define it. Any suggestion? Do you have an example? 


> 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