Skip to content

Changes

Page history
Touchups and extensions authored by Wendell Piez's avatar Wendell Piez
Show whitespace changes
Inline Side-by-side
home.md
View page @ 636777ef
...@@ -58,11 +58,9 @@ Since many of the particular requirements for data capture and representation ca ...@@ -58,11 +58,9 @@ Since many of the particular requirements for data capture and representation ca
For the time being this will involve old-fashioned comparisons between Word source data (viewed both as a printed page, and as an artifact in Word) and HTML produced by the XSLT and as exposed in / interfaced with (tools in) PubSweet, and reporting lapses, discrepancies, and opportunities for improvement. (First question is always: Did we get it all?) For the time being this will involve old-fashioned comparisons between Word source data (viewed both as a printed page, and as an artifact in Word) and HTML produced by the XSLT and as exposed in / interfaced with (tools in) PubSweet, and reporting lapses, discrepancies, and opportunities for improvement. (First question is always: Did we get it all?)
As the system matures it should require less time from an XSLT developer to process a single (set of) Word documents for PubSweet. A sustainable system may permit configuration or tweaks to performed routinely by team members with XSLT (or other) skills; but it should not require deep XSLT knowledge to keep it running or extend to new cases. As the system matures it should require less time from an XSLT developer to process a single (set of) Word documents for PubSweet. A sustainable system may permit configuration or tweaks to performed routinely by team members with XSLT (or other) skills; but it should not require deep knowledge (of XSLT) to keep it running or extend to new cases. Ideally, it would be well enough documented that new users could teach themselves. (Something to aim for.)
Since there is much to be done to get to that point, this means being vigilant for opportunities both for improvement and for skills development. Keep in mind that another advantage of a pipelining architecture is that XSLT can be combined into pipelines with transformations implemented in other languages. It is taken as an assumption from the outset that this tool will only succeed if it works well with other tools, most especially other tools that people actually use.
Keep in mind that another advantage of a pipelining architecture is that XSLT can be combined into pipelines with transformations implemented in other languages.
## Big Questions ## Big Questions
...@@ -72,6 +70,6 @@ While the transformation is lossless as respects "main document content" (that i ...@@ -72,6 +70,6 @@ While the transformation is lossless as respects "main document content" (that i
The solution is vigilance, contextual awareness (both processes and contingencies) and testing. In addition to some means of representing and aligning specifications for the different XSLTs (such as inline documentation), we need to have robust mechanisms for detecting problems in data extraction _especially lost data_; for ameliorating such problems in the instance (sometimes they may not be fatal errors); and for maintaining and improving the XSLTs so they don't happen. The solution is vigilance, contextual awareness (both processes and contingencies) and testing. In addition to some means of representing and aligning specifications for the different XSLTs (such as inline documentation), we need to have robust mechanisms for detecting problems in data extraction _especially lost data_; for ameliorating such problems in the instance (sometimes they may not be fatal errors); and for maintaining and improving the XSLTs so they don't happen.
For now this is happening under [Issues](../../DOCX-xslt/issues) on this-here wiki. For now this is happening under [Issues](../../XSweet/issues) on this-here wiki.
Expected problem areas? Of course, citations and references, math, cross-references. Expected problem areas? Of course, citations and references, math, cross-references.