An ordered list of child information items, in document order.
按照文档顺序的子元素信息的有序列表。
In XSLT 2.0, sequences of nodes are not limited to being processed in document order.
在XSLT 2.0中，节点序列允许按照文档顺序以外的顺序处理。
Returns a collection of the sibling elements before this node, in document order.
按文档顺序返回此节点前的同级元素集合。
Returns a filtered collection of the sibling elements after this node, in document order.
按文档顺序返回此节点后经过筛选的同级元素的集合。
Returns a filtered collection of the sibling elements before this node, in document order.
按文档顺序返回此节点前经过筛选的同级元素的集合。
The latter expression will naturally retrieve nodes in document order, whereas the former might not.
后一个表达式将自然地按文档顺序检索节点，而前一个则不是这样。
Returns a filtered collection of the descendant elements for this document or element, in document order.
按文档顺序返回此文档或元素的经过筛选的子代元素集合。
set:trailing returns the nodes in one node-set that come after the first node in the other node-set, in document order.
trailing将返回一个节点集，其中的节点按照文档顺序要比另一个节点集中的第一个节点晚出现。
Set: leading returns the nodes in one node-set that come before the first node in the other node-set, in document order.
leading将返回一个节点集，其中的节点按照文档顺序要比另一个节点集中的第一个节点早出现。
A template that processes all of its children in document order ensures that processing occurs all the way down the source tree.
以文档次序处理其所有子元素的模板确保处理自始至终都沿着源树进行。
However, XSLT 1.0 will not let you do that, because it processes all node-sets in document order or in reverse document order.
但是在XSLT 1.0中做不到，因为只能按照文档顺序或者逆文档顺序处理全部节点集。
It is important to process mixed content in document order; otherwise, you can get completely mangled output, with a changed order of sentence parts.
按照文档顺序处理混合内容非常重要；否则，会导致混乱的输出，并且句子的顺序完全错乱。
Getting a type error where XSL: sort with a select expression obtains more than one value (XSLT 1.0 just selected the first value in document order.)
带有select表达式(返回多个值)的xsl：sort报告类型错误(XSLT 1.0只能按照文档顺序选择第一个值。)
If the XPath expression does return more than one node and you've specified XPathConstants.NODE, then evaluate returns the first node in document order.
如果XPath表达式返回了多个节点并且指定了XPathConstants . NODE，则evaluate按照文档顺序返回第一个节点。
Following an axis from a context node will still return nodes in document order, but once it has those nodes, your stylesheet can reorder them as it requires.
虽然从上下文节点出发沿着某个轴仍然只能按照文档顺序返回节点，但是得到节点之后样式表可以根据需要重新排列节点。
The net result is that if you need to work with only part of the document model (the "first" part, in document order terms), AXIOM delivers great performance.
最后的结论是，如果只需要处理文档模型中的某些部分（如按文档顺序的“第一”部分），AXIOM提供了优秀的性能。
In practice, as you have seen, the result tree is not materialized in memory, so the serializer is handed the nodes of the tree one at a time in document order.
实际上，如您所见，结果树没有在内存中具体化，所以串行化器将按文档顺序一次交出树的一个节点。
Since a parser delivers data in document order (the same order items appear in the XML document text), the on-demand construction implemented by AXIOM requires some clever handling.
因为解析器按照文档顺序(与XML文档文本中项目的出现顺序相同)传递数据，所以AXIOM所实现的按需构造需要某种灵活的处理方法。
Saxon's result tree is not normally materialized in memory — because its nodes are always written in document order, they can be serialized as soon as they are output to the result tree.
Saxon的结果树通常不在内存中具体化——因为它的节点总是按文档顺序编写，一旦将它们输出到结果树中，就可以串行化这些节点。
The database can assign sequence Numbers to each node so that it knows the position of each node and can compare the document order of two nodes in constant time.
数据库可以为每个节点分配顺序号，这样就知道每个节点的位置，可以在常数时间内比较两个节点的文档顺序。
The code gets quite complex because XML elements in SAX are read in order from top to bottom of the XML document.
代码变得十分复杂，因为SAX中的XML元素是按照从顶部到底部的顺序从 XML文档中读取的。
As you can see, the path simply lists the elements in the order in which they appear in the RSS document.
如您所见，路径只是按照元素在RSS文档中出现的顺序直接列出这些元素。
Information in a data document appears in an order that can be anticipated in the code.
数据文档中的信息以可在代码中预料的次序出现。
The default navigation order is the same as the order in which the elements appear in the document; these attributes allow fine-tuning of navigation order.
默认的导航顺序和元素在文档中出现的顺序一致，这些属性可以更精确地调整导航顺序。
Unlike structured data, these documents can have many degrees of freedom in the order of document elements and the way those elements are nested within each other.
与结构化数据不同，这些文档在文档元素的次序和元素相互嵌套的方式方面有很大的自由度。
All nodes exist in the document in the order in which they are added.
文档中所有的节点保持其添加时的顺序。
We have tried to keep the purchase order table schema simple in the relational-only database by storing the purchase order document as a BLOB.
我们已经通过将采购订单文档存储为 BLOB，在基本关系数据库中尽量保持采购订单表模式简单。
The guidelines are written in a short, concise style, in order to keep the volume of the document to a minimum and to facilitate updating.
为了尽量减少文档的卷册，方便更新，准则采用了短小简洁的风格。
The application will describe an interaction in which a purchase order document that's purposely noncompliant with Section 4 encoding is sent using SOAP.
这个应用程序将描述一个交互，在这个交互过程中使用SOAP发送一个故意不遵循Section4编码的购买订单文档。
Since the customer order in the orders.xml XML document contains a list of items, it is represented using two nicknames.
由于orders .xml xml文档中的客户订单包含多个项，因此要使用两个昵称加以表示。
应用推荐