-
implementation-defined
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
Implementation-defined indicates an aspect
that may differ between implementations, but must be specified by
the implementor for each particular implementation.
-
implementation-dependent
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
The term implementation-dependent refers to
a feature where the behavior may vary from one implementation to
another, and where the vendor is not expected to provide a full
specification of the behavior.
-
implementation-dependent
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
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.
-
implementation-dependent
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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) |
Glossary for this
source
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.
- implicit
timezone.
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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.
- import
precedence
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
A declarationD in the stylesheet is defined
to have lower import precedence than another declaration E if the
stylesheet level containing D would be visited before the
stylesheet level containing E in a post-order traversal of the
import tree (that is, a traversal of the import tree in which a
stylesheet level is visited after its children). Two declarations
within the same stylesheet level have the same import
precedence.
- import
tree
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
The stylesheet levels making up a
stylesheet are treated as forming an import tree. In the import
tree, each stylesheet level has one child for each xsl:import
declaration that it contains.
- important
-
From Web Content
Accessibility Guidelines 1.0 (1999-05-05)
| Glossary for
this source
Information in a document is important if
understanding that information is crucial to understanding the
document.
- imports
closure
-
From OWL Web Ontology Language
Guide (2004-02-10)
| Glossary for
this source
the information in an ontology document,
plus the information in the imports closure of ontology documents
that are imported by the document
-
in-scope attribute declarations.
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
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 attribute declarations.
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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).
-
in-scope element declarations.
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
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 element declarations.
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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).
- in-scope
namespaces
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
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
namespaces
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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 components
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
The schema components that may be
referenced by name in a stylesheet are referred to as the in-scope
schema components. This set is the same throughout all the modules
of a stylesheet.
-
in-scope schema definitions.
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
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 definitions.
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
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) |
Glossary for this
source
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.