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.
Tihenda XML võrgus
100% privaatne brauseris – failid ei lahku kunagi teie seadmest
Kontrolli ja metaandmed
Operatsioonisüsteemid ja failianalüsaatorid tuvastavad XML faile, kontrollides algset binaarset baidijada:
Baidi-taseme päise allkiri (maagilised baidid)
Operatsioonisüsteemid ja failianalüsaatorid tuvastavad XML faile, kontrollides algset binaarset baidijada:
HEX-ALLKIRI (NIHE 0):
3C 3F 78 6DASCII-ESITUS: <?xm
Standardiseerimine: W3C Recommendation (XML 1.0 Fifth Edition)
Tehnilised andmed
| Konteineri arhitektuur | Hierarchical text markup language with custom semantic tags and attributes |
| Tihendamine | Gzip / Deflate achieves 85%-92% compression on verbose closing tags |
| Baitide järjekord (Endianness) | UTF-8 / UTF-16 character stream determined by XML declaration encoding attribute |
| Värviruumid | Not applicable |
| Kanalid ja struktuur | Elements (<tag>), attributes (attr="val"), CDATA blocks, processing instructions |
| Max mõõtmed | Unbounded hierarchical tree structure |
| Läbipaistvus | Not applicable |
| Voogedastus ja progressiivsus | SAX (Simple API for XML) and StAX parsers enable memory-efficient stream reading |
Tehniline võrdlusmaatriks: XML vs konkurendid
| Tehniline atribuut | XML (Praegune) | 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 |
Levinud riknemisvead ja heksataaste juhend
⚠️ XML Parsing Error: mismatched tag or entity not defined.
Juurpõhjus: Unescaped reserved characters (like '&', '<', or '>') or case mismatch between opening and closing tags.
Taastamine: Replace '&' with '&', '<' with '<', '>' with '>', or wrap arbitrary text inside '<![CDATA[ ... ]]>'' blocks.
Turvaanalüüs ja parsimisründevektorid
XML parsers have historically been one of the most attacked components in enterprise computing due to powerful DTD and entity expansion capabilities.
Teadaolevad ründavektorid
- 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.
Kaitsealased parimad tavad: Always disable external DTD resolution and external entity processing (setFeature 'disallow-doctype-decl' to true) in XML parsers.
Ajalooline taust ja verstapostid
Peamised eelised
- 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).
Tehnilised piirangud ja puudused
- 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.
Huvitavaid tehnilisi fakte
- 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.
Korduma kippuvad tehnilised küsimused
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.