[#CMIS-48] Replace cardinality:enumCardinality with multiValued:boolean

OASIS Content Management Interoperability Services (CMIS) TC

Replace cardinality:enumCardinality with multiValued:boolean

Created: 22/Feb/09 11:55 AM Updated: 11/Jan/10 06:36 PM

Component/s:

Domain Model

Affects Version/s:

Draft 0.50

Fix Version/s:

Draft 0.60

Proposal:

« Hide

Replace:
<xs:element name="cardinality" type="cmis:enumCardinality" ... />
with:
<xs:element name="multiValued" type="xs:boolean" ... />
and ajust the spec accordingly, and remove enumCardinality.

Resolution:

« Hide

Leaving as-is. See comments for more details.
TC resolution: rejected. (May submit issue to rename "cardinality")

Description

« Hide

enumCardinality just holds two values, so for simplicity if the model it would be better to replace it with a simple boolean and rename the "cardinality" to "multiValued".

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Al Brown added a comment - 23/Feb/09 01:38 PM

I can go either way. enumCardinality allows us to grow the list in the future. Some ECM systems support - single, multiple - ordered - non unique (list), multiple - non-ordered - unique (set).

I do not want to add the two flavors of multiple values in CMIS 1.0, but we may want to in the future.

My preference would be to leave as-is.

[ Permalink | « Hide ]

Florent Guillaume added a comment - 09/Mar/09 10:16 AM

The ordering and uniqueness characteristics are meaningful only in the case where the cardinality is "multiple". If the spec was extended in the future, these characteristics would be specified as a new property definition attribute IMHO.

If not, and we expect the values to be in the future to be "single", "list", "set", "bag", etc., then the name "cardinality" itself is a misnomer.

[ Permalink | « Hide ]

Al Brown added a comment - 04/Jan/10 11:55 PM

JIRA Cleanup