You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have analysed the JATS schema and found a lot of definitions, which allow too many different ways for tagging the same content.
We want to restrict the original XSD incrementally, getting to a schema with the same expressiveness, but less implementation paths, ultimately allowing for a better Editor UI.
These changes will lead to a schema which is still valid JATS.
Finally we want to propose some real additions, which allow to eliminate deficiencies in the current JATS specification, that force/invite users to use certain workarounds degrading the specificity and cleanness of the schema.
These changes will lead to an incompatibility, which will be bridged adopting the mentioned workarounds.
Example:
To be able to have other block-level elements in footnotes (such as a list), you must wrap the content into a <p> element. However, this degrades the quality of <p>, as itself becomes a container of paragraph-level elements.
We have analysed the JATS schema and found a lot of definitions, which allow too many different ways for tagging the same content.
We want to restrict the original XSD incrementally, getting to a schema with the same expressiveness, but less implementation paths, ultimately allowing for a better Editor UI.
These changes will lead to a schema which is still valid JATS.
Finally we want to propose some real additions, which allow to eliminate deficiencies in the current JATS specification, that force/invite users to use certain workarounds degrading the specificity and cleanness of the schema.
These changes will lead to an incompatibility, which will be bridged adopting the mentioned workarounds.
Example:
To be able to have other block-level elements in footnotes (such as a list), you must wrap the content into a
<p>
element. However, this degrades the quality of<p>
, as itself becomes a container of paragraph-level elements.<element-citation>
should not have mixed contentThe text was updated successfully, but these errors were encountered: