Difference between revisions of "Mapping ODD processing"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS | ! NAME || INPUT || OUTPUT FORM || PROCESSES INVOLVED || PREREQS || XSLT FILES || COMMENTS | ||
|- | |- | ||
| − | | Generate P5 || Combine all chapter and spec files into a single document; processing instructions such as the generation of a table for chapter ST are handled. | + | | 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 || |
|- | |- | ||
| Generate [P5] Subset || Cut-down version of complete P5 guidelines-en.xml || [p5subset].xml (TEI) || Create a special version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || subset.xsl || 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. | | Generate [P5] Subset || Cut-down version of complete P5 guidelines-en.xml || [p5subset].xml (TEI) || Create a special version of P5 which has only divisions and their headers along with all the specs. || Complete guidelines || subset.xsl || 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. | ||
Revision as of 17:45, 4 November 2016
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 | |
| Generate [P5] Subset | Cut-down version of complete P5 guidelines-en.xml | [p5subset].xml (TEI) | Create a special version of P5 which has only divisions and their headers along with all the specs. | Complete guidelines | subset.xsl | 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. |
| 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 |
| A | B | C | D | E | F | G |
