[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cmis] empty multivalued properties
Thanks for SAP KM and JCR.
>The main reason to have it seems to be that you can make a multivalued property mandatory,
>and still allow it to be empty.
How is that different than optional multi-valued property with a choice list? (Beyond the basic optional -> mandatory property flag)
>It probably doesn't make a big difference in practice...
If it is not a big difference in practice, why should it be added and add to the complexity/cost of CMIS?
I try to use 80% as a filter - if 80% of repositories support it or if 80% of targeted applications on repositories require the functionality. Simplicity and ease of implementing (client and app) will be key to the success of this effort.
-Al
Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home
Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.
Julian Reschke ---04/08/2009 01:47:28 PM---Florent Guillaume wrote:
From: | Julian Reschke <julian.reschke@greenbytes.de> |
To: | Florent Guillaume <fg@nuxeo.com> |
Cc: | cmis@lists.oasis-open.org |
Date: | 04/08/2009 01:47 PM |
Subject: | Re: [cmis] empty multivalued properties |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]