A little more explanation may be needed here:
The NewTypeSettableAttributes are enumerated in the CMIS-core.xsd as follows: (this is from my original separate spec)
<xs:complexType name="NewTypeSettableAttributes">
<xs:sequence>
<xs:element name="id" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="localName" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="localNamespace" type="xs:boolean"
minOccurs="1" maxOccurs="1"/>
<xs:element name="displayName" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="queryName" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="description" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="creatable" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="fileable" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="queryable" type="xs:boolean" minOccurs="1"
maxOccurs="1" />
<xs:element name="fulltextIndexed" type="xs:boolean"
minOccurs="1" maxOccurs="1" />
<xs:element name="includedInSupertypeQuery" type="xs:boolean"
minOccurs="1" maxOccurs="1"/>
<xs:element name="controllablePolicy" type="xs:boolean"
minOccurs="1" maxOccurs="1" />
<xs:element name="controllableACL" type="xs:boolean"
minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:complexType>
The schema for the CreateablePropertyTypes looks like the schema below (also from the new CMIS-core.xml)
Note that it can only contain a cmis:enumPropertyType which is already defined in 1.0.
- <xs:complexType name="cmisCreateablePropertiesListType">
<xs:sequence maxOccurs="unbounded" minOccurs="0">
<xs:element name="canCreate"
type="cmis:enumPropertyType">
</xs:element>
</xs:sequence>
</xs:complexType>
Jay Brown
Senior Engineer, ECM Development
IBM Software Group
jay.brown@us.ibm.com
Karsten Eberding ---01/05/2012 11:19:35 AM---Here is a comment regarding the two new Optional Type Capabilities: - NewTypeSettableAttributes From: | Karsten Eberding <karsten@eberding.eu> |
To: | cmis@lists.oasis-open.org |
Date: | 01/05/2012 11:19 AM |
Subject: | [cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 01b |
Sent by: | <cmis@lists.oasis-open.org> |
Here is a comment regarding the two new Optional Type Capabilities:
- NewTypeSettableAttributes
- CreatablePropertyTypes
All existing optional capabilities have a limited list of distinct values, either true/false or other specific responses.
The two new optional capabilities have an unlimited list of possible responses. This is inconsistent, a capability should be a clearly defined level of functionality.
I suggest to have an optional capability defined as capabilitySetTypes, with possible responses e.g. "none", "create", "modify", and then introduce two separate service calls to obtain the list of available attributes and data types for repositories that support this capability.
thanks
--
Karsten Eberding
St.-Martin-Str. 19
85604 Zorneding
Phone +49 171 3090201
Mail karsten@eberding.eu
--------------------------------------------------------------------- To unsubscribe, e-mail: cmis-unsubscribe@lists.oasis-open.org For additional commands, e-mail: cmis-help@lists.oasis-open.org