An Arbortext migration can change how authors work, how pages are composed or both. The decision is not simply which editor replaces the current application. It is which content behavior and publishing behavior the team intends to preserve. We scope those decisions separately and test them against source content and accepted output.
The work starts with the people who own acceptance
This service is for publication managers responsible for delivery, architects maintaining Arbortext customizations and engineering systems leads managing content handoffs. It also serves operations teams that need a maintainable publishing process rather than a replacement application alone.
We identify who accepts authoring behavior and who accepts output. Those owners may differ. An editor that supports the selected writing tasks does not by itself settle whether a publication meets its agreed page-layout criteria.
Authoring and composition are separate decisions
We inventory the source environment, agree a mapping to the target architecture and implement a representative sample. The scope can retain existing authoring while changing composition, or retain composition while changing authoring. Production migration is a separate scope decision after sample acceptance.
Oxygen documents an S1000D framework with schema validation and data-module PDF and HTML publishing. We assess that documented coverage against the program's selected issue and authoring tasks rather than treating framework availability as proof of full publication or CSDB coverage. Oxygen S1000D framework
Antenna House Formatter documents PDF composition using XSL-FO or CSS. That provides a target composition option; it does not establish that existing Arbortext publishing assets will transfer unchanged. Antenna House Formatter
The sample includes difficult content and its dependencies
We start with a bounded publication family and content that exposes difficult behavior. A clean introductory chapter alone is a poor basis for accepting table handling or page sequencing. The input package includes:
- XML or SGML source with schemas or DTDs, plus catalogs and entity definitions.
- Representative graphics and the references that connect them to the source.
- Arbortext frameworks, FOSI or Styler assets and local extensions.
- Scripts and transforms, with the publishing configuration used to produce the reference output.
- Accepted PDFs showing difficult tables, cross-references and page sequences.
- Font dependencies and output constraints, with named acceptance owners.
We also ask for the program's selected S1000D issue and business rules as assessment inputs. Missing dependencies become recorded scope gaps, not silent assumptions in the target implementation.
Deliverables follow the commissioned workstream
The inventory distinguishes assets we propose to reuse from behavior we propose to adapt or rebuild. Each decision is tied to source evidence and an acceptance check. The delivery package then follows the agreed scope:
- An asset and behavior inventory with mapping decisions and unresolved dependencies.
- A target authoring framework and transformation pipeline when authoring migration is commissioned.
- Implemented composition stylesheets and a reference-PDF comparison report when composition migration is commissioned.
- A representative production run with documented exceptions and acceptance results.
- Cutover and rollback plans, supported by maintenance notes and training material.
We keep production conversion and handover explicit in the scope. Accepting a sample does not silently authorize conversion of the full content collection.
A revision tests more than a static sample
Before stylesheet implementation, we agree which visual differences are acceptable and which affect delivery. We keep the source environment available through sample acceptance so reviewers can distinguish an existing source defect from a migration defect.
Our proposed acceptance checks cover the selected workstream:
- Check content and references against the agreed schema and program-rule test set.
- Have authors complete the selected editing and review tasks in the target framework.
- Compare page structure and numbering, then inspect tables, graphics and links.
- Record material differences with an owner and a disposition.
- Repeat the publishing run with documented fonts and settings.
We then apply a representative source revision and repeat the relevant checks. This tests whether the mapping and publishing process survive change, not just whether the initial sample looks right. Acceptance records distinguish automated checks from editorial review and unresolved exceptions.
Exported stylesheets are evidence to assess
PTC documents that XSL-FO export requires a Styler stylesheet configured for that engine. It also warns that exported XSL may not work in other XSL-FO applications and does not support that use. We therefore scope assessment and implementation rather than promise automatic stylesheet portability. PTC stylesheet export guidance
Dakota is listed among Oxygen XML consulting partners under training and consulting. That listing supports our role in assessing authoring work; it is not evidence that a particular Arbortext customization will migrate without rebuilding. Oxygen consulting partners
Bring a real source package, its publishing assets and an accepted reference PDF to a migration workshop with the person who accepts delivery.
Sources
- S1000D Framework add-on — Syncro Soft / Oxygen, date not stated.
- Antenna House Formatter — Antenna House, date not stated.
- Exporting Stylesheets — PTC, date not stated.
- Oxygen XML partners — Syncro Soft / Oxygen, date not stated.