Content Management Interoperability Services (CMIS) Version 1.1
Content Management Interoperability Services (CMIS) Version 1.1
Content Management Interoperability Services (CMIS) Version 1.1
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
MAY also have one or more renditions associated with it. A rendition can be a thumbnail or an alternate<br />
representation of the content stream.<br />
Objects MAY have one Access Control List (ACL), which controls access to the object. A set of policy objects<br />
may also control access to the object. An ACL represents a list of Access Control Entries (ACEs). An ACE<br />
in turn represents one or more permissions being granted to a principal (a user, group, role, or something<br />
similar).<br />
The notion of localization of the objects in the data model is entirely repository specific.<br />
<strong>CMIS</strong> objects MAY expose additional information, such as vendor-specific workflow data, beyond the attributes<br />
described above. In this respect, the data model can be extended as desired. This specification<br />
does not standardize such extensions.<br />
2.1.2.1 Property<br />
A property MAY hold zero, one, or more typed data value(s). Each property MAY be single-valued or multivalued.<br />
A single-valued property contains a single data value, whereas a multi-valued property contains an<br />
ordered list of data values of the same type. The ordering of values in a multi-valued property SHOULD be<br />
preserved by the repository.<br />
A property, either single-valued or multi-valued, MAY be in a "not set" state. <strong>CMIS</strong> does not support "null"<br />
property value. If a multi-valued property is not in a "not set" state, its property value MUST be a non-empty<br />
list of individual values. Each individual value in the list MUST NOT be in a "not set" state and MUST conform<br />
to the property's property-type.<br />
A multi-valued property is either set or not set in its entirety. An individual value of a multi-valued property<br />
MUST NOT be in an individual "value not set" state and hold a position in the list of values. An empty list of<br />
values MUST NOT be allowed.<br />
Every property is typed. The property-type defines the data type of the data value(s) held by the property.<br />
<strong>CMIS</strong> specifies the following property-types. They include the following data types defined by "XML Schema<br />
Part 2: Datatypes Second Edition" (see [XMLSchema]):<br />
string (xsd:string)<br />
boolean (xsd:boolean)<br />
decimal (xsd:decimal)<br />
(see section 2.1.3.3.5 Attributes specific to Decmial Object-Type Property Definitions for attributes<br />
specific to Decimal object-type property definitions.)<br />
integer (xsd:integer)<br />
(see section 2.1.3.3.3 Attributes specific to Integer Object-Type Property Definitions for attributes specific<br />
to Integer object-type property definitions.)<br />
datetime (xsd:dateTime)<br />
(see section 2.1.3.3.4 Attributes specific to DateTime Object-Type Property Definitions for attributes<br />
specific to DateTime object-type property definitions.)<br />
uri (xsd:anyURI)<br />
In addition, the following property-types are also specified by <strong>CMIS</strong>:<br />
id<br />
html<br />
Individual protocol bindings MAY override or re-specify these property-types.<br />
For single valued String, Id and HTML properties, a repository MAY support the distinction between a set<br />
value with an empty string (length = 0), and a "not set" value. In this case an empty value element (e.g.<br />
<strong>CMIS</strong>-v<strong>1.1</strong>-csprd01<br />
Standards Track Work Product<br />
Copyright © OASIS Open 2012. All Rights Reserved.<br />
18 August 2012<br />
Page 21 of 331
Change language