[CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 01b: comments pp 100-192

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

My comments for the rest of chapter 2, from pp. 100 - 192. Thx.

-------------------------------------------------------------------------
pg.92 2.1.12.1.2 Secondary Type Projection

There are some inconsistencies in specifying the secondary type patterns.

pg.92 2.1.12.1.2 Secondary Type Projection:
"<secondary type query name>.<property query name>"

pg.108 2.2.1.2.1 Properties
"<secondaryTypeQueryName>.<propertyQueryName>"

I think pg.92 should be changed, because pg 108 and pg 112 both have the concatenated version without the spaces.

---------------
pg.108 2.2.1.2.1 Properties

The Note: and the Example paragraphs both are explaining the optional input "filter", and should be relocated and indented under the "filter" bullet, instead of being part of the general description of "Properties":

"Note:
This filter is a list of property query names and NOT a list of property
ids. The query names of secondary type properties MUST follow this pattern:
<secondaryTypeQueryName>.<propertyQueryName>
...
Example:
cmis:name,amount,worflow.stage"

--------------
pg.117 2.2.2.1.2 Outputs
Consistency: The last "repository" should be lowercase in the 2nd bullet, to be consistent with the first bullet:

"-Id repositoryId: The identifier for the repository.
-String repositoryName: A display name for the Repository."

--------------
pg.144 2.2.4.3.1 Inputs
=> Optional

The optional inputs for createFolder are incorrectly referencing "the newly-created document object". They should be changed to "newly-created folder object".

"- <Array> Id policies: A list of policy ids that MUST be applied to the newly-created
document object.
- <Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created
document object, ...
- <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newlycreated
document object, ..."

----------------
pg.146 2.2.4.4.1 Inputs
=> Optional

Same comment for createRelationship. The optional inputs are incorrectly referencing "the newly-created document object". They should be changed to "newly-created relationship object".

----------------
pg. 148 2.2.4.5.1 Inputs
=> Optional

Same comment for createPolicy. The optional inputs are incorrectly referencing "the newly-created document object". They should be changed to "newly-created policy object".

----------------
pg. 152 2.2.4.8.3 Exceptions Thrown & Conditions

Since there is no rendition filter for getProperties, the filterNotValid exception description should remove the reference to rendition filter:

"filterNotValid If the property <DELETE>or rendition</DELETE> filter input parameter is not valid."

----------------
pg.160 2.2.4.15 deleteTree
TYPO in last bullet: "owever" => "however"

----------------
pg.165 2.2.5 Multi-filing Services

In the intro paragraph, I suggest adding a pointer/link to "capabilityMultifiling":

"The Multi-filing services are supported only if the repository supports the multifiling or unfiling
optional capabilities<INSERT>(capabilityMultifiling)</INSERT>."

----------------
pg.176 2.2.7.3.1 Inputs
=> Optional
TYPO in 3rd bullet: forthe => for the

-----------------
pg.176 2.2.7.3.1 Inputs
=> Optional

Since there is no folderId input parameter for checkIn, the references to "folderId" should be removed from the 2 bullets:

"- <Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created
document object, either using the ACL from folderId if specified, or being applied if no folderId
is specified.
- <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newlycreated
document object, either using the ACL from folderId if specified, or being ignored if
no folderId is specified.
"

-----------------
pg. 178 2.2.7.4 getObjectOfLatestVersion
TYPO: remove extra " a ":

"Description: Get a the latest document object in the version series."

-----------------
pg. 180 2.2.7.5.3 Exceptions Thrown & Conditions

Since there is no rendition filter for getPropertiesOfLatestVersion, the filterNotValid exception description should remove the reference to rendition filter:

"filterNotValid If the property <DELETE>or rendition</DELETE> filter input parameter is not valid."

-----------------
pg. 181 2.2.7.6.3 Exceptions Thrown & Conditions

Same comment for getAllVersions. The filterNotValid exception description should remove the reference to rendition filter.

-----------------