[OASIS Issue Tracker] Commented: (CMIS-82) Property Definitions: Aproperty definition should not ever say READONLY + REQUIRED

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

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

Al Brown commented on CMIS-82:
------------------------------

We should clarify required is from the writer's point of view.  Also, the spec should be updated to say that repositories should not have properties that are required + readonly and that if such properties exist on an object, then updates will fail

> Property Definitions: A property definition should not ever say READONLY + REQUIRED
> -----------------------------------------------------------------------------------
>
>                 Key: CMIS-82
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-82
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.50
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>            Priority: Trivial
>             Fix For: Draft 0.6
>
>
> Currently in the CMIS spec we have the following 2 attributes on a property definition:
> - updateability: Where you can say a property is readonly (i.e. the app can never set it)
> - required: Where you can say that a property is required. 
> BUt it's not clear/obvious what it would mean to have a property that is read-only and required... what is an application supposed to do in that situation?

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