... | ... | @@ -65,7 +65,7 @@ This validation should be super-simple for purposes of process intelligibility a |
|
|
|
|
|
4. Co-occurrence and other dependency constraints, for example 'If there is an Acknowledgements section there may be no Funding section'.
|
|
|
|
|
|
For now, HTMLcognizer will enforce only the first of these rule sets. The specific types and their criteria (recognized values) should be configurable. We can consider more complex requirements for validation of type assignments as they emerge.
|
|
|
For now, HTMLevator will enforce only the first of these rule sets. The specific types and their criteria (recognized values) should be configurable. We can consider more complex requirements for validation of type assignments as they emerge.
|
|
|
|
|
|
When a section title is detected, but its value is not recognized as that of a known section title, we make the section but also inject a warning (into the main output) to go with it.
|
|
|
|
... | ... | @@ -97,7 +97,7 @@ If this is considered to be a problem or potential problem we could address it b |
|
|
|
|
|
An input document has no paragraphs marked with style "Section_Title".
|
|
|
|
|
|
Its output through the HTMLcognizer pipeline represents the input without modification.
|
|
|
Its output through the HTMLevator pipeline represents the input without modification.
|
|
|
|
|
|
#### 2
|
|
|
|
... | ... | @@ -107,7 +107,7 @@ In the result, a `<section>` is created with an assigned class of `UNKNOWN` and |
|
|
|
|
|
```
|
|
|
<section class="UNKNOWN">
|
|
|
<p style="htmlcog_alert">[[[ HTMLCognizer alert: "Conclsions" is not recognized as a section title. ]]]</p>
|
|
|
<p style="htmlcog_alert">[[[ HTMLevator alert: "Conclsions" is not recognized as a section title. ]]]</p>
|
|
|
<p style="Section_Title">Conclsions</p>
|
|
|
<p>We conclude there is less than an 0.001% probability that the moon is made of green cheese.<p>
|
|
|
...
|
... | ... | @@ -118,13 +118,13 @@ In the result, a `<section>` is created with an assigned class of `UNKNOWN` and |
|
|
|
|
|
If XSweet header promotion is applied, it occurs separately (either before or after) from the sectioning process. Sectioning is based *only* on the assigned style name, not on its features or contents.
|
|
|
|
|
|
The (string) content of the Section_Title line, only (and nothing regarding its formatting) is evaluated to determine whether the section is recognized as a defined type. Regex matching or other string testing is okay. For example, a rule that "any title starting with 'Conclusion' and not longer than 40 characters indicates a `conclusion` section" would be straightforward to implement. HTMLcognizer should not, however, normalize "deviant" forms or variants even if it is programmed to recognize them.
|
|
|
The (string) content of the Section_Title line, only (and nothing regarding its formatting) is evaluated to determine whether the section is recognized as a defined type. Regex matching or other string testing is okay. For example, a rule that "any title starting with 'Conclusion' and not longer than 40 characters indicates a `conclusion` section" would be straightforward to implement. HTMLevator should not, however, normalize "deviant" forms or variants even if it is programmed to recognize them.
|
|
|
|
|
|
HTMLcognizer should not be confused when footnote references occur inside titles. They must not throw off any string comparison. Other contents, however, are all construed as literals; no formatting (either paragraph-level or inline) is considered.
|
|
|
HTMLevator should not be confused when footnote references occur inside titles. They must not throw off any string comparison. Other contents, however, are all construed as literals; no formatting (either paragraph-level or inline) is considered.
|
|
|
|
|
|
HTMLcognizer does not intervene to "correct" anything. If conversion does not produce acceptable results, it is up to the user whether to modify the Word document and run it through XSweet+HTMLcognizer again, or whether to correct the file in the HTML.
|
|
|
HTMLevator does not intervene to "correct" anything. If conversion does not produce acceptable results, it is up to the user whether to modify the Word document and run it through XSweet+HTMLevator again, or whether to correct the file in the HTML.
|
|
|
|
|
|
Everything *added* by HTMLcognizer must be flagged somehow so it can be seen downstream where it comes from.
|
|
|
Everything *added* by HTMLevator must be flagged somehow so it can be seen downstream where it comes from.
|
|
|
|
|
|
We don't do nesting. For example, within the "Conclusions" section everything will be flat, there are no subsections. Subsectioning must be accomplished by a different (probably subsequent) process.
|
|
|
|
... | ... | |