Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
From: Vyacheslav Pascarel <vpascare@opentext.com>
To: =?iso-8859-1?Q?Florian_M=FCller?= <fmui@apache.org>,
        "dev@chemistry.apache.org" <dev@chemistry.apache.org>
Subject: RE: "null" values for multi-value properties and CMIS specs
Thread-Topic: "null" values for multi-value properties and CMIS specs
Thread-Index: AdIq/2SD9lvEULtfR5y2plwKuL55/gAlHsoAAs8IHDA=
Date: Fri, 4 Nov 2016 19:18:08 +0000
Message-ID: <2E2BF646C525684C8733BCBB2D1280C7BD518C1E@otwlxg20.opentext.net>
References: <2E2BF646C525684C8733BCBB2D1280C7BD513104@otwlxg20.opentext.net>
 <77c906bb7fbd4624e0b41d1b8bf09158@jpberlin.de>
In-Reply-To: <77c906bb7fbd4624e0b41d1b8bf09158@jpberlin.de>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
archived-at: Fri, 04 Nov 2016 19:18:27 -0000

Hi Florian,

Thank you for clarification.

Vyacheslav Pascarel


-----Original Message-----
From: Florian M=FCller [mailto:fmui@apache.org]=20
Sent: Friday, October 21, 2016 4:09 AM
To: dev@chemistry.apache.org
Cc: Vyacheslav Pascarel <vpascare@opentext.com>
Subject: Re: "null" values for multi-value properties and CMIS specs

Hi Vyacheslav,

If I recall correctly, most vendors involved in the specification had troub=
le distinguishing null strings from empty strings. That's why null values a=
re not supported.
 From a protocol and OpenCMIS low-level API point of view you can send null=
 values, but that would be outside the CMIS specification.

- Florian


> Hi Everyone,
>=20
> A have a general question regarding CMIS specs. CMIS 1.1 says:
>=20
> -------------------------
> A property, either single-valued or multi-valued, MAY be in a "not=20
> set" state. CMIS does not support "null" property value. If a=20
> multi-valued property is not in a "not set" state, its property value=20
> MUST be a non-empty list of individual values. Each individual value=20
> in the list MUST NOT be in a "not set" state and MUST conform to the=20
> property's property-type.
> A multi-valued property is either set or not set in its entirety. An=20
> individual value of a multi-valued property MUST NOT be in an=20
> individual "value not set" state and hold a position in the list of=20
> values. An empty list of values MUST NOT be allowed.
> -------------------------
>=20
> Does anybody know what is the reason behind not allowing individual=20
> values to be in "value not set" state for multi-valued property? Is=20
> there any way to work around that limitation (beside "reserved" values=20
> or extensions)?
>=20
>=20
> Regards,
>=20
> Vyacheslav Pascarel