in the Publication Workflow
- Are we all on the same page? [slide 1]
- XML and XSLT [slide 2]
- XSLT for quality checking in the publication workflow [slide 3]
- The opportunity and the problem [slide 4]
- The territory [slide 5]
- Strengths (and weaknesses) of XSLT for QA [slide 6]
- XSLT was designed for down-conversion [slide 7]
- It's hard to make predictions, especially about the future [slide 8]
- Today's examples [slide 9]
- Three architectures [slide 10]
- Single documents [slide 11]
- False-color proof [slide 12]
- An Extreme Markup Languages paper in false-color
proof [slide 13]
- What's happening here [slide 14]
- Filters and reports for content checking [slide 15]
- Example: A generic tag usage profile [slide 16]
- Details about the generic tagging profile [slide 17]
- Example: Identify possible URIs (untagged) [slide 18]
- Results of this example [slide 19]
- Details about the URI-finding stylesheet [slide 20]
- Some other possibilities [slide 21]
-
“Soft validation” filters and reports [slide 22]
- Examples of soft validation [slide 23]
- Example: Locate all codeblocks with long lines [slide 24]
- Details about the line-measuring stylesheet [slide 25]
- Where else can we go with this? [slide 26]
- An alternative processing paradigm [slide 27]
- Documents in combination [slide 28]
- Example: pesky characters [slide 29]
- How the character-analysis works [slide 30]
- Result of running the character analysis [slide 31]
- Document differencing [slide 32]
- Sets of documents [slide 33]
- The quick-n-dirty XSLT approach [slide 34]
- A filter for unfinished bios [slide 35]
- Keys to Success [slide 36]
- References [slide 37]
- Examples for download [slide 38]
- Colophon [slide 39]