[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-540) 3.6.1.1 query inputsneed clarification
[ http://tools.oasis-open.org/issues/browse/CMIS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552#action_16552 ]
Ryan McVeigh commented on CMIS-540:
-----------------------------------
Likely clarification reads:
3.6.1.1 Inputs
Required:
• ID repositoryId: The identifier for the Repository.
• String statement: CMIS query to be executed. (See section 2.10 Query.)
Optional:
• Integer maxItems: See section 3.1.1 Paging.
• Integer skipCount: See section 3.1.1 Paging.
• Boolean searchAllVersions:
o If TRUE, then the Repository MUST include latest and non-latest versions of document objects in the query search scope.
o If FALSE (default), then the Repository MUST only include latest versions of documents in the query search scope.
o If the Repository does not support the optional capabilityAllVersionsSearchable capability, then this parameter SHOULD be ignored by the repository.
The following parameters are only valid for query statements where the SELECT clause contains properties from only one virtual table reference. When the SELECT clause contains properties from more than one virtual table, these parameters SHOULD be ignored by the repository.
• Enum includeRelationships: See section 3.1.2.2 Relationships.
• String renditionFilter: See section 3.1.2.4 Renditions.
• Boolean includeAllowableActions: See section 3.1.2.6 Allowable Actions.
> 3.6.1.1 query inputs need clarification
> ---------------------------------------
>
> Key: CMIS-540
> URL: http://tools.oasis-open.org/issues/browse/CMIS-540
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: Domain Model
> Reporter: Ryan McVeigh
> Assignee: Ethan Gur-esh
>
> searchAllVersions, includeRelationships, includeAllowableActions are all optional, with specified defaults. Yet under certain conditions they are required to be set:
> * searchAllVersions: If the Repository does not support the optional capabilityAllVersionsSearchablecapability, then this parameter value MUST be set to FALSE.
> * includeRelationships: If the SELECT clause contains properties from more than one table, then the value of this parameter MUST be "none".
> * includeAllowableActions: If the SELECT clause contains properties from more than one table, then the value of this parameter MUST be "none".
> * Can these not be specified as truely optional, that is, require that under certain circumstances they be NOT SET or that they be ignored by the repository?
> * Compare with deleteObject's allVersions, which the repository "MUST ignore" for non-versionable objects.
> For renditionFilter: It seems that this could have the same problems as includeRelationships and includeAllowableActions. If the results contain properties from more than one table, then they may also contain renditions from more than one type, and those renditions may have the same names. So how does a result from a JOIN return two or more cmis:thumbnail renditions (for example) for a single result?
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]