[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=21992#action_21992 ] 

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

Derek:
Just to clarify.  So you are just suggesting we allow the same hint mechanism that I described above be extended to localName and localNamespace?  Or were you saying we should allow them to be set in a normal fashion.   i.e. set value must always exactly equal value submitted? 

> 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