XML Markup Language Cheat Sheet

Updated 2026-05-16

Next Topic: YAML Data Serialization Language Cheat Sheet

🧠Study flashcards on this topic125 cards · spaced repetition→

XML (eXtensible Markup Language) is a markup specification developed by the W3C for storing and transporting structured data in a text-based, human-readable format. Unlike HTML, which focuses on presentation, XML is designed purely for data representation — it provides strict syntax rules (well-formedness), optional schema validation for structural integrity, and namespace mechanisms for avoiding element conflicts. Key consideration: while XML's flexibility and self-describing nature made it a standard for web services (SOAP), configuration files (Maven, Spring), and document formats (SVG, XHTML), its verbose syntax and parsing overhead have led many modern APIs to favor JSON; however, XML remains essential when schema validation, document processing (XPath/XSLT), and complex hierarchies are required.

What This Cheat Sheet Covers

This topic spans 19 focused tables and 135 indexed concepts, 125 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core XML SyntaxTable 2: Character Handling and EntitiesTable 3: NamespacesTable 4: Well-Formedness and ValidityTable 5: Document Type Definition (DTD)Table 6: XML Schema Definition (XSD) BasicsTable 7: XSD Compositors and StructureTable 8: XSD Restrictions and FacetsTable 9: XSD ModularizationTable 10: XPath BasicsTable 11: XPath AxesTable 12: XPath FunctionsTable 13: XPath Operators and Node TestsTable 14: XSLT Core ElementsTable 15: XSLT Advanced FeaturesTable 16: XML Parsing ApproachesTable 17: XML Security ConsiderationsTable 18: Common XML Use CasesTable 19: XML Tools and Standards

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: Core XML Syntax

The building blocks every XML document is made of — elements, attributes, the single root, and proper nesting. Master these and you can read or write any XML by hand; the strict rules here are exactly what make a document "well-formed" before any schema even enters the picture.

Element	Example	Description
XML Declaration	`<?xml version="1.0" encoding="UTF-8"?>`	• Optional first line specifying XML version (1.0 or 1.1) and character encoding (typically UTF-8) • the `standalone` attribute indicates whether external definitions are required (`yes` or `no`).
Element	`<book>Clean Code</book>`	• Basic building block consisting of start tag, content, and end tag • element names are case-sensitive and must start with a letter or underscore
Empty Element	or `<img src="logo.png"/>`	• Self-closing tag with no content between opening and closing • the slash before `>` is mandatory for well-formedness
Attribute	`<book id="101" lang="en">`	• Name-value pair inside a start tag providing metadata about the element • attribute values must be quoted (single or double quotes).
Root Element	`<library>` `<book/>` `</library>`	• Single top-level element that contains all other elements • every well-formed XML document must have exactly one root element
Nested Elements	`<book>` `<title>XML Guide</title>` `</book>`	• Elements contained within other elements creating a hierarchical tree structure • elements must be properly nested (no overlapping).
Text Content	`<title>Learning XML</title>`	• Character data between opening and closing tags • whitespace is preserved by default unless processed by an application
Comments	`<!-- This is a comment -->`	• Non-parsed text ignored by XML processors • comments cannot contain `--` and cannot be nested inside other comments

Table 2: Character Handling and Entities

A few characters like < and & are reserved, so XML needs entities and CDATA sections to carry them as literal text. Beyond escaping, entities double as reusable text macros — and external entities are also the root of the notorious XXE vulnerability, which is why they resurface in the security table.

Concept	Example	Description
Predefined Entities	`< > & ' "`	• Five built-in entity references for reserved XML characters: `<` becomes `&lt` `•`, `>` becomes `&gt` `•`, `&` becomes `&amp` `•`, `'` becomes `&apos` `•`, `"` becomes `&quot` `•`.

The rest of this section is part of the full cheat sheet

Table 3: Namespaces

When documents combine vocabularies — say SVG inside XHTML — namespaces keep identically named elements from colliding by binding them to a URI. The key mental shift is that the namespace URI is just a unique identifier, not an address to fetch anything from.

Feature	Example	Description
Namespace Declaration	`<root xmlns="http://example.com/ns">`	• Associates elements with a namespace URI to prevent name collisions • the URI is an identifier, not a location to retrieve data

The rest of this section is part of the full cheat sheet

Table 4: Well-Formedness and Validity

These are two separate bars an XML document can clear. Well-formed means it obeys the syntax rules; valid means it additionally conforms to a schema like a DTD or XSD. A document can be perfectly well-formed yet invalid, and grasping that distinction is central to how XML processing works.

Concept	Example	Description
Well-Formed XML	Document with proper syntax	• XML that follows syntax rules: single root, proper nesting, quoted attributes, case-sensitive tags, and closed elements • parsers reject malformed documents

The rest of this section is part of the full cheat sheet

Table 1: Core XML Syntax

Element	Example	Description
XML Declaration	`<?xml version="1.0" encoding="UTF-8"?>`	• Optional first line specifying XML version (1.0 or 1.1) and character encoding (typically UTF-8) • the `standalone` attribute indicates whether external definitions are required (`yes` or `no`).
Element	`<book>Clean Code</book>`	• Basic building block consisting of start tag, content, and end tag • element names are case-sensitive and must start with a letter or underscore
Empty Element	or `<img src="logo.png"/>`	• Self-closing tag with no content between opening and closing • the slash before `>` is mandatory for well-formedness
Attribute	`<book id="101" lang="en">`	• Name-value pair inside a start tag providing metadata about the element • attribute values must be quoted (single or double quotes).
Root Element	`<library>` `<book/>` `</library>`	• Single top-level element that contains all other elements • every well-formed XML document must have exactly one root element
Nested Elements	`<book>` `<title>XML Guide</title>` `</book>`	• Elements contained within other elements creating a hierarchical tree structure • elements must be properly nested (no overlapping).
Text Content	`<title>Learning XML</title>`	• Character data between opening and closing tags • whitespace is preserved by default unless processed by an application
Comments	`<!-- This is a comment -->`	• Non-parsed text ignored by XML processors • comments cannot contain `--` and cannot be nested inside other comments

Table 2: Character Handling and Entities

Concept	Example	Description
Predefined Entities	`< > & ' "`	• Five built-in entity references for reserved XML characters: `<` becomes `&lt` `•`, `>` becomes `&gt` `•`, `&` becomes `&amp` `•`, `'` becomes `&apos` `•`, `"` becomes `&quot` `•`.

Table 3: Namespaces

Feature	Example	Description
Namespace Declaration	`<root xmlns="http://example.com/ns">`	• Associates elements with a namespace URI to prevent name collisions • the URI is an identifier, not a location to retrieve data

Table 4: Well-Formedness and Validity

Concept	Example	Description
Well-Formed XML	Document with proper syntax	• XML that follows syntax rules: single root, proper nesting, quoted attributes, case-sensitive tags, and closed elements • parsers reject malformed documents