locating a file in a hierarchical file system. It is a sequence of one
or more \e{steps} separated by slash '/' or double slash '//'.
Although path expressions are used for traversing XML trees, not file
-systems, in QtXmlPatterms we can model a file system to look like an
+systems, in Qt XML Patterns we can model a file system to look like an
XML tree, so in Qt XML Patterns we can use XQuery to traverse a file
system. See the \l {File System Example} {file system example}.
//! [5]
/*!
- This function is called by the QtXmlPatterns query engine when it
+ This function is called by the Qt XML Patterns query engine when it
wants to move to the next node in the model. It moves along an \a
axis, \e from the node specified by \a nodeIndex.
structure that can be queried as if the data were XML.
The node model represented by a subclass of QAbstractXmlNodeModel is
- meant to be accessed by the QtXmlPatterns query engine. If the API
+ meant to be accessed by the Qt XML Patterns query engine. If the API
seems a little strange in a few places, it is because the member
functions are called by the query engine as it evaluates an
XQuery. They aren't meant to be used programatically.
\section1 Thread Safety
Because the node model can be accessed concurrently by threads in
- the QtXmlPatterns module, subclasses of QAbstractXmlNodeModel must
+ the Qt XML Patterns module, subclasses of QAbstractXmlNodeModel must
be written to be \l{Reentrancy and Thread-Safety}{thread-safe}.
Classes that simplify implementing thread-safety include QReadLocker
and QWriteLocker.
available on AxisAttribute.
The value past in \a axis is not guaranteed based on what is used in
- a query. QtXmlPatterns may call this function arbitrarily with any
- value for \a axis. This is because QtXmlPatterns may rewrite queries
+ a query. Qt XML Patterns may call this function arbitrarily with any
+ value for \a axis. This is because Qt XML Patterns may rewrite queries
to be more efficient, using axes in different ways from the original
query.
/*!
\fn QXmlNodeModelIndex QAbstractXmlNodeModel::nextFromSimpleAxis(SimpleAxis axis, const QXmlNodeModelIndex &origin) const
- When QtXmlPatterns evaluate path expressions, it emulate them through a
+ When Qt XML Patterns evaluate path expressions, it emulate them through a
combination of calls with QSimpleXmlNodeModel::SimpleAxis values. Therefore,
the implementation of this function must return the node, if any, that
appears on the \a axis emanating from the \a origin.
in base64), a date, a float, and an attribute.
QXmlItem is the class that represents these XQuery items in the
- QtXmlPatterns API. A non-null instance of QXmlItem is either a node
+ Qt XML Patterns API. A non-null instance of QXmlItem is either a node
or an atomic value. Calling isNode() or isAtomicValue() tells you
which it is. Atomic values are represented elsewhere in the Qt API
as instances of QVariant, and an instance of QXmlItem that
/*!
Returns the query's URI resolver. If no URI resolver has been set,
- QtXmlPatterns will use the URIs in queries as they are.
+ Qt XML Patterns will use the URIs in queries as they are.
The URI resolver provides a level of abstraction, or \e{polymorphic
URIs}. A resolver can rewrite \e{logical} URIs to physical ones, or
it can translate obsolete or invalid URIs to valid ones.
- QtXmlPatterns calls the URI resolver for all URIs it encounters,
+ Qt XML Patterns calls the URI resolver for all URIs it encounters,
except for namespaces. Specifically, all builtin functions that deal
with URIs (\c{fn:doc()}, and \c{fn:doc-available()}).
Rather than use the URI the user specified, the return value of
QAbstractUriResolver::resolve() will be used.
- When QtXmlPatterns calls QAbstractUriResolver::resolve() the
+ When Qt XML Patterns calls QAbstractUriResolver::resolve() the
absolute URI is the URI mandated by the XQuery language, and the
relative URI is the URI specified by the user.
/*!
Returns the schema's URI resolver. If no URI resolver has been set,
- QtXmlPatterns will use the URIs in schemas as they are.
+ Qt XML Patterns will use the URIs in schemas as they are.
The URI resolver provides a level of abstraction, or \e{polymorphic
URIs}. A resolver can rewrite \e{logical} URIs to physical ones, or
it can translate obsolete or invalid URIs to valid ones.
- When QtXmlPatterns calls QAbstractUriResolver::resolve() the
+ When Qt XML Patterns calls QAbstractUriResolver::resolve() the
absolute URI is the URI mandated by the schema specification, and the
relative URI is the URI specified by the user.
/*!
Returns the schema's URI resolver. If no URI resolver has been set,
- QtXmlPatterns will use the URIs in instance documents as they are.
+ Qt XML Patterns will use the URIs in instance documents as they are.
The URI resolver provides a level of abstraction, or \e{polymorphic
URIs}. A resolver can rewrite \e{logical} URIs to physical ones, or
it can translate obsolete or invalid URIs to valid ones.
- When QtXmlPatterns calls QAbstractUriResolver::resolve() the
+ When Qt XML Patterns calls QAbstractUriResolver::resolve() the
absolute URI is the URI mandated by the schema specification, and the
relative URI is the URI specified by the user.
\class tst_XmlPatternsDiagnosticsTS
\internal
\since 4.5
- \brief Test QtXmlPatterns test suite driver in tests/auto/xmlpatternsxqts/lib/.
+ \brief Test Qt XML Patterns test suite driver in tests/auto/xmlpatternsxqts/lib/.
*/
class tst_XmlPatternsDiagnosticsTS : public tst_SuiteTest
{
\class tst_XmlPatternsXSLTS
\internal
\since 4.5
- \brief Test QtXmlPatterns against W3C's XSL-T 2.0 test suite, XSLTS.
+ \brief Test Qt XML Patterns against W3C's XSL-T 2.0 test suite, XSLTS.
*/
class tst_XmlPatternsXSLTS : public tst_SuiteTest
{