[OASIS Issue Tracker] Updated: (CMIS-227) Query optional argumentincludeAllowableActions doesn't make sense.

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

     [ http://tools.oasis-open.org/issues/browse/CMIS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Al Brown updated CMIS-227:
--------------------------

    Proposal: 
Query has all the include options of getChildren.  For queries where the select clause contains properties from only one virtual table reference (e.g., referenced object type), the include options MAY be used.  If the include options are used, the repository MUST include the information from the object type reference whose properties are specified in the select clause.  If the select clause contains properties from more than one object type reference, the repository MUST/SHOULD throw an exception.

also clarify reference terminology in query section (e.g., define object type reference)

  was:query wg agreed - Remove includeAllowableActions, includeACL since this is not appropriate in the join scenario.


> Query optional argument includeAllowableActions doesn't make sense.
> -------------------------------------------------------------------
>
>                 Key: CMIS-227
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-227
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> Line 2794 - includeAllowableActions doesn't make sense as the output is not objects, but query results, and thus have no AllowableActions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira