VTD-XML
software
Virtual Token Descriptor for eXtensible Markup Language (VTD-XML) refers to a collection of cross-platform XML processing technologies centered on a non-extractive XML, "document-centric" parsing technique called Virtual Token Descriptor (VTD). Depending on the perspective, VTD-XML can be viewed as one of the following:
A "Document-Centric" XML parser
A native XML indexer or a file format that uses binary data to enhance the text XML
An incremental XML content modifier
An XML slicer/splitter/assembler
An XML editor/eraser
A way to port XML processing on chip
A non-blocking, stateless XPath evaluator
VTD-XML is developed by XimpleWare and dual-licensed under GPL and proprietary license. It was originally written in Java, but is now available in C, C++ and C#.
Basic concept
Non-extractive, document-centric parsing
Traditionally, a lexical analyzer represents tokens (the small units of indivisible character values) as discrete string objects. This approach is designated extractive parsing. In contrast, non-extractive tokenization mandates that one keeps the source text intact, and uses offsets and lengths to describe those tokens.
Virtual token descriptor
Virtual Token Descriptor (VTD) applies the concept of non-extractive, document-centric parsing to XML processing. A VTD record uses a 64-bit integer to encode the offset, length, token type and nesting depth of a token in an XML document. Because all VTD records are 64 bits in length, they can be stored efficiently and managed as an array.
Location cache
Location Caches (LC) build on VTD records to provide efficient random access.
Begin with the source’s own compact description: “VTD-XML” is software. The dossier treats that line as a proposition to test through VTD-XML and software, not as a finished interpretation.
Why this record matters
The phrase “software” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Jul 31, 2026. The linked authority identifier is Q7907612. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “VTD-XML”, its source revision and the description used here.
- Expand the search: follow VTD-XML primary sources, VTD-XML archive and VTD-XML research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “VTD-XML”?
- Has classification or technical consensus changed since the cited source?
- Is the terminology current, historical or disputed?
Search terms from this dossier
This entry incorporates text from “VTD-XML” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.