@Charles, it would e.g. be relatively simple to convert all our dependent styles to independent styles when we transfer them to https://github.com/citation-style-language/styles-distribution. That would free the CSL software products from having to look up the parent styles, but it would complicate contributions to the CSL style repository, since users would start to modify and submit changes to those monolithic, formerly dependent styles.
@Bruce, Frank, is there really a need for a general extension mechanism? I think it would be of limited use if it only covers XML attributes. And wouldn't an uncontrolled extension mechanism encourage forking of CSL? How would we deal with arbitrary style extensions that are submitted to the style repository? I would also like to stress that CSL can already be extended through an extension schema, as we did for Frank's CSL-m fork (https://github.com/fbennett/schema/blob/master/csl-mlz.rnc), although that of course breaks compatibility with the regular CSL schema. Rintze On Sat, Feb 28, 2015 at 9:00 AM, Frank Bennett <[email protected]> wrote: >> My question is more how. > > If an extension mechanism is possible, that would be great. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
