[OASIS Issue Tracker] (CMIS-771) Clarify the query support for secondary types

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CMIS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58540#comment-58540 ] 

Andy Hind commented on CMIS-771:
--------------------------------

The application of a specific secondary type to any one of the base types document/folder/relationship/policy/item is repository specific.

The CMIS retentions and holds model we define only applies to documents. There is nothing to stop its application to folders.

Another example may be adding some GEO tag via secondary type. It comes down to how people choose to model their data.

We certainly have developers/customers who query for mixed objects just by custom secondary type.
One is creating virtual folders based on some workflow and other states stored via secondary types.
They make a second pass to get the real objects one at a time.

So we are doing 2B where all secondary types are "standalone-queryable".

> Clarify the query support for secondary types
> ---------------------------------------------
>
>                 Key: CMIS-771
>                 URL: https://issues.oasis-open.org/browse/CMIS-771
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: V1.1 Errata
>            Reporter: Andy Hind
>            Priority: Critical
>
> The query support for secondary types is not clear.
> CMIS-742 defined the query behaviour for secondary types in CMIS 1.1.
> CMIS-742 and section  2.1.14.2 of the 1.1 specification imply that secondary types can be used alone.
> For example
> SELECT * from cmis:rm_hold
> There are two issues with this.
> 1) It implies that heterogeneous objects may be returned from a query, as the same secondary type could be applied to both documents and folders.  Heterogeneous object can not be returned for all repositories.
> 2) Section 2.1.14.2.1, BNF Grammar, allows only <table name> in both the <from clause> and <joined table>. <table name> is defined to identify a primary type. There is a <secondary type table name> defined but only used in <column reference>. It looks like this was overlooked in the changes made for CMIS-742. The current BNF implies that only primary types may appear in FROM and JOIN clauses.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)