Extensible Markup Language (.xml)
W3C 標準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.
XMLをオンラインで圧縮
ブラウザ内100%ローカル圧縮 — ファイルが外部サーバーに送信されることはありません
調査とメタデータ
オペレーティングシステムやファイル解析ツールは、先頭のバイナリバイトシーケンスを検査することで XML ファイルを識別します:
バイトレベルのヘッダーシグネチャ (マジックバイト)
オペレーティングシステムやファイル解析ツールは、先頭のバイナリバイトシーケンスを検査することで XML ファイルを識別します:
16進数シグネチャ (オフセット 0):
3C 3F 78 6DASCII表現: <?xm
標準化: W3C Recommendation (XML 1.0 Fifth Edition)
技術仕様
| コンテナアーキテクチャ | Hierarchical text markup language with custom semantic tags and attributes |
| 圧縮 | Gzip / Deflate achieves 85%-92% compression on verbose closing tags |
| バイトエンディアン | UTF-8 / UTF-16 character stream determined by XML declaration encoding attribute |
| 色空間 | Not applicable |
| チャンネルと構造 | Elements (<tag>), attributes (attr="val"), CDATA blocks, processing instructions |
| 最大寸法 | Unbounded hierarchical tree structure |
| 透過性 | Not applicable |
| ストリーミングとプログレッシブ | SAX (Simple API for XML) and StAX parsers enable memory-efficient stream reading |
技術比較マトリックス: XML 対 競合製品
| 技術属性 | XML (現在) | 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 |
一般的な破損モードと16進数リカバリガイド
⚠️ XML Parsing Error: mismatched tag or entity not defined.
根本原因: Unescaped reserved characters (like '&', '<', or '>') or case mismatch between opening and closing tags.
復旧: Replace '&' with '&', '<' with '<', '>' with '>', or wrap arbitrary text inside '<![CDATA[ ... ]]>'' blocks.
セキュリティ分析とパーサー攻撃ベクトル
XML parsers have historically been one of the most attacked components in enterprise computing due to powerful DTD and entity expansion capabilities.
既知の攻撃ベクター
- 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.
防御的ベストプラクティス: Always disable external DTD resolution and external entity processing (setFeature 'disallow-doctype-decl' to true) in XML parsers.
歴史的背景とマイルストーン
主な利点とメリット
- 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).
技術的な制限とデメリット
- 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.
興味深い技術トリビア
- 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.
よくある技術的な質問
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.