[OASIS Issue Tracker] Commented: (CMIS-669) add CMIS TypeMutability for next version of spec

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

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

Florian Mueller commented on CMIS-669:
--------------------------------------

The current draft specifies that only the object type id is returned, not the whole type definition.
Here is a proposal to solve the property mapping problem: createType returns the type definitions and all property definitions. The order of all not inherited property definitions MUST match the order of the input. So the first not inherited property definition would match the first property definition in newPropertyDefinitions, the second not inherited property definition would match the second property definition in newPropertyDefinitions, and so on.

> add CMIS Type Mutability for next version of spec
> -------------------------------------------------
>
>                 Key: CMIS-669
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-669
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>         Environment: n/a
>            Reporter: Jay Brown
>
> Have submitted a draft to the TC documents, to get this discussion started.   See proposal for URL. 

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