[CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 01b: comments through pg. 91. Section 2.1.11.10

[Jane Doong <jku@us.ibm.com>]

My comments from pp. 1 - 91. Thx.

---------
pg.5 2.1.1.1 Optional Capabilities
=> Object Capabilities => capabilityContentStreamUpdatability => pwconly:

Original text: "The abbreviation PWC is described in section 2.1.11 Versioning."

Suggested text: "Private Working Copy (PWC) is described in section 2.1.11."

---------
pg.6 2.1.1.1 Optional Capabilities
=> Object Capabilities => capabilityRenditions

Suggested text to add to the end: "See section 2.1.4.2 Renditions."

----------
pg.7 2.1.1.1 Optional Capabilities
=> Type Capabilities => capabilityNewTypeSettableAttributes
and capabilityCreatablePropertyTypes

Suggested text to add to the ends: "See section 2.1.9.1 General Constraints on Metadata Changes."

-----------
pg.9 2.1.2 Object
The list of 4 "base types" does not include the "secondary object type".
This is inconsistent with pg 12 2.1.3.1 Object-Type Hierarchy and Inheritance,
where the following bullet shows it is a base type:

"-A CMIS repository MAY have these base types:
– cmis:relationship object-type
– cmis:policy object-type
– cmis:secondary object-type"

-----------
pg.15 2.1.3.2.1 Attributes common to ALL Object-Type Definitions
TYPO. should delete "from":

"typeMutability.create Boolean
Indicates whether new child types may be created from with this type as the parent."

----------
pg. 15 2.1.3.3.2 Attributes common to ALL Object-Type Property Definitions
=> id
TYPO. "iId" should be "id":

"with the same iId,"

---------
pg.18 2.1.3.3.2 Attributes common to ALL Object-Type Property Definitions
=> orderable

Need to clarify what the ORDERBY parameter is for. e.g.

"an ORDERBY parameter of the get Services."

---------
pg.18 2.1.3.3.2 Attributes common to ALL Object-Type Property Definitions
=> choices

The following sentence should be a new paragraph, because it applies not just to "multi" cardinality:

"If this attribute is "not set", then any valid value for this property
based on its type may be used."

----------
pg. 20 2.1.3.3.4 Attributes specific to DateTime Object-Type Property Definitions

Can we clarify that the minValue/maxValue of DateTime is a decimal that means "milliseconds since 1970/01/01, UTC"? It wasn't clear that a datetime is a decimal.

----------
pg.20 2.1.4 Document Object
TYPO. "exmape" should be "example":

"(for exmape: query)"

----------
pg.22 2.1.4.2.2 Rendition Kind
TYPO. Not sure what "singler" means.

"a singler rendition"

-----------
pg. 25 2.1.4.3.3 Property Definitions

The difference between "Should be" and "May be" in the attribute values needs to be explained up front if there is a difference. If it "SHOULD be TRUE", can't we just say "TRUE" for the attribute? And if it is "May be TRUE", can't we just say "<repository specific>"? This comment applies to all "Property Definitions" sections. Here is an example:

"cmis:baseTypeId
Queryable: SHOULD be TRUE
Orderable: MAY be TRUE"

-----------
pg.69 2.1.8 Secondary Object-Types
TYPO. "If" should be "Whether":

"If an object is fileable, versionable or controllable is determined by its primary object-type."

-----------
pg.71 2.1.9 Object-Type Creation, Modification and Deletion
TYPO. Incorrect attribute name. "create" should be "creatable".

"(create = TRUE)"

--------------
pg.71 2.1.9.1 General Constraints on Metadata Changes
TYPO. "If" should be "Whether" in 2nd paragraph:

"Note, that the client CANNOT define if a new object-type can be used as a parent type, or can be
updated or deleted."

--------------
pg.74 2.1.10.3 ACL Capabilities
TYPO. 2nd line. "repositories" should be "repository's"

"about the repositories permission model"

--------------
pg.89 2.1.11.7 Document Creation and Initial Versioning State

Need to add an intro paragraph before describing the versioning States, e.g.

"When calling the createDocument service, a versioningState parameter can be used
to specify what the versioing state of the newly-created object MUST be."

--------------
pg.91 2.1.11.10 Versioning visibility in Query Services
TYPO. duplicate "in results"

"Additionally, repositories MAY include Private Working Copy objects in results in results to the
query service."