[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=10114#action_10114 ] 

Florent Guillaume commented on CMIS-82:
---------------------------------------

It all boils to to whether "required" is seen from the writer's side (a value is required when the document is created/updated), or from the reader's side (the value will always been set).

> 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 TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.52
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>            Priority: Trivial
>
> 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