[tei-council] agenda items

Piotr Bański bansp at o2.pl
Tue Oct 4 11:06:22 EDT 2011

On 04/10/11 11:24, Sebastian Rahtz wrote:
> On 4 Oct 2011, at 10:09, Piotr Bański wrote:
>> * software under BSD-2
>> * docs (generated HTML) under CC BY
>> * schemas, ODD, pending precedents and codification --> choice up to the
>> licensee, depending on whether they need them as software or documentation
> i thought we were proposing to dual-license everything as BSD-2 and CC-BY? ie putting both
> licenses on everything, including generated material? you make it sound here as
> if we're going to explicitly choose a different licence  for some files.

I was under impression, especially after Lou's remark, and the ensuing
exchange, that we are going to keep of nature X with their kin of genus
X. And not pretending that X, Y and Z are all Z, or all X. That is not
going to take us far.

Specifically, for documentation, I am not sure what the first sentence
of the BSD license means:" 1. Redistributions of source code must retain
the above copyright notice(...)" Are we going to pretend that HTML is
the source code of some abstract documentation? The HTML *is* the
documentation (and I mean, to be sure, the generated HTML that is
distributed separately). Or the PDF. Etc. I hope someone is not going to
say that postscript is a prog language and the clause suddenly makes
sense in this very case, because that case doesn't generalise. The
second sentence is about the binary form. The source-binary opposition
just doesn't fit documentation, does it, because it's only accidentally
applicable to latex and PDF, trying to pretend that a horse is a fox
just because it has a nice tail doesn't cut it.

I'm reminded of Michael Sperberg-McQueen's message about not knowing
what a code licence means for documentation. To paraphrase him: "you
want a single license in order to simplify stuff, that is noble. But
adopting a licence that doesn't fit its intended object is not a
simplification, it only leads to trouble!" (not that he would like to be
paraphrased, I'm sure)

And recall that the CC people very explicitly say: "do NOT use CC for

We are running in circles, this is so horribly unproductive.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4054 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20111004/e5ceb090/attachment.bin 

More information about the tei-council mailing list