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

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

I'm not sure I understand what do you want to move the secondary type
section.

Query names of secondary types are not different to query names of primary
types.
In order to compile a query statement the client has to know the query
names of all involved types. It doesn't matter if they primary or
secondary types.
There is no special handling of query names. Secondary type properties
have to prefixed because the type query name cannot be used in the FROM
clause. But that's it.


Regards,

Florian




On 05.03.12 14:53, "alexander.haag@wewebu.com" <alexander.haag@wewebu.com>
wrote:

>
>Thank you very much, I somehow missed CMIS-729.
>
>For 2.1.12.1.2 Secondary Type Projection
>I understand that the query name is provided by the server, but still the
>responsibility is not clear in that case.
>
>I propose to move that definition of query name into the chapter
>2.1.8 Secondary Object-Types
>Since for secondary types a special handling of query name must be done.
>
>Otherwise the interpretation could be that the client has enough
>information
>about object-type and property-type definition (like their query names)
>and
>have to prefix the secondary type properties in the query-statement.
>
>Regards,
>Alexander
>
>
>-----Ursprüngliche Nachricht-----
>Von: cmis@lists.oasis-open.org [mailto:cmis@lists.oasis-open.org] Im
>Auftrag
>von Mueller, Florian
>Gesendet: Montag, 5. März 2012 14:02
>An: Alexander Haag; cmis@lists.oasis-open.org
>Betreff: Re: [cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 02
>
>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
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cmis-unsubscribe@lists.oasis-open.org
>For additional commands, e-mail: cmis-help@lists.oasis-open.org
>