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?