- implementation-dependent
-
From XQuery 1.0: An XML Query Language (2007-01-23)
Implementation-dependent indicates an aspect that may differ between implementations, is not specified by this or any W3C specification, and is not required to be specified by the implementor for any particular implementation.
- implicit timezone.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
Implicit timezone. This is the timezone to be used when a date, time, or dateTime value that does not have a timezone is used in a comparison or arithmetic operation. The implicit timezone is an implementation-defined value of type xs:dayTimeDuration. See for the range of legal values of a timezone.
- in-scope attribute declarations.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
In-scope attribute declarations. Each attribute declaration is identified either by an expanded QName (for a top-level attribute declaration) or by an implementation-dependent attribute identifier (for a local attribute declaration). If the Schema Import Feature is supported, in-scope attribute declarations include all attribute declarations found in imported schemas.
- in-scope element declarations.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
In-scope element declarations. Each element declaration is identified either by an expanded QName (for a top-level element declaration) or by an implementation-dependent element identifier (for a local element declaration). If the Schema Import Feature is supported, in-scope element declarations include all element declarations found in imported schemas.
- in-scope namespaces
-
From XQuery 1.0: An XML Query Language (2007-01-23)
The in-scope namespaces property of an element node is a set of namespace bindings, each of which associates a namespace prefix with a URI, thus defining the set of namespace prefixes that are available for interpreting QNames within the scope of the element. For a given element, one namespace binding may have an empty prefix; the URI of this namespace binding is the default namespace within the scope of the element.
- in-scope schema definitions.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
In-scope schema definitions. This is a generic term for all the element declarations, attribute declarations, and schema type definitions that are in scope during processing of an expression.
- in-scope schema types.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
In-scope schema types. Each schema type definition is identified either by an expanded QName (for a named type) or by an implementation-dependent type identifier (for an anonymous type). The in-scope schema types include the predefined schema types described in . If the Schema Import Feature is supported, in-scope schema types also include all type definitions found in imported schemas.
- in-scope variables.
-
From XQuery 1.0: An XML Query Language (2007-01-23)
In-scope variables. This is a set of (expanded QName, type) pairs. It defines the set of variables that are available for reference within an expression. The expanded QName is the name of the variable, and the type is the static type of the variable.
- initializing expression
-
From XQuery 1.0: An XML Query Language (2007-01-23)
If a variable declaration includes an expression, the expression is called an initializing expression.
- item
-
From XQuery 1.0: An XML Query Language (2007-01-23)
An item is either an atomic value or a node.
- kind test
-
From XQuery 1.0: An XML Query Language (2007-01-23)
An alternative form of a node test called a kind test can select nodes based on their kind, name, and type annotation.
- library module
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A module that does not contain a Query Body is called a library module. A library module consists of a module declaration followed by a Prolog.
- literal
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A literal is a direct syntactic representation of an atomic value.
- main module
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A main module consists of a Prolog followed by a Query Body.
- MAY
-
From XQuery 1.0: An XML Query Language (2007-01-23)
MAY means that an item is truly optional.
- module
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A module is a fragment of XQuery code that conforms to the Module grammar and can independently undergo the static analysis phase described in . Each module is either a main module or a library module.
- module declaration
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A module declaration serves to identify a module as a library module. A module declaration begins with the keyword module and contains a namespace prefix and a URILiteral.
- module feature
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A conforming XQuery implementation that supports the Module Feature allows a query Prolog to contain a Module Import and allows library modules to be created.
- module import
-
From XQuery 1.0: An XML Query Language (2007-01-23)
A module import imports the function declarations and variable declarations from one or more library modules into the function signatures and in-scope variables of the importing module.
- MUST
-
From XQuery 1.0: An XML Query Language (2007-01-23)
MUST means that the item is an absolute requirement of the specification.