First, congratulations on the - as it looks so far - quite smooth release. > - I'm relatively happy with the workflow for accepting style patches. > Having Travic CI check each pull request, and having the ability to > run the same tests locally > (https://github.com/citation-style-language/styles/wiki/Test-Environment) > has made it much easier to keep errors out. We now also rely much more > on the style authors themselves to fix style errors. Big kudos to > Sylvester for setting up the tests, and thanks to Sebastian and > Charles for helping out with adding styles! I just hope CSL doesn't > become too popular :) (the current workload is still okay).
agreed - I'm a little concerned what will happen when the visual editor goes live for real. While it writes pretty clean code, it doesn't validate and it does some odd things still. > - I don't think we need to rush with trying to incorporate Frank's MLZ > extensions to CSL into official CSL. MLZ will be a nice testing > ground, and I rather wait a little to see how the MLZ styles perform > in practice. agreed again - a lot of MLZ functionality already works with CSL once the respective fields are added to Zotero et al. > (...) > * field assignments (which item type should, or shouldn't, have > which fields). Aurimas prepared a map for Zotero: > http://aurimasv.github.com/z2csl/typeMap.xml . It would be great if we > could standardize the fields exposed to the CSL processors among the > different reference managers (on a per item type basis). My hope is > that we can clean up Zotero's metadata model in the coming year > (tickets as compiled by the Zotero user community can be found at > https://github.com/ajlyon/zotero-bits/issues ), and offer the result > as a guideline for other reference managers. This is, imho, really the top priority - with different fields/item we'll get inconsistent outputs - cf. e.g. publishers for journals. Happy to help work on this. (...) > - There are still quite a few open CSL tickets ( > https://github.com/citation-style-language/schema/issues ). Some have > solutions that require a backwards incompatible release (i.e. CSL 1.1) > and style upgrades, while other tickets have stalled due to the > absence of good ideas or due to disagreement. I don't expect too much > progress here, unless people step in and reboot the discussions. I think some of them are pretty important. My top two are: https://github.com/citation-style-language/schema/issues/36 https://github.com/citation-style-language/schema/issues/94 The first one is pretty major, but I'd really like to see 94 in one of the smaller releases. -------- Sebastian Karcher Ph.D. Candidate Department of Political Science Northwestern University ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
