Technical insight · 2026-09-15

The market is buying publication delivery.

For publications managers and engineering leads, the useful starting point is a publication package with a named acceptance owner. Scope a representative sample to receive an agreed mapping, assessed outputs and evidence that a revision can pass through the delivery process before production begins.

A publication lead may have source files and a working authoring tool but still lack an accepted delivery. The practical job is to connect the source to the recipient’s rules, resolve findings and produce an output that can be maintained. We scope that job around a real package rather than a catalog of software features.

The evidence supports defined publication work

Time Technology’s business report describes named export-publication work and several Korean-to-English manual scopes. This supports a concrete discussion about export acceptance and English production. It is a supplier disclosure, not an open solicitation or proof that every export program uses the same publication rules. Time Technology report

A historical Japan Maritime Self-Defense Force eligibility notice links publication work to Mogami-class knowledge and S1000D expertise or close collaboration. It also calls for EAGLE VISION knowledge and web publication capability. The receiving environment is therefore part of that specific delivery scope, not an incidental tool choice. JMSDF notice

These records support specific delivery jobs. They do not establish market size, current openings or demand for Dakota capacity. An export destination alone is also not evidence of a required publication language.

The buyer owns an acceptance or change problem

For qualification, we separate the publication obligation from the tool discussion. The useful buyer conversation starts with who owns the package and who can accept it.

  • Publications managers can bring a rejected supplier package or a backlog awaiting assessment.
  • Engineering and PLM leads can bring a released change that has not reached the publication output.
  • Supplier delivery leads can bring a conversion scope with unresolved recipient rules.

Each case calls for a different sample. A conversion sample tests interpretation and mapping. A change sample tests ownership and release handling. A rejected package tests whether findings can be reproduced and closed.

The sample starts with the receiving baseline

Our proposed intake brings the source and acceptance evidence together before estimating correction work. We ask for:

  • The controlling contract and publication baseline, including the specified S1000D issue.
  • Program business rules and any available recipient check results.
  • Representative source content with its referenced illustrations.
  • The expected output and access to the receiving environment where permitted.
  • A released engineering change and the person authorized to resolve exceptions.

Missing inputs become scope decisions, not silent assumptions. If the recipient cannot supply an acceptance example, we propose a review checkpoint before bulk conversion. That keeps an unresolved interpretation from being copied across the source collection.

Acceptance and migration need separate checks

We treat schema validation as evidence about structure, not as the whole acceptance decision. The proposed assessment records each check, its controlling source and its result. Findings distinguish content corrections from questions that need a program decision.

For engineering reuse, the sample follows information from a released source through the publication output. We identify what is reused and what remains authored, then test how each responds to a change. This avoids treating a successful import as proof of a maintained handoff.

For migration, we assess the authoring framework separately from composition. PTC documents restrictions on exported Styler XSL-FO; an export is not sufficient evidence that another formatting engine will reproduce the output. PTC export documentation

Oxygen documents issue-specific S1000D framework support and Data Module PDF and HTML output. We assess that documented coverage against the requested baseline rather than assume universal support or claim that the framework cannot publish. Oxygen S1000D framework

The handoff includes decisions and evidence

We propose a scoped sample engagement with tangible review material:

  • A requirements-to-check matrix with unresolved decisions visible.
  • An agreed source-to-target mapping and an assessed representative package.
  • A findings log with correction owners and exception decisions.
  • Published sample outputs with instructions for reproducing the build.
  • A revision record that connects the source change to the delivered result.

Where DITA web publishing is in scope, define validated .ditamap and .dita assets plus publish-ready HTML as separate deliverables. Do not treat those assets as substitutes for a contracted S1000D exchange package.

A revised sample is the production gate

Our recommended acceptance test includes both the initial sample and a revised sample. Apply the agreed change, rerun the checks and inspect the resulting output. Record which steps were repeatable and which depended on manual intervention.

A clean first build can hide an unworkable change handoff. Reviewing the revision before scaling conversion exposes that risk while the correction scope is still bounded. Production planning can then use the demonstrated process rather than an assumed throughput.

Partner status supports qualification but does not prove demand

Dakota is listed among Oxygen XML consulting partners under training and consulting. That is evidence of a published relationship, not evidence of a customer project or delivery result. Oxygen consulting partners

For partner-led work, we qualify the workshare and acceptance owner before proposing production. A capabilities conversation without an available sample remains an early discussion.

Bring a real source package, the required output and the acceptance owner to a scoping workshop.

Sources

Start with a real sample

Bring one representative procedure or data module. We scope the work against your contracted S1000D issue and business rules, then quote production.

Book a workshopContact