This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 3.2.4 (FTThesaurusOption) Description of levels (Technical/Editorial) It isn't clear if an implementation is expected to implement all these kinds of relationships in thesuarus matching, or if these are implementation-defined levels that may be available. This should be made clear and added to the list of implementation-defined features. OTOH, if the intent is that all these relationships should be implemented, then thesaurus or the levels should be on the list of optional features.
The WG agreed to change the specification as follows: DECISION: Section 3.2.4 (FTThesaurusOption) changes: 1) After the numbered bullets add: Implementations should support the relationships defined in ISO 2788. The following list of terms have the meanings defined in ISO 2788. If a query specifies thesaurus relationships or levels not supported by the thesaurus, the relationships and the behaviors are implementation-defined. 2) Change examples: Example 1 change synonyms to UF. Example 2: change narrow terms to NT. Example 3: Add at beginning of descriptive text: Assuming that there is a locally defined thesaurus that contains soundex capabilities, this returns....