Home → Migration → Ironmark and Oxygen XML Editor

Ironmark and Oxygen XML Editor

Different categories. Meant to coexist.

Oxygen XML Editor (SyncroSoft) is one of the strongest general-purpose XML tools on the market — deep XPath and XSLT tooling, mature schema authoring, the framework model, cross-platform (Windows / macOS / Linux). Ironmark isn't a like-for-like alternative to that; it's a defense-standards technical publications platform that runs a program end-to-end. The two solve different problems, and Ironmark is designed to run alongside Oxygen rather than displace it.

Authors keep the editor they know. Programs gain workflow, review, publishing, traceability, and delivery.

At a glance

What stays the same

• Your source XML. Both read and write the same DTD/schema-conformant content. No proprietary intermediate.
• Schema and BREX validation. Ironmark validates against the project's own schema and BREX rules on demand, whichever editor produced the XML.
• Standard output formats. IADS packages, S1000D-shaped PDFs, IETPs — all industry-standard.
• Cross-platform authoring. Oxygen runs on Windows/macOS/Linux; Ironmark runs in the browser. Neither locks authors to one OS.

What Ironmark adds

Ironmark isn't trying to out-edit Oxygen. The value it adds sits around the editor:

• CSDB with checkout isolation and audit. The working-copy vs released-copy split, checkout locks, change bars, and the full audit trail live in the platform, not in per-author filesystems.
• Structured review workflow. Peer review, IPRF, review queue, auto up-issue on approval — not track-changes stapled onto a document.
• Publishing pipeline in the same tool. PDF, IETP, IADS builds are one click from the same UI that saw the document check in.
• Cross-standard traceability. Parts browser, applicability wizard, cross-DM references, TM Families for paired manuals.
• Customer portal + feedback intake. Branded portal, DA-2028 flow, deliverable delivery + acknowledgment — a first-class surface, not a downstream project.
• Program-level reporting. PM dashboard, per-author health, coverage summaries, top-firing BREX rules.

Where Oxygen keeps its edge

• Deep XML engineering. XSLT and XPath debugging, RelaxNG / XSD design and testing, Schematron rule development — Oxygen's daily job for a decade+. Ironmark's browser editor covers the author-side common shapes; specialist XML developers usually want Oxygen alongside.
• Framework model. Oxygen's custom framework mechanism gives one team a way to tailor the editor per project without touching the tool itself. Ironmark's SDM system covers the analogous need for defense standards, but the two aren't interchangeable.
• DITA, DocBook, TEI, JATS. Oxygen's category is "any XML." Ironmark's is "defense standards." If your program lives on a schema Ironmark doesn't ship an SDM for, Oxygen is likely the right tool.
• Author-standalone workflows. Some teams don't need a CSDB, review queue, or publishing platform — a single author writing structured content in git is a legitimate shape. Oxygen fits that; Ironmark is over-scoped for it.

Using both

The intended fit for most Oxygen-heavy programs is Oxygen as the editor, Ironmark as the platform. The Ironmark Desktop Launcher is a small Windows helper that turns that pairing into a one-click flow: from the Ironmark web UI, Open in Desktop Editor checks the document out, drops the XML into a temp file, and opens it in Oxygen. Each save in Oxygen flushes to the server as a working-copy update; closing Oxygen performs the final check-in.

An author who leaves a checkout open at the end of the day gets a Continue in Desktop button on the checkout banner the next morning — the launcher resumes the existing checkout without creating a new one. Review, applicability, parts, publishing, and portal delivery still flow through the Ironmark server, so nothing about running Oxygen up front changes the rest of the workflow.

System administrators can force per-user API-token auth (rather than browser-minted session tokens) or hide the launcher download entirely when program policy calls for it.

When to keep it simple with Oxygen alone

A single author, a small team on non-defense schemas, an XML-engineering shop building stylesheets and schemas — Ironmark isn't the right tool for those. Oxygen alone (with git) is usually a better fit. The Ironmark story starts making sense when a program has multiple authors, a review workflow, PDF and IADS publish cycles, and a customer or PMO on the other end of the delivery.

Related

← Back to migration guides