Re: [cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 02

["Mueller, Florian" <florian.mueller02@sap.com>]

Hi Alexander,

Re 1) The query name is defined by the CMIS server. Since secondary types are just types, a client retrieve the query name by calling getTypeDefinition.

Re 2) Yes, they are different. See also 2.1.13.2.4.4 and CMIS-729.


Regards,

Florian


From: "alexander.haag@wewebu.com<mailto:alexander.haag@wewebu.com>" <alexander.haag@wewebu.com<mailto:alexander.haag@wewebu.com>>
Date: Mon, 5 Mar 2012 13:25:20 +0100
To: "cmis@lists.oasis-open.org<mailto:cmis@lists.oasis-open.org>" <cmis@lists.oasis-open.org<mailto:cmis@lists.oasis-open.org>>
Subject: [cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 02

Hi all,

reviewing the latest draft, some minor issues/questions appeard:
- 2.1.12.1.2 Secondary Type Projection
            In order to distinguish secondary type properties from primary type properties, they have to be prefixed with
the query name of the secondary type. The full pattern is:
[<primaryTypeQueryName OR alias>.]<secondaryTypeQueryName>.<propertyQueryName>
      Must the CMIS-client provide the prefix or is the query name of the property already defined by CMIS-server?

-          2.1.12.3 Escaping
Within a CONTAINS text search expression, the double characters \* and \? represent a literal asterisk
      (*) character and a literal question mark (?) character respectively.
Do we have different wildcard definitions for CONTAINS- and LIKE-Search?

Regards,
Alexander