Michael Aufreiter

Strange. I remember seeing that error a while ago, but that was related to our dev environment. What node version are you using?

You can try installing the cutting edge build using: ``` $ sudo npm install -g [email protected] ```

I guess we messed something up with our alpha release.. assuming that providing 0.0.0 as version number.. npm install (without version) still uses the latest available version.. but it seems...

Hi @minrk! This is something we haven't decided on yet. It's being discussed here: https://docs.google.com/document/d/1-aF637_bbdWtWS11BaO4pEzmAOUozQkt1rum4w7m0mU/edit#heading=h.qxc3j9ll1wn8 One idea was to only provide a runtime identifier and a version. And then there...

Hey! We don't have a generated dtd yet (will come once the spec has stabilised). However, we have our schemas specified in RelaxNG. https://github.com/substance/substance/blob/develop/dar/Manifest.rng https://github.com/substance/texture/blob/master/src/article/DarArticle.rng https://github.com/stencila/stencila/blob/develop/src/sheet/SheetSchema.rng

Currently our schema validator can not enforce attribute values. Hope we find time to add that soon. However you can find a formal, more readable spec here: https://github.com/substance/dar/blob/master/DarArticle.md#aff

The Jupyter Notebook format does not model some contents which are important for an article to be considered a full-fledged manuscript (e.g. reference list, abstract with translations, journal specific metadata...

Also see this recent demo of such a reproducible publication in action: http://builds.stenci.la/stencila/reproducible-publication-example-2018-04-16-dcf17f9/example.html?archive=repro-pub (note this is still a work in progress, and Python, R, etc. contexts are not exposed in...

Hi @jobdiogenes the Dar format actually IS valid JATS. We just enforce a stricter tagging schema. Once we have all use-cased covered SciELO, Erudit, eLife and others will be using...

not directly... what we have is highlighting the text fragments of a multi-annotation, which must exist as a node in the doc. however what would be also nice to have...