Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans to an import-HTML module? #1213

Open
ppKrauss opened this issue Jul 29, 2018 · 0 comments
Open

Plans to an import-HTML module? #1213

ppKrauss opened this issue Jul 29, 2018 · 0 comments

Comments

@ppKrauss
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant