S1000D and WebCGM

S1000D and WebCGM conversion workflows

S1000D and WebCGM programs run strict illustration QA. Reforge converts CGM to SVG against the profile the file claims to be, and flags the constructs that won't survive — before the SVG hits the publication step.

Common S1000D/WebCGM conversion risks

  • Mixed profile usage across legacy and new illustration sets.
  • Output drift in text metrics and stroke rendering after conversion.
  • Late discovery of invalid source files during release windows.
  • Difficulty reproducing conversion behavior across team members.

Supported S1000D and WebCGM profiles

Reforge treats each S1000D issue and the WebCGM standard as a discrete profile. Each applies the appropriate CGM element restrictions, hotspot handling rules, and APS attribute conventions for that issue level:

  • S1000D Issue 4.0 — CGM ATA variant with standard S1000D hotspot conventions.
  • S1000D Issue 5.0 — updated CGM profile alignment and DM reference handling.
  • S1000D Issue 6.0 — current issue with full APS region and view context support.
  • WebCGM 2.1 — W3C profile with link, region, and viewcontext element preservation.
  • ATA iSpec 2200 — for ATA-origin S1000D programs using ATA markup conventions.

Auto-detect mode works across all of these. For programs where files must always conform to a specific issue level, use an explicit profile selection (--profile s1000d on the CLI or the Profile Override setting in the desktop app) to enforce that issue's rules in both validation and conversion.

Profile detection in mixed-origin archives

S1000D programs often receive CGM files from multiple illustration vendors or convert legacy archives alongside new production. In these cases, file provenance metadata — and therefore the correct profile — can be ambiguous.

  • The confidence score (High / Medium / Low) and runner-up profile shown per file help QA staff identify ambiguous cases before a batch run.
  • Medium or Low confidence files are candidates for manual profile override review before final conversion.
  • The Validation Issue Explainer can be used to interpret detection-related notices — for example, constructs present in one S1000D issue but deprecated in another.

Workflow pattern with Reforge

Most teams validate incoming CGM, review the exceptions, and then convert the approved files. The SVG output goes downstream to publishing or to interactive delivery.

  • Run profile-aware conversion settings per program standard.
  • Validate source data before final export.
  • Export consistent SVG output for web and documentation delivery.
  • Keep processing local to protect controlled technical data.

For teams running nightly release batches, the reforge watch and reforge convert CLI commands automate this pattern end-to-end. See the Batch and CLI guide for details.

Need procurement details? Use the pricing section for plan comparison and trial access for hands-on evaluation.

Validate your program-specific file set before rollout

Use representative S1000D/WebCGM graphics from your current release cycle to confirm profile handling and QA workflow compatibility.

Start trial evaluation Review plans

Need throughput or compliance guidance next?

Pair this workflow review with automation and validation pages if your team is planning production rollout or release-window controls.

Batch + CLI guide Validation guide