1 / 12

S1000D Converter

S1000D Converter. Mike Day Rolls-Royce Defence Aerospace Mike.Day@Rolls-Royce.com. Background. Action at Starnberg Meeting to produce a conversion program to convert 1.9 Data Modules to Issue 002 standard.

issac
Download Presentation

S1000D Converter

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. S1000D Converter Mike Day Rolls-Royce Defence Aerospace Mike.Day@Rolls-Royce.com

  2. Background • Action at Starnberg Meeting to produce a conversion program to convert 1.9 Data Modules to Issue 002 standard. • Program is now in the test stage. In order to test it, we are looking for volunteers in S1000D community… • A specification created documenting mappings required.

  3. The Solution - Overview SGML Data Module Data Module S1000D Converter XML Data Module

  4. The Solution - For Anoraks XSL Stylesheet Auto-detect incoming DTD / Schema standard SGML Data Module Global Changes Data Module S1000D Converter XML Data Module Tag Options Project Attribute Map XML Character Map Public Identifier Catalog

  5. The Solution • A multi-directional converter has been produced that is capable of converting 1.8, 1.8.1 and 1.9 data modules into Issue 002. Thus, we can convert 1.8 into 2.0 or 2.0 into 1.8! • Although backwards conversion is not always possible without data loss, this will prove a useful feature. Why?...

  6. Engines go into many “darts”

  7. Why Backwards Conversion? • Take the example of the RTM322 engine. • This powers Merlin (1.6 DTD), Support (1.6.1 DTD), Apache (1.8 DTD) and NH90 (1.8.1). In order to share common data, we have to convert backwards and forwards.

  8. Additional Features • Conversion to SGML / XML at all standards • Ability to apply global mark-up changes such as • Issue number • Inwork attribute • QA status • Issue Date • Reason for update • Others? • Able to specify Issue 2 Projectised Attributes I.a.w. Swedish CPF • Conversion to Upper/Lower/Sentence case Element names and attribute names

  9. Limitations • Data loss on backwards conversion • Data Modules MUST be normalised before conversion (end tag for every non-empty start tag) • Data Modules MUST parse against the DTD

  10. Problems Found in Converting to 2.0 Converted mark-up no longer parses as warning is NOT allowed after a <para> <step1> <para> Some text </para> <specpara> <warning> <para>WARNING TEXT</para> </warning> <para> Text warning applies to</para> </specpara> </step1> <step1> <para> Some text </para> <warning> <para>WARNING TEXT</para> </warning> <para> Text warning applies to</para> </step1> As specpara is no longer in DTD 2.0, you can no longer tie a WCN to the para it relates

  11. Continuing Work • Test in AECMA / AIA Community • Fix bugs and implement improvements from test • Implement any DTD / Schema changes • Release • Improve “backwards” conversions

  12. Let’s watch some paint dry!

More Related