Closed wendellpiez closed 1 year ago
Hm - is propagating table//@style
into the output a potential security issue? We could provide the feature but we should perhaps also expose it in a diagnostic XSLT - since tables mean semantics, and table styles are a good indicator of semantics latent in the data.
To add to above - links in landing page for viewer should probably be marked 'external' when that applies.
So, three items so far:
table//@style
- current and desired functionalityNew feature: fallback handling of elements not identifiably STS by 'tagging' with a different color (not pink).
For example, when consuming JATS, elements that are in JATS not STS should not appear as STS. But since JATS elements have the same semantics as their STS counterparts, when they match, they match, and goodness results.
This also points the way to a viewer that accepts either tagging (as long as in no namespace).
Note that caption
is not being matched and processed, or always matched and processed.
So add that to the work item list. An example is NIST SP800-53 in STS XML.
caption
and outbound linking issues were captured in PR #42 so captions/tables/figures lists are the only to-do remaining here.
Closing this issue since the requirement is now addressed by STS Checker.
The STS Viewer does not currently create lists of tables, figures, equations etc., but it could.