cmis message

Subject: [OASIS Issue Tracker] Created: (CMIS-659) Clarification forproperties in state "not set" required

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: cmis@lists.oasis-open.org
Date: Fri, 25 Jun 2010 04:06:13 -0400 (EDT)

Clarification for properties in state "not set" required
--------------------------------------------------------

                 Key: CMIS-659
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-659
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: Task
          Components: Domain Model
            Reporter: Martin Hermes
            Assignee: Ethan Gur-esh


I need clarification about how properties are handled in the getProperties() call which have the status "not set".
On the one hand side the spec states:

2.2.1.2.1 Properties
...
If a property filter specifies a property that is 'not set', it MUST be represented as a property element without a value element. 

On the other hand side its stated for multi value properties:

2.1.2.1 Property
...
A multi-valued property is either set or not set in its entirety. An individual value of a multi-valued property MUST NOT be in an individual "value not set" state and hold a position in the list of values. An empty list of values MUST NOT be allowed.

My question is if properties with value 'not set' should be returned in a getProperties() call at all?

Martin

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