Extensible Markup Language (.xml)
W3C StandartsExtensible 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.
Saspiest XML tiešsaistē
100% privāta saspiešana pārlūkprogrammā – faili nekad nepamet jūsu ierīci
Pārbaudīt un metadati
Operētājsistēmas un failu analizatori identificē XML failus, pārbaudot sākotnējo bināro baitu secību:
Baitu līmeņa galvenes paraksts (maģiskie baiti)
Operētājsistēmas un failu analizatori identificē XML failus, pārbaudot sākotnējo bināro baitu secību:
HEKSADECIMĀLAIS PARAKSTS (NOBĪDE 0):
3C 3F 78 6DASCII ATTEIOLOJUMS: <?xm
Standartizācija: W3C Recommendation (XML 1.0 Fifth Edition)
Tehniskās specifikācijas
| Konteinera arhitektūra | Hierarchical text markup language with custom semantic tags and attributes |
| Saspiešana | Gzip / Deflate achieves 85%-92% compression on verbose closing tags |
| Baitu secība | UTF-8 / UTF-16 character stream determined by XML declaration encoding attribute |
| Krāsu telpas | Not applicable |
| Kanāli un struktūra | Elements (<tag>), attributes (attr="val"), CDATA blocks, processing instructions |
| Maks. izmēri | Unbounded hierarchical tree structure |
| Caurspīdīgums | Not applicable |
| Straumēšana un progresīvā ielāde | SAX (Simple API for XML) and StAX parsers enable memory-efficient stream reading |
Tehniskā salīdzinājuma matrica: XML pret konkurentiem
| Tehniskais atribūts | XML (Pašreizējais) | 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 |
Biežākie bojājumu veidi un heksadecimālās atkopšanas ceļvedis
⚠️ XML Parsing Error: mismatched tag or entity not defined.
Pamatcēlonis: Unescaped reserved characters (like '&', '<', or '>') or case mismatch between opening and closing tags.
Atkopšana: Replace '&' with '&', '<' with '<', '>' with '>', or wrap arbitrary text inside '<![CDATA[ ... ]]>'' blocks.
Drošības analīze un parsētāja uzbrukuma vektori
XML parsers have historically been one of the most attacked components in enterprise computing due to powerful DTD and entity expansion capabilities.
Zināmie uzbrukuma vektori
- 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.
Aizsardzības labākā prakse: Always disable external DTD resolution and external entity processing (setFeature 'disallow-doctype-decl' to true) in XML parsers.
Vēsturiskā izcelsme un pavērsieni
Galvenās priekšrocības un plusi
- 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).
Tehniskie ierobežojumi un mīnusi
- 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.
Interesanti tehniski fakti
- 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.
Bieži uzdotie tehniskie jautājumi
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.