These are the parameters of the document model elements:
You can use one of the following variables in a name. The variable is replaced by a string generated from the matching element in the source document.
When writing a XML Document Model file, the qualified names, known as QNames, inside a locator must be identical to some tags in the XML document, otherwise no fields will be recognized and the queries on fields will not return a result.
The following are examples of locators. For further information, see the syntax in The semantics of locator (XPath) expressions.
A literal is a string enclosed either in single or double quotes. For an exact definition of terminal tokens see the XML recommendations.
The XPath locators are similar to XML Stylesheet Language Transformation (XSLT) patterns. They comprise exactly the subset of XSLT patterns that do not contain any predicates nor the functions 'id' and 'key' nor the node tests 'text()' and 'node()'.
Sometimes you may want to specify a general locator, such as *, to match the nodes you want to index. But you may also specify that some nodes matching a more specific locator should not be indexed.
To formulate this, include a field definition with the more specific locator for the nodes to be ignored during indexing. You then give this locator a higher priority than the one with the general locator, and specify ignore="yes". This indicates to the indexer that it must not generate field information for the matching nodes.
Note that when such an ignored node is embedded in a field-generating node, the content of the ignored node gets indexed, because it also belongs to the contents of the field-generating node.
If you do not specify a priority, the default priorities are used:
Note that the more specific the locator is, the higher the default priority. For example, the unspecific locator * gives a low priority to the found definition, whereas a name is a more specific locator and gives a higher priority.
Also note that when a node is matched by more than one locator, you can determine which of the definitions are chosen by assigning priorities to them. The definition with the highest priority is chosen. If two definitions have the same priority, the latest is chosen.
This conflict resolution is the same as that used in XML Stylesheet Language Transformation (XSLT).
In the example, the field definition "customerName" would be excluded, but definition "addresses" included.
Restrictions: