Reverse Nimzoa typed JSON/XML documents or preserve arbitrary XML elements, attributes, namespaces and mixed-content ordering in a separate JSON representation.
LOCAL INPUT
Well-formed XML · mapping chosen during conversion
COMPUTED OUTPUT
TRANSFORM & CHECK
Nimzoa typed documents are recognized by the mapping namespace/version and reversed to original supported JSON types. Other XML uses {$xml:{representation:"ordered-xml-v1",children:[...]}} with ordered element/text/CDATA/comment/processing-instruction nodes, attribute arrays and namespace metadata. Whitespace inside elements is retained, XML line endings/entities normalize, and this is not universal byte-lossless XML conversion. DTD/entity declarations are rejected before parsing; no resources are fetched.
Inputs are bounded to 200,000 UTF-8 bytes. JSON values use JavaScript numeric precision; nonfinite values and unsafe integers are rejected, and exact large numbers should be strings. JSON nesting is limited to 64 levels and 10,000 values. Output is bounded to 1 MB. Files are decoded locally as UTF-8. Nothing is uploaded to a calculation service; clipboard and downloads require an explicit action.
Enter your values locally; no inputs are uploaded.
Check validation feedback before reviewing the browser-generated result.
Review the explanation, copy supported outputs or reset the workspace.
Paste or import supported UTF-8 documents, review live validation, run the named action, then inspect and export the computed output.
It recognizes the explicit mapping namespace and version, validates its container/primitive metadata and reverses supported values. Malformed typed mappings are rejected instead of silently falling back to a different representation.
Documents are processed locally in browser memory, without an external calculation-processing API or server upload. File import, clipboard and download happen only through explicit actions. Ordinary website requests may still be logged; no persistent document profile is created.
It recognizes the explicit mapping namespace and version, validates its container/primitive metadata and reverses supported values. Malformed typed mappings are rejected instead of silently falling back to a different representation.
Arbitrary supported XML uses an ordered $xml document representation. Element nodes retain names, local names, prefixes, namespace URIs, ordered attribute arrays and ordered children, rather than guessing scalar JSON types from text.
Yes. Children remain an ordered array of element, text, CDATA, comment and processing-instruction nodes. Repeated elements are not overwritten by duplicate JSON object keys, and text around nested elements remains in order.
Attributes retain their qualified names, values and namespace information, including namespace declarations. Unprefixed attributes are not incorrectly assigned the default element namespace; undeclared prefixes and duplicate expanded-name attributes are rejected.
No. DTD and entity declarations are rejected before parsing. Only predefined XML entities and valid numeric character references are supported. XML is displayed as text, not inserted into a live page or used to fetch schemas/stylesheets.
No. XML line endings and entity references normalize according to parsing semantics, and unsupported declarations are rejected. The tool preserves supported document information and ordering, not every lexical spelling, encoding or arbitrary XML standard feature.