[tei-council] Licensing - 2-license

James Cummings James.Cummings at oucs.ox.ac.uk
Sat Oct 1 05:09:49 EDT 2011

On 01/10/11 09:35, Laurent Romary wrote:
> Why would not it be? Could not the same content (an XSLT fragment,
> for instance) be seen  as software if included in a processor
> (someone selling an ODD processor for instance) or a documentation
> (illustrating the way one can design XSLT stylesheets to process TEI
> documents in a tutorial). In either case, the user could say, I'm

Just to say that this is how I think XSLT stylesheets are functioning on 
the wiki. I understand Piotr and other's objections to using the wiki to 
store software, but I don't believe these are acting as software when in 
the wiki but as documentation. (This is why the sample XSLT page 
suggests having sections on Summary, Required Input, Expected Output, 
Known Restrictions or Problems, Stylesheet itself, etc.) People aren't 
supposed to be grabbing the stylesheet from wiki but instead reading it 
to learn what to do in their own stylesheets. I find plenty of code 
examples on blog posts and these function as documentation but I cut and 
paste lots of it into my own software(scripts/shell/whatever). The wiki 
functions exactly as a blog post might do, but has the benefit of being 
able to be collaboratively authored and updated.  I'd have no problem 
with people providing links from the wiki to a TEI group on github 
(let's say), but that is fulfilling a different function. That is 
providing Contributed Software rather than documentation and examples on 
small utility stylesheets.

> using TEI content under BSD-2 (resp. CC-BY). Like Piotr said, these
> should be by definition disjunctive.

Yes, I certainly agree with this part.

Dr James Cummings, InfoDev,
OUCS, University of Oxford

More information about the tei-council mailing list