Mapping ODD processing
Jump to navigation
Jump to search
This page is intended to help us map out and document the various processing steps that are applied to ODD files, both in the current Stylesheets and in a future alternative ODD processor.
| NAME | INPUT | OUTPUT FORM | PROCESSES INVOLVED | PREREQS | XSLT FILES | COMMENTS |
|---|---|---|---|---|---|---|
| Generate P5 | P5 chapters and specs | [p5].xml (TEI) | Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. | There must be a repodate.xml file containing an XML representation of the git repo state. | [TEI]/Utilities/expand.xsl | *Spec elements occur in specGrp and in div. |
| Generate [P5] Subset | p5.xml (generated above) | p5subset.xml (TEI); p5subsetDoctored.xml (TEI) | Create a special cut-down version of P5 which has only divisions and their headers along with all the specs. | Complete guidelines | Utilities/subset.xsl; Utilities/dtdMagic.xsl (for Doctored) | Why are all the div/head elements included? Why is a schemaSpec not created? Is it the case that schemaSpec always and only represents a customization of an existing source, which must eventually chain back to p5subset? If so, ODD is not a generic language; it depends on P5. This also generates the ugly p5subsetDoctored.xml, which is a hack for DTD production. |
| Merge ODD customization with P5 source (SR calls this oddexpand) | ODD customization; p5subset | file.processedodd | D | E | F | G |
| A | B | C | D | E | F | G |
| A | B | C | D | E | F | G |
| A | B | C | D | E | F | G |
| A | B | C | D | E | F | G |
| A | B | C | D | E | F | G |
