Extensible Markup Language (.xml)

W3C Estándar

Extensible Markup Language (XML) is a versatile markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.

Comprimir XML en línea

Compresión 100% privada en el navegador – los archivos nunca salen de tu dispositivo

Inspeccionar y metadatos

Los sistemas operativos y analizadores de archivos identifican los archivos de XML inspeccionando la secuencia de bytes binarios inicial:

Selecciona o arrastra archivos

Selecciona o arrastra archivos aquí

Conversión 100% privada en el navegador; los archivos nunca salen de tu dispositivo

o pega Ctrl+V
Garantía de privacidad sin transmisión de red: 0 bytes subidos a servidores externos. Todo el procesamiento se realizó de forma local en el entorno seguro de tu navegador.

Firma de cabecera a nivel de bytes (Bytes mágicos)

Los sistemas operativos y analizadores de archivos identifican los archivos de XML inspeccionando la secuencia de bytes binarios inicial:

FIRMA HEXADECIMAL (DESPLAZAMIENTO 0):

3C 3F 78 6D

REPRESENTACIÓN ASCII: <?xm

Estandarización: W3C Recommendation (XML 1.0 Fifth Edition)

Especificaciones técnicas

Arquitectura del contenedorHierarchical text markup language with custom semantic tags and attributes
CompresiónGzip / Deflate achieves 85%-92% compression on verbose closing tags
Orden de bytes (Endianness)UTF-8 / UTF-16 character stream determined by XML declaration encoding attribute
Espacios de colorNot applicable
Canales y estructuraElements (<tag>), attributes (attr="val"), CDATA blocks, processing instructions
Dimensiones máximasUnbounded hierarchical tree structure
TransparenciaNot applicable
Streaming y progresivoSAX (Simple API for XML) and StAX parsers enable memory-efficient stream reading

Matriz de comparación técnica: XML frente a la competencia

Atributo técnicoXML (Actual)JSONYAMLProtocol Buffers
VerbosityHigh (closing tags and attribute syntax)Low (compact key-value format)Low (indentation-based)Ultra-low (binary serialization)
Schema ValidationMature XSD & DTD standards with compiler enforcementJSON Schema (optional)JSON Schema / Yaml schemasStrict .proto schema definitions
NamespacesNative XML namespaces (xmlns) supportNo native namespace mechanismNo native namespace mechanismPackage declarations
TransformationsXSLT declarative transformation pipelinesCustom code / jq scriptsCustom codeCustom code

Modos de corrupción comunes y guía de recuperación hexadecimal

⚠️ XML Parsing Error: mismatched tag or entity not defined.

Causa raíz: Unescaped reserved characters (like '&', '<', or '>') or case mismatch between opening and closing tags.

Recuperación: Replace '&' with '&amp;', '<' with '&lt;', '>' with '&gt;', or wrap arbitrary text inside '<![CDATA[ ... ]]>'' blocks.

Análisis de seguridad y vectores de ataque al analizador

XML parsers have historically been one of the most attacked components in enterprise computing due to powerful DTD and entity expansion capabilities.

Vectores de ataque conocidos

  • XML External Entity (XXE): Malicious DOCTYPE referencing local server files ('file:///etc/passwd') or internal network endpoints.
  • Billion Laughs Attack (XML Bomb): Nested entity declarations expanding exponentially in memory to cause denial of service.
  • XPath Injection: Unsanitized user inputs allowing unauthorized querying of XML databases.

Mejores prácticas defensivas: Always disable external DTD resolution and external entity processing (setFeature 'disallow-doctype-decl' to true) in XML parsers.

Orígenes históricos e hitos

2008W3C publishes XML 1.0 Fifth Edition, standardizing modern international character support.
1998W3C publishes XML 1.0 Recommendation as a simplified, web-friendly subset of SGML.

Ventajas clave y pros

  • Rigorous schema validation using XSD (XML Schema Definition) or DTD ensures strict data integrity.
  • Namespaces (xmlns) prevent element name collisions in complex multi-source documents.
  • Powerful querying and transformation toolchains (XPath, XSLT, XQuery).

Limitaciones técnicas y contras

  • Extremely verbose: closing tags repeat element names, creating large file sizes and high bandwidth consumption.
  • DOM parsing builds large memory-intensive object trees.
  • Prone to XML External Entity (XXE) and entity expansion security vulnerabilities.

Curiosidades técnicas interesantes

  • XML is a simplified subset of SGML (Standard Generalized Markup Language), designed to work seamlessly over the World Wide Web.
  • Modern office documents (.docx, .xlsx), vector images (.svg), and RSS feeds are all specialized XML dialects.

Preguntas técnicas frecuentes

What is the difference between well-formed and valid XML?

'Well-formed' XML follows the basic syntax rules (matching tags, quotes around attributes, single root element). 'Valid' XML is well-formed AND adheres strictly to an external schema definition (XSD or DTD).

Why did JSON replace XML for most web APIs?

JSON maps directly to native JavaScript and programming language data structures (hash maps and arrays) with much less boilerplate, faster parsing, and smaller network payloads.