# csl and experimental changes

**URL:** <https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045>\
**Category:** CSL Development\
**Created:** [November 15, 2011, 3:56pm UTC](https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045 "2011-11-15T15:56:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [November 15, 2011, 3:56pm UTC](https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045/1 "2011-11-15T15:56:02Z")

</div>

So given that Frank is working on innovating CSL to work for some  
funky law and multi-lingual stuff, some thoughts to ensure we can make  
it easier to merge them down the line.

At the level of the XML, it’s possible for us to define, or to  
redefine in a separate schema, the CSL schema in such a way that it  
allows foreign content. Examples:

any element = \*  
any attribute = @  
any element in a specific namespace (my preference, given that CSL is  
namespaced) = test:\*  
any attribute in a specific namespace = @test:\*

… and, of course, we can define extension points in the main schema  
to allow one to define, and add additional stuff.

Any mix of these would allow people to add stuff to styles without  
having to edit the main CSL schema source.

So that’s at the level of the XML; ways to allow experimental stuff to  
still be valid CSL, and to contain changes.

The other thing to make it easier to incorporate experimental features  
is just to make sure to document use cases and requirements, so that  
we leave room for other solutions to the same problems. It might be  
that some of the funky law stuff never makes it in, but that we have a  
csl-law.rnc file for those little extensions?

Thoughts or comments?

Bruce

---

<div class="post-metadata">

**Author:** ![Robert\_Knight](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@Robert\_Knight](https://discourse.citationstyles.org/u/Robert_Knight)\
**Post date:** [November 15, 2011, 4:00pm UTC](https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045/2 "2011-11-15T16:00:56Z")

</div>

> The other thing to make it easier to incorporate experimental  
> features is just to make sure to document use cases and requirements,  
> so that we leave room for other solutions to the same problems

Indeed, preferably in the same place that code changes and issues are  
tracked.

Regards,  
Rob.

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [November 15, 2011, 5:37pm UTC](https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045/3 "2011-11-15T17:37:30Z")

</div>

Just to clarify, are you suggesting these get tracked at the main csl  
github project?

And to be really clear, I’m almost going so far as to suggest a common  
template for feature requests going forward; in Markdown:

# Use Cases

[insert examples of what people need to be able to do that they cannot  
now, in the most clear way possible]

# Requirements

[deriving some higher-level processing principles that allows us to  
quickly understand the different design issues and tradeoffs]

# Proposal

[Not sure, but in some cases this might come in the form of a schema patch]

I think too many of the issues in the tracker result in long threads,  
and hence, wasted time.

Bruce

---

<div class="post-metadata">

**Author:** ![andrea\_rossato2](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@andrea\_rossato2](https://discourse.citationstyles.org/u/andrea_rossato2)\
**Post date:** [November 18, 2011, 9:34pm UTC](https://discourse.citationstyles.org/t/csl-and-experimental-changes/1045/4 "2011-11-18T21:34:55Z")

</div>

“Bruce D’Arcus” \<@Bruce\_D\_Arcus1\> writes:

> So given that Frank is working on innovating CSL to work for some  
> funky law and multi-lingual stuff, some thoughts to ensure we can make  
> it easier to merge them down the line.
> 
> At the level of the XML, it’s possible for us to define, or to  
> redefine in a separate schema, the CSL schema in such a way that it  
> allows foreign content. Examples:

When it comes to the XML magics to allow the kind of extensions Frank is  
developing I must confess my ignorance and the lack of time to dig into  
the problem. But I can express my interest, together with Frank’s I  
suppose, since I’m implementing most of them (I still have some doubts  
on the multi-language extensions to the JSON input for bibliographic  
data because there is no user interface in the pandoc world to permit a  
comfortable use of them).

The next pandoc will allow the use of abbreviations (it is just a start  
since ‘jurisdiction’ is not yet implemented). I really lack the time to  
code this stuff quickly but I’m slowly catching up.

Andrea
