[OASIS Issue Tracker] Created: (CMIS-81) Repository capabilities - Merge FullText values into Query

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

Repository capabilities -  Merge FullText values into Query
-----------------------------------------------------------

                 Key: CMIS-81
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-81
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Bug
          Components: Schema
    Affects Versions: Draft 0.52
            Reporter: Ethan Gur-esh
            Priority: Minor


In the CMIS domain model/schema, we currently have two "capabilities" relating to full-text support in search. These are: 

Query (non-Boolean)     Indicates the types of queries that the Repository has the ability to fulfill. Query support levels are:
- None
- MetadataOnly: Only queries that filter based on object properties can be fulfilled.
- FulltextOnly: Only queries that filter based on the full-text content of documents can be fulfilled. 
- Both: The Repository can fulfill queries that filter based on object metadata and/or document full-text content.

FullText (non-Boolean)
Indicates the types of full-text queries that the Repository has the ability to fulfill. FullText support levels are:
- None: No full-text queries can be issued.
- FullTextOnly: Only queries that filter based on the full-text content of documents can be fulfilled.
- FullTextAndStructured: The repository can fulfill queries that filter on both the full-text content of documents and their properties.

This is unnecessarily complicated. There are redundant states and inter-dependency between the values (e.g. there are two full-text only values, and FullTextAndStructured only makes sense for Fulltext if "both" is the value for Query).

-- 
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