On Thu, Apr 28, 2011 at 2:08 PM, Rintze Zelle <[email protected]> wrote: > Can we go back and discuss whether it's possible to: "keep a 'normal' "sub > verbo" term and create a "sub-verbo" locator term", along with "CSL > processors would have to link "sub-verbo" to "sub verbo"" (see my earlier > post). > > This way any valid CSL 1.0 style will remain valid (because the locator="sub > verbo" wouldn't pass validation anyway). With only added functionality, this > wouldn't be a backwards-incompatible change. I will be a little messy in the > schema, but we can clean that up in CSL 1.1.
This is an option. But I suspect what on first blush looks like the easier approach may actually create more headaches. What would be the problem if we simply did as I suggest: a quick search-and-replace on all github csl repos? So long as implementations update their locales files, things would continue to "just work" without interruption. If styles themselves include the term, they'd need to be updated. But as I said, there's only *one* style (that we control) that fits that scenario. Even if a style did need to be updated but wasn't, the impact on output would be trivial (in the case of this style, there'd be a single, extra period). 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
