DMA Architecture Enhancement Proposal for
Content Based Search CapabilitiesAuthors: DMA Query SC: Mitsuru Akizawa, Yoshifumi Sato, Ann Palmer, Jim Green, Dennis Hamilton, Alan Babich
| HTML Rendition: This HTML rendition was produced from the Microsoft Word 97 file CBRCap02.doc. It might not be the latest version of the CBSearch extensions to DMA 1.0. Check the definitive sources for the latest version. There may be a later packaging of complete, current CBSearch materials there. |
Version 1.1: 12/06/98 Mitsuru Akizawa, Yoshifumi Sato, Ann Palmer, Jim Green, Alan Babich
(CBRCap02.doc) Removed Word macro, changed paper size to 8 ½ X 11. Fixed spelling errors. No change to proposal content.
Version 1.0: 12/06/98 Mitsuru Akizawa, Yoshifumi Sato, Ann Palmer, Jim Green, Alan Babich
Initial version.
dmaClass_DocSpace
dmaProp_DocSpaceCapabilities
DMAC_CONTENT_SEARCH
DMAC_CBR_QUERY_RESTRICTIONS
Integration Model
Query
Internationalization/Localization
Content
Containment
Versioning
Security
Naming
Performance Impact
Failure Modes/Crash Recovery
This proposal describes query capabilities for content search. This proposal assumes the content search proposal.
N/A
The value of the list element at index DMAC_LEVEL is changed from 1 to 2.
The following capabilities are to be added at the end of the Query capabilities:
DMAC_CONTENT_SEARCH
If set, DMAC_QUERY is set, and content search is supported. The class Content Search is supported, and it may have one or more subclasses.
If reset, then content search is not supported and the Content Search class is not supported.
DMAC_CBR_QUERY_RESTRICTIONS
If DMAC_CONTENT_SEARCH is set, then the following restrictions apply to queries containing content conditions as well as property conditions. A query which incorporates only content conditions is always allowed and is not affected by these restrictions. If DMAC_CONTENT_SEARCH is reset, then this capability is ignored.
The following restrictions are listed in order of least restrictive to most restrictive. These restrictions apply only to the case where a query contains both content conditions and property conditions. This capability is an integer with one of the following values:
This value indicates that there are no restrictions to the placement or the number of content conditions in a query. This means that content conditions can be freely mingled with property conditions at any level in the query tree.
This value indicates that content conditions may be mingled with property conditions. However, where there is a content condition, all nodes of the query tree subordinate to that condition may contain only content conditions. This restriction means that a query may contain any number of content conditions (subqueries), and each content condition subtree may contain only content conditions.
This value indicates that content conditions can exist only as an operand of the top level operator, and the top level operator must be either AND or OR. This restriction means that a query may contain one and only one set of content conditions and content conditions may not occur at any lower point in a query tree. The content condition subquery may contain only content conditions.
This value indicates that content conditions can exist only as an operand of the top level operator, and the top level operator must be AND. This restriction means that a query may contain one and only one set of content conditions and content conditions may not occur at any lower point in a query tree. . The content condition subtree may contain only content conditions.
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
If a document space supports unrestricted content search, the list element at index DMAC_CBR_CONTENT_SEARCH would be DMA_TRUE, and the list element at index DMAC_CBR_QUERY_RESTRICTIONS would be DMA_CBR_RESTRICT_NONE.
This proposal is backwards compatible.
There is no impact on existing systems.
N/A
This addresses the requirement of advertising content search capabilities.
This is a good solution, because it is aligned with the existing mechanism.
N/A
N/A
As per section 5, add the new capabilities, and change the format level.
html rendition derived 1999-07-29-21:23 -0700 (pdt)
$$Date: 00-02-17 15:07 $
$$Revision: 4 $