I have neaver heard of any such beast. What you could always do is choose a license that matches your needs the closest and say "this article is licensed under Blah with the following further constraints..."
I'm going to forward this to Sean as well so he can get nin touch with you and ensure that what nappears on your article (license wise) is what you want.
In the message I just posted below, I had the following PRE block:
It seems the ASP.Net code block got highlighted like ASP.Net (i.e., the text is highlighted bright yellow). This is unexpected, because I set the lang to "text", not to a specific language, like "html". When I set the lang to "text", I would think there would be no special highlighting. This is how it gets rendered:
The system thought you were drunk and ignored you.
Some background: our old, old colouriser used to only be able to handle a single language within a code block (as most colourisers today do). If you had an ASP or ASPX page with inline code then you had a mix of markup and code. A user would need to specify, say, VBSsript as the language in an ASP page to make the inline VBScript look good, or they could choose ASP as the language to make the markup look good.
In order to get this working consistently we needed to override what users were specifying. Someone would create a file that had a single <% at the start and then was all C#, but we knew it was actually markup first, then C#, so we overrode their choice to make the colourisation as correct as possible.