[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=23130#action_23130 ] 

Jay Brown commented on CMIS-669:
--------------------------------

I agree this additional info on return could be useful to some clients, but I had constrained myself to minimize the schema changes and thus the surface area of this change as a whole to the spec.  It was a significant feature of type Mutability that the response (instance and schema) from CreateType should be the same at if one had performed a simple getType for the new type.     I would instead suggest that since the client had just supplied the hint in the very same call,  they will be able to easily obtain this mapping if it is something they are conerned about.  The spec will need to clearly state that client must ONLY use the value returned by the server (the final Id as you have referred to it ) and NEVER the hint value.   Would that be acceptable?

> 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