Rintze M. Zelle, PhD

Yeah, good call. For shortTitle, this is a duplicate of https://github.com/citation-style-language/schema/issues/113. Regarding the property value conventions, the latter properties should probably be relaxed to accept both "string" and "number".

Yeah, since "shortTitle" is the odd one out, I doubt we'll ever switch everything to camelcase, although I see the benefit from a programming point of view.

Uhm, I'm not a 100% sure. I created the schema based on the JSON input snippets in the citeproc-js test suite, and this schema is therefore more descriptive than normative....

> What are the prospects for migrating all citeproc-js-specific engines to use EDTF as input format? Is that a rhetorical question? @nickbart1980, maybe we should start with checking what needs...

@phillipsyoav, @roypeled1, could either of you review my comments above? I prepared a new pull request from @phillipsyoav submission (https://github.com/citation-style-language/locales/pull/146), but there are a few outstanding issues such as missing...

Fine with me. The only question I have is whether this would complicate automated style editing.

@adam3smith, do you see (a lot of) value in this, seeing as you're our most seasoned style editor?

We currently claim copyright in 3 files: https://github.com/citation-style-language/schema/search?utf8=%E2%9C%93&q=copyright&type= I think we can add an MIT license to the entire repo using the standard GitHub template. Will prep a PR.

(leaving this open since we'll probably want to backport the MIT license to at least CSL 1.0.1)

(there are e.g. a large number of reports that the editor doesn't work properly in Chrome: http://feedback.mendeley.com/forums/182109-csl-editor/suggestions/11290860-cannot-use-visual-editor-in-chrome)