On Thu, Apr 28, 2011 at 10:26 PM, Bruce D'Arcus <[email protected]> wrote: > On Wed, Apr 27, 2011 at 9:03 PM, Frank Bennett <[email protected]> wrote: >> On Thu, Apr 28, 2011 at 3:36 AM, Bruce D'Arcus <[email protected]> wrote: >>> All - we've got a little bug in the schema, outlined here: >>> >>> <http://forums.zotero.org/discussion/17742/locators-zotero-216/> >>> >>> Basically, we need to change the 'sub verbo' locator value to 'sub-verso'. >>> >>> Any objections to doing that ASAP in a minor point release? >>> >>> I need a +1 or -1 one from all implementors please. >> >> ~~1 >> >> I don't think there's a need to rush this. A workaround was used in >> 2.0.9 (testing for all locator labels that are not "sub verbo"). The >> workaround didn't work in citeproc-js because the locator attribute >> was not being handled correctly; with a fix in place, code from 2.0.9 >> will carry over smoothly. >> >> A change in the term name should be tested in applications before >> release. There will be legacy documents around that set "sub verbo" as >> the locator label key, so processors will need to remap that to >> "sub-verbo" on the fly in any case, to avoid breaking documents, and >> we'll want to be sure the special handling needed works correctly >> before the locale files change underneath the processor. >> >> So I think it's desirable to move "sub verbo" to "sub-verbo", but I >> think the change can wait a bit for testing and reflection. > > Let me put this is the most straightforward terms possible: > > Any style that currently uses "sub verbo" as a condition is completely > invalid. > > So effectively, for implementations, it's as if the term doesn't exist > for purposes of conditional testing (e.g. you shouldn't be coding > citeproc-js to accept "sub verbo" as a condition in my view because > you're going out of your way to accept a broken style).
I explained why this is necessary, in order into avoid breaking documents during the migration to the repaired version of the schema. It's the processor's job to serve citations against a valid schema, and citeproc-js will do that, both before and after the schema is fixed. > > Therefore, I do think there's some urgency in fixing this; in say the > next couple of weeks. It's an infrequently enough used term that a > simple search-and-replace on the following repos should suffice: > > - docs > - schema > - locales > - styles > > That, plus rolling in the spec changes in author grouping should be a > reasonable 1.0.1 release. Great, will look forward to it. > > Bruce > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
