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
As we see the arrival of version 1.0 (congratulations!), we are imagining a perfect future where we can import any HTML document and transform it into some pre-JATS... But "any HTML document" is perhaps ambitious... There are some plan to operate Substance with an ecosystem of interoperable parts, to import universal standards like "dirty HTML"?
There are a methodology "from HTML to JATS" used by Substance community?
In nowadays there are HTML5 semantic tags (article, section, figure, etc.) that can be easylly mapped to JATS, and there are some standard-RDFa as http://schema.org/Article (or ScholarlyArticle) to add more information that will easy to map to JATS.
So, is not necessary a rigid workflow in authoring process... Will be natural to start the job with HTML and, only later in the authoring process, after some magic "import from HTML", edit with Texture. There are a group working this scenario?
The text was updated successfully, but these errors were encountered:
As we see the arrival of version 1.0 (congratulations!), we are imagining a perfect future where we can import any HTML document and transform it into some pre-JATS... But "any HTML document" is perhaps ambitious... There are some plan to operate Substance with an ecosystem of interoperable parts, to import universal standards like "dirty HTML"?
Example, operate with https://github.com/punkave/sanitize-html (and some Substance's recommendations) to feed with "reasonable HTML" instead "dirty HTML".
There are a methodology "from HTML to JATS" used by Substance community?
In nowadays there are HTML5 semantic tags (
article
,section
,figure
, etc.) that can be easylly mapped to JATS, and there are some standard-RDFa as http://schema.org/Article (or ScholarlyArticle) to add more information that will easy to map to JATS.So, is not necessary a rigid workflow in authoring process... Will be natural to start the job with HTML and, only later in the authoring process, after some magic "import from HTML", edit with Texture. There are a group working this scenario?
The text was updated successfully, but these errors were encountered: