- Error in compiling value for variable variable Name!
This message occurs when the
user compiles a grammar. There was a problem while compiling a variable. For more information about the
error see Compilation messages.
- Error during compiling :
This message occurs when the user loads grammar(s) from a file in
the system and he/she wants them to be compiled. For more information about the error see Compilation messages.
- Error occurred while loading!
This message occurs when the user loads grammar(s) from a file in the system. There is a problem in the communication with the operating system. Check read/write
permissions of the directory in which the system writes its data files.
- Error on parsing key for element name
This message occurs when the user tries to
apply a query. The Element value of the element is not a valid XPath.
- Error in opening grammar grammar name!
This message occurs when the user tries to
edit a grammar. The system file with the grammar is damaged and the grammar is lost.
- Error in opening grammar query query name!
This message occurs when the user tries
to apply a grammar group from the Group Manager dialog. The query was deleted after it had been
added to the group query.
- Expression expression not finished! Expected variable name!
This message occurs
when the user compiles a grammar. It means that there is a variable identifier (&) in the expression,but no
capital Latin letter specifies the variable name.
- Grammar grammar name not found!
This message occurs when the user loads a
grammar query and the grammar in that query is not found in the system database. A possible reason is that the
grammar was deleted after the query had been created.
- Grammar Query query name has an incorrect XPath expression for this group!
This
message occurs when the user applies a Grammar Group. All grammars from a group must have the same
Apply to XPath expression.
- Grammars.dtd compilation error!
This message occurs when the user wants to edit a grammar
in the editor. There is a problem in compiling the system DTD. The system cannot find the file with the DTD or
that file was corrupted.
- If value is Token Category, put '$' in front of it.
This message occurs when the user
compiles a grammar. The grammar compiler has found an atom and cannot determine its type. This error
message proposes a probable solution.
- Invalid XPath expression in 'Apply to'!
This message occurs when the user wants to apply a
grammar over an XML document. The XPath expression in the Apply to text field is not correct. It
specifies the nodes which the grammar will be applied to. For details see the XPath messages.
- No XPath expression in 'Apply to' field!
This message occurs when the user wants to apply a
grammar over an XML document. The Apply to text field is empty. It specifies the nodes which the
grammar will be applied to.
- Node Set result expected!
This message occurs when the user wants to apply a grammar over an
XML document. The XPath expression in the Apply to text field is expected to return a node set in the
result, but it returns something else (number, string or boolean). The XPath specifies the nodes which the
grammar will be applied to.
- Problem with saving automaton in internal format!
This message occurs when the system
tries to save a grammar, but the grammar cannot be saved. Possible reasons are: no free disk space on the user's
computer or no write permission declared.
- Select grammar(s) first.
This message occurs when the user performs some operations like
Edit grammar in editor or Save grammar to file. There are no grammars selected for saving
or opening.
- The system cannot create the grammar gramName!
This message occurs when the
system tries to save a grammar in its database, but the grammar cannot be saved. Possible reasons are: no free
disk space on the user's computer or no write permission declared.
- The system cannot load the grammar gramName from an internal file!
This error
occurs when there is a problem while loading a grammar from the system database. A possible reason is
damage of the system files.
- The system cannot load the grammar automaton from an internal file!
This message occurs
when the user tries to apply a grammar. The internal format for saving grammars is changed in this version.
The user must recompile the grammars to fix this problem.
- The system cannot load the grammar from an internal file!
This message occurs when the user
tries to edit a grammar. The system file with the grammar is damaged and the grammar is lost.
- The system cannot save the grammar in an internal file!
This message occurs when the user
tries to save a grammar in its database. There is a problem in the communication with the operating system.
Check read/write permissions of the directory in which the system writes its data files.
- The system cannot save the grammar automaton in an internal file!
This message occurs when
the user tries to save a grammar in its database. There is a problem in the communication with the operating
system. Check read/write permissions of the directory in which the system writes its data files.
- The system was not able to load query:
This message occurs when the user loads a Grammar
Group query. The query in the message is not found in the system. A possible reason is that the query was
deleted after it had been added to the Grammar Group query.
- There was an error while saving in file name
This message occurs when the user tries
to save grammar(s) from the system in a file and the grammar(s) cannot be saved. Possible reasons are: no free
disk space on the user's computer or no write permission declared.
- There was an error while trying to open grammar name
This message occurs when the
user loads a grammar in the system. There is a problem in the communication with the operating system.
Check read/write permissions of the directory from which the system reads its data files.
- There was an error while trying to read from file name
This error occurs when the
user loads a grammar from a file in the system. Possible reasons are: the document is in another encoding, it is
not in the appropriate format or it is not a well-formed document.
- This in not a valid mark-up!
This message occurs when the user has changed the return
markup of a grammar from the select dialog. The mark-up cannot be used for changing the document because
it is not a valid XML mark-up.
- Variable name has value that can be empty!
This message occurs when the user
compiles a grammar. A variable matches the empty word. It cannot receive an empty value.
- Variable name not defined
This message occurs when the user compiles a grammar.
The compiler has encountered a variable that is not defined. This can be corrected by adding the variable
definition in the list with variables or by choosing another variable.
- Variable variable name defined more than once!
This message occurs when the user
compiles a grammar. There are two or more definitions for one variable.
- Unable to apply. Grammar name not selected!
This message occurs when the user wants to
apply a grammar over the document. There is no grammar selected for applying.
- Unable to load grammar from system database!
This message occurs when the user compiles a
grammar. There is a problem in the communication with the operating system. Check read/write permissions
of the directory in which the system writes its data files.
- Empty regular expression cannot be used here!
This message occurs when the user creates or
edits a regular expression and there is no value in the Regular Expression text field. The regular
expression defines the constraint over the nodes' content. The regular expression may consist of: tags, token
categories, token values and token value templates.
- Error in regular expression:
This message occurs when the user creates or edits a regular
expression and the value in the Regular Expression text field is not valid. The regular expression
defines the constraint over the nodes' content. The regular expression may consist of: tags, token categories,
token values and token value templates.
- Error in writing file filename! Constraints NOT saved!
This message occurs when the
user tries to save a constraint in the system, but the constraint cannot be saved. Possible reasons are: no free
disk space on the user's computer or no write permission declared.
- Incorrect constraint name!
This message occurs when the user tries to save a constraint
without a name. The user must specify a constraint name in order to save it. Constraints are identified by their
names.
- No XPath expression entered!
This message occurs when the user applies a Regular
Expression Constraints operation. The Select Nodes text field is empty. The XPath expression defines
the nodes which the constraints will be applied to.
- There are no new constraints to load. Please check if the file syntax is correct!
This message
occurs when the user tries to load constraints from a file and the selected XML document is not in the
appropriate format. It must be valid according vconstraint.dtd stored in Resource directory of the system.
- There was an error while trying to load from file! No constraints loaded.
This message occurs
when the user tries to load constraints from a file and the selected file is not a well-formed XML
document.
- A non-empty source expression allowed!
This message occurs when the
XML/XPath text field in the Source panel of the Constraint Editor dialog is
empty. It defines the values that will be inserted or validated by the constraint.
- A positive number expected in field Prompt for save on each ... times
This message occurs
when the Prompt for save on each ... checkbox from the Constraint Editor dialog is
selected but the value is not a number. A positive integer value is expected. It tells that the document must be
saved when the constraint is applied number times.
- Constraint constraint name not found.
This message occurs when a query is applied
and the constraint specified in the query is not found in the system database. A possible reason is that the
constraint was deleted after it had been added to the query.
- Constraint group group name not found.
This message occurs when a query is applied
and the constraint group specified in the query is not found in the system database. A possible reason is that the
group was deleted after it had been added to the query.
- Constraints Group name not specified!
This message occurs when the user tries to save a
constraint group without a name. The user must specify a constraint group name in order to save it. Constraint
groups are identified by their names.
- Constraint Group not selected for application!
This message occurs when the user tries to
apply a group from the Value Constraints manager and there is no selected constraint group in the
table with all groups. The user must select a constraint group in order to apply it.
- Context (XPath) expression not specified!
This message occurs when the Context
(XPath) text field of the Constraint Group Editor is empty. The context expression defines where
the constraint group will be applied.
- The current document is not presented in the document database of the Clark System. To save the
document, use menu: File/Save!
This message occurs when the Prompt for save on each: ...
applications of constraint checkbox is selected in the constraint and the document which it is applied to is
not saved in the system.
- Error in writing file filename Constraints NOT saved!
This message occurs
when the user tries to save a constraint in the system and the constraint cannot be saved. Possible reasons are:
no free disk space on the user's computer or no write permission declared.
- Error loading document: document name! Proceeding to next constraint ...
This error
message occurs when the source of a constraint in the Constraint Editor dialog is from an external
document and there is a problem while loading that document. A possible reason is that the document was
deleted after the constraint creation.
- Expected positive number (number)!
This message occurs when the value of the
Position text field in the Constraint Editor dialog is not a positive integer value. It
defines the position where the constraint value will be inserted as a child.
- Group entries not found.
This message occurs when a constraint group is applied and one or
more of the listed constraints are not found in the system database.
- Incorrect constraint name!
This message occurs when the user tries to save a constraint
without a name. The user must specify a constraint name in order to save it. Constraints are identified by their
names.
- Incorrect number in field Prompt for save on each...
This message occurs when the
Prompt for save on each ... checkbox from the Constraint Editor dialog is selected but the
value is not a number. A positive integer value is expected. It tells that the document must be saved when
the constraint is applied number times.
- Incorrect template!
This message occurs when the user creates/modifies templates in a
Constraint Editor dialog. The entered template is not valid.
- Invalid insertion position:
This message occurs when the value of the
Position text field of the Constraint Editor dialog is not a positive integer value. It
defines the position where the constraint value will be inserted as a child.
- Invalid target attribute name: attribute name!
This message occurs when the value
entered in the Target Attribute text field of the Constraint Editor dialog is not a valid
attribute name. A valid attribute name is expected. It defines attributes which the constraint will be
applied to.
- Invalid target node name: node name
This message occurs when the value entered in
the Target Node text field of the Constraint Editor dialog is not a valid node name. A valid
node name is expected. It defines the target nodes where the constraint will be applied.
- Invalid XML markup. Expected element-rooted structure!
This message occurs while the
Parent constraints are being applied and the user wants to insert a different item from the ones defined
in the constraint. This problem appears when the new item cannot be treated as an XML tag placed for a
parent.
- No input in field Prompt for save on each ...
This message occurs when the Prompt
for save on each ... checkbox from the Constraint Editor dialog is selected but no value is
entered. A positive integer value is expected. It tells that the document must be saved when the constraint is
applied number times.
- No constraints/groups to apply!
This message occurs when no constraints or/and groups are
added in the list of constraints in the Apply Constraints dialog and the Apply button is pressed.
In order to apply a constraint the user must add it to the list.
- No target attribute defined!
This message occurs when no value is entered in the Target
Attribute text field of the Constraint Editor dialog. A valid attribute name is expected. It defines
the attributes which the constraint will be applied to.
- No target node defined!
This message occurs when no value is entered in the Target
Node text field of the Constraint Editor dialog. A valid node name is expected. It defines the nodes
which the constraint will be applied to.
- The following invalid entries were detected: invalid constraints. They will be excluded.
This message occurs when a constraint group is applied and one or more of the listed constraints from the group are not found in the system database.
- The selected group does not contain any valid constraints!
This message occurs when there
are no constraints in the group which the user wants to apply to the document.
- The Value Constraints can only be applied to Element nodes.
This message occurs when the user presses Ctrl +D - the standard shortcut for applying Value Constraints over a selected node and the selection is on a text or attribute node. Value Constraints work over element nodes.
- There are no active constraints of suitable type to be applied!
This message occurs when no
constraints are activated and the user wants to apply constraints from the Value Constraints manager. In order to apply a constraint the user must make it active.
- There are no constraints of suitable type to be applied!
This message occurs when there are
only constraints of All Children type defined in the system. Constraints of this type are used
automatically when the document is validated.
- There are no constraint types activated. Please check Options!
This message occurs when
there are no active constraint types in use. Constraints of a given type can be made active from the button
Options, by selecting certain types.
- There are no constraints to be applied!
This message occurs when there are no constraints
defined in the system. In order to apply a constraint the user must first create it.
- There are no new constraints to load. Please check whether the file syntax is correct!
This
message occurs when the user tries to load constraints from a file and the selected XML document is not in the
appropriate format. It must be valid according to the vconstraint.dtd stored in Resource
directory of the system.
- There was an error while trying to load from file! No constraints loaded.
This message occurs
when the user tries to load constraints from a file and the selected file is not a well-formed XML
document.
- Unable to parse source XML data!
This message occurs when the user creates/modifies the
source of a constraint in the Constraint Editor dialog, and the source is an XML mark-up. The entered
expression is not a valid XML mark-up.
- Unable to parse source XPath expression!
This message occurs when the user
creates/modifies the source of a constraint in the Constraint Editor dialog and the source is an XPath
expression. The entered XPath expression is not valid. For details see the XPath messages.
- Unable to parse the Target XPath expression!
This message occurs when
the user creates/modifies the content of the Target XPath field of a constraint in the Constraint
Editor dialog that is an XPath expression. The XPath expression which is entered is not valid. For details
see the XPath messages.
- Unable to parse XPath expression:
This message occurs when the user creates/modifies
the content of the Context field of a constraint group in the Constraints Group Editor dialog
is an XPath expression. The entered XPath expression is not valid. For details see the XPath messages.
- <copy-of> without 'select' attribute!
In order to copy data the user has to specify it. This is done by the select attribute required for that element. Its value must be an XPath expression.
- <for-each> without 'select' attribute!
In order to use this operator a node set must be
selected. This is done by the select attribute required for that element. Its value must be an XPath expression.
- <if> without 'test' attribute!
In order to use this operator a condition must be defined.
This is done by the test attribute required for that element. Its value must be a boolean expression.
- <value-of> without 'select' attribute!
In order to get a value of a data the user has to
select it. This is done by the select attribute required for that element. Its value must be an XPath
expression.
- A required attribute 'match' is missing!
In order to use the template rule a node(s) must be
selected. The match attribute is a pattern which identifies the source node or nodes which the rule
applies to. It is required for template rules. Its value must be an XPath expression.
- Error deleting xslt transformation name
The transformation was not found in the
system.
- Error during loading document document name.
The file was not found in the system.
Probably it was deleted out of the system.
- Error while saving xslt
The transformation cannot be saved in the system. Possible reasons
are: no free disk space on the user's computer or no write permission declared.
- Expression not evaluated as a node-set.
The XPath expression does not define any nodes
which the local transformation to be applied to.
- Invalid tranformation document! Root must be either 'stylesheet' or 'transform'!
The
document which the user wants to add in the XSLT Manager is not a transformation. The root element of a
transformation must be either xsl:stylesheet or xsl:transform element.
- Invalid value for attribute 'match'(XPath expression expected)!
The match
attribute is a pattern that identifies the source node or nodes which the rule applies to. Its value must be an
XPath expression.
- Invalid value for attribute 'priority' (number expected)!
The priority of a template rule is
specified by the priority attribute of the template rule. Its value must be a real number (positive or
negative).
- Invalid value for attribute 'select' (XPath expression expected)!
xsl:sort has a
select attribute whose value is an XPath expression. For each node to be processed, the
expression is evaluated with that node as a context node and with the complete list of nodes being processed
in unsorted order as a context node list. The resulting object is converted to a string as if by a call to the
string() function in the XPath. This string is used as the sort key value for that node.
- Invalid XPath for local transformation:
The defined XPath expression is not valid.
- No match attribute in pattern!
The match attribute is a pattern that identifies the
source node or nodes which the rule applies to. It is required for the template rules.
- No result produced!
The transformation does not produce a result file from the source
document.
- Root node selected as a context. This node cannot be used in local transformations and will be
ignored.
Local Tranformation cannot be applied on the root element, because it does not produce a
document as a result, but a node set. In order to apply the transformation over the root element the user must
not select the Use Local Transformation checkbox from the Apply XSLT dialog.
- Template rule without 'match' attribute!
In order to use this operator (a) node(s) must be
selected. The match attribute is a pattern that identifies the source node or nodes which the rule applies
to. It is required for the template rules.
- The application of the current XSLT has performed an illegal DOM operation! Further processing will
be cancelled.
The result document that is produced by the transformation is not a well-formed XML
document.
- The system was unable to load transformation "transformation name"! Bad Transformation
File
The file was not found in the system. Probably it was deleted out of the system.
- The XPath expression: expression does not select any nodes!
The XPath expression
does not define any nodes which the local transformation to be applied to.
- There was an error while trying to load transformation "transformation name" Further
processing will terminate.
A file with the transformation is not found in the system. Probably it was
deleted out of the system.
- This name 'transformation name' is already in use. Do you want to overwrite the
transformation?
The entered transformation name is already used for another transformation.
- Value "data type for attribute 'sort' is not supported!
Only "number" and "text" values
for that attribute are supported. It defines whether values will be compared as strings or as numbers.
- Value "order value" for attribute 'order' is not allowed!
The Order attribute
specifies whether the strings should be sorted in ascending or descending order. Values that are allowed here are : ascending and descending.
- XPath expression for local transformation not specified.
The XPath text field
for a local transformation is empty.
- XSL transformation document not specified.
No transformation is selected for applying.
- XSLT document "transformation name" not found.
The file was not found in the
system. Probably it was deleted out of the system.
- Error while compiling xpath context expression XPath Error
The XPath
expression in the Define Context: field of the Concordance dialog is not
valid. For details see the XPath messages.
- Error while compiling xpath left context expression XPath Parse Error
The
XPath expression in the Left Context: field of the Concordance dialog is not
valid. For details see the XPath messages.
- Error while compiling xpath right context expression XPath Parse Error
The
XPath expression in the Right Context: field of the Concordance dialog is
not valid. For details see the XPath messages.
- Error while compiling xpath search expression XPath Parse Error
The XPath
expression in the Search Elements: field of the Concordance dialog is not
valid. For details see the XPath messages.
- Node set result expected!
The XPath expression in the Define Context:, Left
Context:, Right Context: or Search Elements: field of the Concordance dialog is
not specified.
- The search query element values and restriction query element values are not equal!
In
order to use a restriction grammar over the input of the search grammar, the user must
synchronize the queries of both grammars on the following options: tokenizer, filter,
normalize options and element values. This will allow a subword selected from the output
by the restriction grammar to be acknowledged as a valid input for the search grammar.
- The search query filter and restriction query filter are not equal!
In
order to use a restriction grammar over the input of the search grammar, the user must
synchronize the queries of both grammars on the following options: tokenizer, filter,
normalize options and element values. This will allow a subword selected from the output
by the restriction grammar to be acknowledged as a valid input for the search grammar.
- The search query normalize and restriction query normalize are not equal!
In
order to use a restriction grammar over the input of the search grammar, the user must
synchronize the queries of both grammars on the following options: tokenizer, filter,
normalize options and element values. This will allow a subword selected from the output
by the restriction grammar to be acknowledged as a valid input for the search grammar.
- The search query tokenizer and restriction query tokenizer are not equal!
In
order to use a restriction grammar over the input of the search grammar, the user must
synchronize the queries of both grammars on the following options: tokenizer, filter,
normalize options and element values. This will allow a subword selected from the output
by the restriction grammar to be acknowledged as a valid input for the search grammar.
- Error in compiling xpath expression XPath Parse Error
The XPath expression in
the Search: field of the Extract dialog is not valid. For details see the XPath messages.
- Node set result expected!
The XPath expression in the Search: field of
the Extract dialog is not specified.
- Number attribute field is empty!
The name of the attribute in the Create
number attribute? field of the Extract dialog is not specified. The user must specify
it or he/she must uncheck this option.
- Number attribute has invalid symbol at position N !
The name of the
attribute in the Create number attribute? field of the Extract dialog
does not obey the standard. For details see the XML
recommendation for the valid name standard.
- Path attribute field is empty!
The name of the attribute in the Create path
attribute? field of the Extract dialog is not specified. The user must specify it or
he/she must uncheck this option.
- Path attribute has invalid symbol at position N !
The name of the
attribute in the Create path attribute? field of the Extract dialog does not
obey the standard. For details see the XML
recommendation for the valid name standard.
- Result element field is empty!
The name of the attribute in the Create
result tag? field of the Extract dialog is not specified. The user must specify it or
he/she must uncheck this option.
- Result element has invalid symbol at position N !
The name of the
attribute in the Create result tag? field of the Extract dialog does not obey
the standard. For details see the XML
recommendation for the valid name standard.
- Source attribute field is empty!
The name of the attribute in the Create
source attribute? field of the Extract dialog is not specified. The user must specify
it or he/she must uncheck this option.
- Source attribute has invalid symbol at position N !
The name of the
attribute in the Create source attribute? field of the Extract dialog
does not obey the standard. For details see the XML
recommendation for the valid name standard.
- Error in destination XPath :
The XPath expression is not valid or empty. For details see the XPath messages.
- Error in XPath : XPath Parse Error
The XPath expression in the Source:
field of the XPath Transformation dialog is not valid. For details see the XPath messages.
- Hierarchy error!
This message appears when the user tries to violate the structure of the XML
document. For example the user tries to insert a child of a text node.
- Invalid number format!
An integer value is expected. It defines the position where the value
will be inserted as a child or as a sibling.
- Invalid XML markup in source :
This message occurs when the user creates/modifies the
source which is an XML mark-up. The entered expression is not a valid XML mark-up.
- No elements selected for node name
This message appears when there are no nodes
selected from the source XPath expression.
- No nodes in destination!
This message appears when there are no nodes selected from the
destination XPath expression.
- No nodes left for processing!
This message appears when there are no nodes selected from the
source XPath expression.
- Please write non-empty source expression!
This message appears when there is no source
defined. The source must be an XML mark-up (if XML mark-up check box is selected) or an XPath
expression.
- A possible error in XPath for element number element : element name. The node will
not be processed.
The XPath expression is not valid. For details see the XPath messages
- Sizes not equal!
This message appears when the Check for equal sizes checkbox is
selected and the size of node set defined by the source is not equal to the size of the node set defined by the
destination.
- There is no 0th sibling!
This message appears when the source is pasted as 0 sibling.
Siblings are enumerated starting from 1.
- Duplicated label: label
This message occurs when the user tries to
apply a Multi Query Tool operation over a document. There are more than one labels with equal names.
The label names must be unique for the correct identification of the corresponding label configurations. The
user must rename one of the labels.
- Error in compiling xpath: XPath Parse Error
The XPath expression in the
XPath: field of the Control Operator dialog (MultiQuery Tool Manager dialog) is
not valid. For details see the XPath messages.
- Invalid conditional XPath for Control operator! XPath Parse Error
This
message occurs when the user tries to apply a Multi Query Tool operation over a document.
The xpath attribute of the control node in the query is not valid. For details see the XPath messages.
- Invalid Control type!
This message occurs when the user tries to apply a Multi
Query Tool operation over a document. The type attribute of the control
node in the query is not valid.
- Invalid tool name 'Tool Name' for query: 'Query Name'!
This
message occurs when the user tries to apply a Multi Query Tool operation over a document.
The tool attribute of the control node in the query is not valid.
- No conditional XPath defined!
The XPath expression in the XPath: field
of the Control Operator dialog (MultiQuery Tool Manager dialog) is not
specified.
- No conditional XPath for Control operator!
This message occurs when the user
tries to apply a Multi Query Tool operation over a document. The xpath attribute of
the control node in the query is not specified.
- No queries selected for applying!
This message occurs when the user tries to
apply a Multi Query Tool operation over a document. There are no queries in the Tool Queries
field. The system requires at least one query.
- No target label for Control found!
This message occurs when the user tries
to apply a Multi Query Tool operation over a document. The target attribute of the control
node in the query is not specified.
- No target label selected ! You must assign one before application.
The target
label in the Target: field of the Control Operator dialog (MultiQuery
Tool Manager dialog) is not specified.
- Missing or invalid tool query name!
This message occurs when the user tries
to apply a Multi Query Tool operation over a document. The query name in the query is not
specified or there is no such kind of query name in the system.
- Missing tool name for query: 'Query'!
This message occurs when the user tries to
apply a Multi Query Tool operation over a document. The tool attribute of the query node in
the query is not specified.
- Query file for 'Query Name' not loaded! Reason: Error
This message occurs
when the system tries to load a query, which is not found in the system. Probably it was deleted out of the
system.
- Recursive target-label pair: Target Label!
This message occurs
when the user tries to apply a Multi Query Tool operation over a document. The target label is
used as a label and as a target in one control row in the Tool Queries table of
the MultiQuery Tool Manager dialog.
- Target label 'Lab' used but not defined!
This message occurs when the user tries to
apply a Multi Query Tool operation over a document. The target label Lab is used as a target in the
Info column in the Tool Queries field, but it is not defined as a label in the Label
column.
- The query document 'Query Name' does not appear in a suitable query group for tool Tool
Name
There are several system groups. Each of them can contain only documents with a certain
DTD. Each query has a DTD and is located to a relevant group. The user cannot use documents without a
required query DTD or documents from folders except for Root : SYSTEM : Queries.
- The selected documents either do not represent tool queries, or they do not appear in an appropriate
group.
There are several system groups. Each of them can contain only documents with a certain DTD.
Each query has a DTD and is located to a relevant group. The user cannot use documents without a required
query DTD or documents from folders except for Root : SYSTEM : Queries.
- The system was not able to load query: Error
This message occurs when the system
tries to load a query, which is not found in the system. Probably it was deleted out of the system.