WebToolArcWhat this XML step proves
Use the tree to understand structure before transforming it.
What to review before handoff
Repeated siblings, namespace mappings and mixed content often determine whether JSON/CSV conversion is safe.
XML Tools
XML Viewer & Tree
Inspect parsed XML structure without uploading the document, then use the review to spot namespaces, repeated records and mixed content.
—Root
—Elements
—Attributes
—Depth
ReadyText tree is capped for large documents and is intended for inspection, not editing the original byte stream.
XML structure & handoff review
Reviewing…Parse the document you will actually use
Check structure, namespaces, repeated records, mixed content and remote-looking references. Converter pages review generated XML output when that is the handoff artifact.
Review scope—
Root—
Elements—
Namespaces—
UTF-8 bytes—
Structural findings
Copyable handoff summary
Reviewing current XML…
Browser DOM parsing checks well-formedness and structure. It is not an XSD/DTD/business-rule validator, sanitizer or permission to trust remote resources; this review does not fetch external schemas or entities.
XML Viewer: Indexed Paths & Structure Audit
Format XML and inspect indexed element paths, attributes, leaf nodes, namespaces and document structure locally.
Structure workspace
Collapsible tree, XPath and search
Reuse the current XML source and parser to inspect hierarchy, query nodes and search indexed paths without changing the document.
—Elements
—Attributes
—Max depth
—XPath matches
Tree
XPath / search evidence
Uses the same browser-local XML source and WTAXml67 parser as the existing viewer.
Practical guide and verification
Use the tool first, then use these checks to interpret, verify and hand off the result without turning explanatory content into the primary workflow.
Use the tree to understand structure before editing
The collapsible view exposes parent/child relationships, attributes and short text previews without flattening the document. Expand only the branch you need, then compare the visible hierarchy with the raw XML before making a transformation so repeated elements and nested containers are not mistaken for flat records.
Use XPath as a query, not as a mutation
The XPath workspace evaluates expressions against the current browser-parsed document and lists matching nodes or scalar results. It does not rewrite the XML. Preserve the expression with the source document when it becomes part of a repeatable extraction or QA workflow.
Treat namespaces as part of element identity
Two elements with the same local name can belong to different namespaces. Default namespaces are especially easy to overlook in XPath work. If a query unexpectedly returns no nodes, inspect namespace evidence first instead of changing the XML simply to make an unqualified expression match.
Keep external references and parser limits in scope
A browser viewer can parse the text you provide, but it does not prove that remote schemas, external entities, linked resources, or application-specific processing will behave the same way elsewhere. Use the structural stats and reference audit as evidence about this document, then validate downstream behavior in the target system.