XML tree

XML documents have a hierarchical structure and can conceptually be interpreted as a tree structure, called an XML tree.

XML documents must contain a root element (one that is the parent of all other elements). All elements in an XML document can contain sub elements, text and attributes. The tree represented by an XML document starts at the root element and branches to the lowest level of elements. Although there is no consensus on the terminology used on XML Trees, at least two standard terminologies have been released by the W3C:

XPath defines a syntax named XPath expressions that identifies one or more internal components (elements, attributes, etc.) of an XML document. XPath is widely used to accesses XML-encoded data.

The XML Information Set, or XML infoset, describes an abstract data model for XML documents in terms of information items. It is often used in the specifications of XML languages, for its convenience in describing constraints on constructs those languages allow.

Representation as trees

In mathematics, a tree is an undirected graph in which any two vertices are connected by exactly one simple path. Any connected graph without simple cycles is a tree. A tree data structure simulates a hierarchical tree structure with a set of linked nodes. A hierarchy consists of an order defined on a set. The term hierarchy is used to stress a hierarchical relation among the elements.

The XML specification defines an XML document as a well-formed text if it satisfies a list of syntax rules defined in the specification. This specification is long, however 2 key points relating to the tree structure of an XML document are:

  • The begin, end, and empty-element tags that delimit the elements are correctly nested, with none missing and none overlapping
  • A single "root" element contains all the other elements

These features resemble those of trees, in that there is a single root node, and an order to the elements. XML has appeared as a first-class data type in other languages. The JavaScript (E4X) extension explicitly defines two specific objects (XML and XMLList), which support XML document nodes and XML node lists as distinct objects and use a dot-notation specifying parent-child relationships. [1] These data structures represent XML documents as a tree structure.

An XML Tree represented graphically can be as simple as an ASCII chart or a more graphically complex hierarchy. For instance, the XML document and the ASCII tree have the same structure. XML Trees do not show the content in an Instance document, only the structure of the document. In this example Product is the Root Element of the tree and the two child nodes of Product are Name and Details. Details contains two child nodes, Description and Price. The tree command in Windows and *nix also produce a similar tree structure and path.

Product
├───Name
└───Details
    └───Description
    └───Price

1 <Product>
2     <Name>Widget</Name>
3     <Details>
4         <Description>
5             This Widget is the highest quality widget. 
6         </Description>
7         <Price>5.50</Price>
8     </Details>
9 </Product>

XPath Data Model

XPath, the XML Path Language, is a query language for selecting nodes from an XML document. XPath defines a syntax named XPath expressions that can query an XML document for one or more internal components (elements, attributes, etc.). XPath is widely used in other core-XML specifications and in programming libraries for accessing XML-encoded data. [2]

XPath Data Model terminology

The XPath Data Model is a long specification, and goes into many features unrelated to XML trees. Listed below are key terms from that specification and the XML specification.[3][4]

Instance
The data model represented as a sequence.
Instance document
A document using and conforming to the same sequence/XML tree.
Sequence
An order collection of zero or more items. A sequence cannot be a member of a sequence. A single item appearing individually is modeled as a sequence containing one item.
Element
A node within the sequence that may contain
Node
Any item represented in the XML tree/sequence.
Root Node
The topmost element of the tree. All other elements and nodes must be contained within the root node.
Item
A node or an atomic value.
Value space
The part of an item that contains data rather than additional elements.
Atomic type
A primitive simple type or a type derived by restriction from another atomic type.
Atomic value
A value contained in the value space that is an atomic type.
QName
The qualified name of an element. It must conform to naming rules of XML objects. (i.e. must start with a letter or underscore, case-sensitive, cannot start with the letters xml(in any case), can contain letters, digits, hyphens, underscores, and periods, cannot contain spaces.)
Expanded-QName
The fully qualified name of an element. It may include a prefix and namespace. It must include the local name of the element.

Within a given tree, document order satisfies the following constraints:[5]

  • The root node is the first node.
  • Every node occurs before all of its children and descendants.
  • Namespace Nodes immediately follow the Element Node with which they are associated. The relative order of Namespace Nodes is stable but implementation-dependent.
  • Attribute Nodes immediately follow the Namespace Nodes of the element with which they are associated. If there are no Namespace Nodes associated with a given element, then the Attribute Nodes associated with that element immediately follow the element. The relative order of Attribute Nodes is stable but implementation-dependent.
  • The relative order of siblings is the order in which they occur in the children property of their parent node.
  • Children and descendants occur before following siblings.

XML Information Set

XML Information Set (XML Infoset) describes an abstract data model of an XML document in terms of a set of information items. The definitions in the XML Information Set specification are meant to be used in other specifications that need to refer to the information in a well-formed XML document. The infoset makes it convenient to describe constraints on the XML constructs other XML languages allow. An XML document has an information set if it is well-formed and satisfies the namespace constraints. An information set can contain up to eleven different types of information items:

  • The Document Information Item (always present)
  • Element Information Items
  • Attribute Information Items
  • Processing Instruction Information Items
  • Unexpanded Entity Reference Information Items
  • Character Information Items
  • Comment Information Items
  • The Document Type Declaration Information Item
  • Unparsed Entity Information Items
  • Notation Information Items
  • Namespace Information Items [6]

XML Information Set terminology

The XML Information Set is a long specification, and goes into many features unrelated to XML trees. Listed below are the most important terms relating to XML tree terminology:

"There is exactly one document information item in the information set, and all other information items are accessible from the properties of the document information item, either directly or indirectly through the properties of other information items. The document information item has the following properties:

  • [children]
  • [document element]
  • [notations]
  • [unparsed entities]
  • [base URI]
  • [character encoding scheme]
  • [standalone]
  • [version]
  • [all declarations processed]

There is an element information item for each element appearing in the XML document. One of the element information items is the value of the [document element] property of the document information item, corresponding to the root of the element tree, and all other element information items are accessible by recursively following its [children] property. An element information item has the following properties:

  • [namespace name]
  • [local name]
  • [prefix]
  • [children]
  • [attributes]
  • [namespace attributes]
  • [in-scope namespaces]
  • [base URI]
  • [parent]

There is an attribute information item for each attribute (specified or defaulted) of each element in the document, including namespace declarations. The latter however appear as members of an element's [namespace attributes] property rather than its [attributes] property. Attributes declared in the DTD with no default value and not specified in the element's start tag are not represented by attribute information items. An attribute information item has the following properties:

  • [namespace name]
  • [local name]
  • [prefix]
  • [normalized value]
  • [specified]
  • [attribute type]
  • [references]
  • [owner element][7]

Notes
  1. "Processing XML with E4X". Mozilla Developer Center. Mozilla Foundation.
  2. XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition), 14 December 2010, http://www.w3.org/TR/xpath-datamodel/
  3. XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition), 14 December 2010, http://www.w3.org/TR/xpath-datamodel/
  4. Extensible Markup Language (XML) 1.0 (Fifth Edition), 26 November 2008, retrieved: 24 July 2018, https://www.w3.org/TR/xml/REC-xml-20081126-review.html#sec-terminology
  5. XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition), 14 December 2010, http://www.w3.org/TR/xpath-datamodel/
  6. XML Information Set (Second Edition), February 4 2004, http://www.w3.org/TR/xml-infoset/
  7. XML Information Set (Second Edition), February 4 2004, http://www.w3.org/TR/xml-infoset/
gollark: I called the bald thing arbitrary, I suppose both apply.
gollark: Also, it's more "not under your control" than "arbitrary".
gollark: I disagree with premise #3 there.
gollark: Yes, one (1) l.
gollark: I believe this to be a "footbal metaphor".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.