| Thank you very much for your comments! A few notes from the authors: Texture's first goal is its use at publishers, during their review and QC processes. Word or InDesign submissions are converted to JATS using the converter from Open Journal Systems (OJS) and from then on are treated with Texture until publication. Once journals have adopted JATS in their editing workflow, I'm sure they are willing to switch allowing submissions in JATS. Then authors have an incentive to write their papers in Texture from the beginning. Texture is hackable and can be extended via packages implemented in JS (think Github Atom editor). Each JATS node type is implemented as a package already, with still many of them missing (math, figgroups, ...). A package implementation looks like this: https://github.com/substance/texture/tree/develop/lib/taggin... We understand that publishers have different needs and allow them to configure and customize the editor to any degree. We also want to open up the editor to community contributions, e.g. one could implement an R-backed visualization content type (see https://stenci.la/), that could live right in the editor. This would require introducing custom tags in the JATS serialization format, which we think is valid, if you are aware of the implications. Texture is at an Alpha state, but a number of organisations committed to funding it's development, so we should see stable versions in the coming months. You are invited to join the Substance Consortium, which drives the development of Texture. http://substance.io/consortium/ See the current product brief, until we have published a public roadmap. https://docs.google.com/document/d/1v01mfeJw0IHgN7EIKE6JtEkE... |