Extensible Markup Language (.xml)
W3C StandardExtensible 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.
Komprimer XML på nett
100% privat i nettleseren – filer forlater aldri enheten din
Undersøk og metadata
Operativsystemer og filanalysatorer identifiserer XML-filer ved å undersøke den innledende binære bytesekvensen:
Byte-nivå hodesignatur (Magic Bytes)
Operativsystemer og filanalysatorer identifiserer XML-filer ved å undersøke den innledende binære bytesekvensen:
HEX-SIGNATUR (OFFSET 0):
3C 3F 78 6DASCII-REPRESENTASJON: <?xm
Standardisering: W3C Recommendation (XML 1.0 Fifth Edition)
Tekniske spesifikasjoner
| Beholderarkitektur | Hierarchical text markup language with custom semantic tags and attributes |
| Komprimering | Gzip / Deflate achieves 85%-92% compression on verbose closing tags |
| Bytterekkefølge | UTF-8 / UTF-16 character stream determined by XML declaration encoding attribute |
| Fargerom | Not applicable |
| Kanaler og struktur | Elements (<tag>), attributes (attr="val"), CDATA blocks, processing instructions |
| Maks. dimensjoner | Unbounded hierarchical tree structure |
| Gjennomsiktighet | Not applicable |
| Strømming og progressiv | SAX (Simple API for XML) and StAX parsers enable memory-efficient stream reading |
Teknisk sammenligningsmatrise: XML vs konkurrenter
| Teknisk attributt | XML (Gjeldende) | JSON | YAML | Protocol Buffers |
|---|---|---|---|---|
| Verbosity | High (closing tags and attribute syntax) | Low (compact key-value format) | Low (indentation-based) | Ultra-low (binary serialization) |
| Schema Validation | Mature XSD & DTD standards with compiler enforcement | JSON Schema (optional) | JSON Schema / Yaml schemas | Strict .proto schema definitions |
| Namespaces | Native XML namespaces (xmlns) support | No native namespace mechanism | No native namespace mechanism | Package declarations |
| Transformations | XSLT declarative transformation pipelines | Custom code / jq scripts | Custom code | Custom code |
Vanlige korrupsjonsmoduser og heksadesimal gjenopprettingsveiledning
⚠️ XML Parsing Error: mismatched tag or entity not defined.
Underliggende årsak: Unescaped reserved characters (like '&', '<', or '>') or case mismatch between opening and closing tags.
Utbedring: Replace '&' with '&', '<' with '<', '>' with '>', or wrap arbitrary text inside '<![CDATA[ ... ]]>'' blocks.
Sikkerhetsanalyse og parser-angrepsvektorer
XML parsers have historically been one of the most attacked components in enterprise computing due to powerful DTD and entity expansion capabilities.
Kjente angrepsvektorer
- 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.
Beste praksis for forsvar: Always disable external DTD resolution and external entity processing (setFeature 'disallow-doctype-decl' to true) in XML parsers.
Historisk opprinnelse og milepæler
Viktige fordeler
- 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).
Tekniske begrensninger og ulemper
- 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.
Interessante tekniske fakta
- 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.
Ofte stilte tekniske spørsmål
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.