Feel free to create a pull request. In this case, I think there will be little resistance to aligning the specification with the schema on this point (and the schema usually takes precedence over the specification anyway in case of discrepancies).
Your pull request might sit for a while until I have had some time to document and implement our plans for a better development process for CSL. It's rather trivial to accept the change, but I want to make sure that the stakeholders are at least aware of the change before I merge it (will inform the mailing list) and that it ends up in the changelog for the next release. I'm focused on moving the CSL website from WordPress to GitHub pages right now, but that should be done in the next few weeks. Rintze On Fri, Nov 3, 2017 at 11:57 AM, toreilly <ia...@hotmail.com> wrote: > I created a patch to the GitHub repo to correct the error in the > documentation. > > https://github.com/citation-style-language/documentation/compare/1.0.1...iamio87:patch-1 > > Before I send a pull request, I was wondering if there is a voting or review > process for accepting changes to the documentation. > > > > -- > Sent from: http://xbiblio-devel.2463403.n2.nabble.com/ > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > xbiblio-devel mailing list > xbiblio-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
