Content Management Interoperability Services (CMIS) Version 1.1

B.3.8
Array Types
Arrays are specified using the array type specifier. Schemas for arrays elements may be specified in one of
two ways. First, we can specify a single schema that governs all array members, with the schema enclosed
by square brackets:
array [
numbers{0.00, 1.00};
] weights; # an array of floating point weights between 0 and 1.
Alternately, "tuple typing" may be used to specify the allowable values for an array, in this case a list of
schemas that apply to each member of the array in sequence:
array {
integer;
string;
number;
} artificial;
When tuple typing is used, the * operator may be used to allow additional elements at the end of an array.
For instance, to specify an array where the first element is an integer and the remaining are of arbitrary
number and type, one might use the following schema:
array { integer; }* intFollowedByWhatever;
Finally, array types also support range semantics, for min/max number of elements:
array { integer; } {0,10} myArrayOfSmallInts;
B.3.9
Additional properties in arrays and objects
JSONSchema provides the additionalProperties attribute, which allows a schema author to either:
• specify that a valid instance object/array may not have any properties not in the schema
• specify an additional schema that applies to any additional properties in the instance object or array
that are not explicitly mentioned in the schema
Orderly allows you to specify if additional properties SHOULD be allowed, but does not allow you to specify
a schema which governs these additional properties. A trailing * in Orderly indicates additional properties
are allowed, and occurs immediately after the definition of nested schemas (the closing curly brace) for both
objects:
object {
string name;
string title;
}* employee;
And for arrays:
array { integer; string; }* myOpenTupleTypedArray
B.3.10
Null Types
The null type in JSONSchema specifies a value that MUST be null. The null type specifier is Orderly's
equivalent:
null likeAir;
As explained in the JSONSchema proposal, null is useful "mainly for purpose of being able use union types
to define nullability". For example:
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 321 of 331