[Members] XEP IP

Peter Saint-Andre stpeter at stpeter.im
Mon Dec 17 16:59:06 CST 2007


I haven't seen any feedback about this. I usually take silence as
agreement but not violent agreement. :)

Peter Saint-Andre wrote:
> A few weeks ago I posted to the Standards list about intellectual
> property [1] issues related to our XEP series:
> 
> http://mail.jabber.org/pipermail/standards/2007-October/016914.html
> 
> http://mail.jabber.org/pipermail/standards/2007-October/016915.html
> 
> However, this is really an issue for the XSF members to discuss and for
> the XSF Board to vote on.
> 
> In fact there are two issues here:
> 
> (1) I would like to accomodate the Debian team by making the rules about
> copying XEPs less restrictive.
> 
> Please see the URLs above (and follow-on messages) for discussion. I
> propose the following text, which is very similar to the MIT license
> (mostly with changes to make clear that we publish specifications that
> can be implemented in code or deployed in services):
> 
> ***
> 
> Permission is hereby granted, free of charge, to any person obtaining a
> copy of this specification (the "Specification"), to make use of the
> Specification without restriction, including without limitation the
> rights to implement the Specification in a software program, deploy the
> Specification in a network service, and copy, modify, merge, publish,
> translate, distribute, sublicense, or sell copies of the Specification,
> and to permit persons to whom the Specification is furnished to do so,
> subject to the condition that the foregoing copyright notice and this
> permission notice shall be included in all copies or substantial
> portions of the Specification. Unless separate permission is granted,
> modified works that are redistributed shall not contain misleading
> information regarding the authors, title, number, or publisher of the
> Specification, and shall not claim endorsement of the modified works by
> the authors, any organization or project to which the authors belong, or
> the XMPP Standards Foundation.
> 
> ***
> 
> (2) I think we need to add information about the warranty (in fact the
> lack of a warranty).
> 
> Following the MIT license, I propose the following:
> 
> ***
> 
> THIS SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
> IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
> CLAIM, DAMAGES OR, OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
> TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE
> SPECIFICATION OR THE IMPLEMENTATION, DEPLOYMENT, OR OTHER USE OF THE
> SPECIFICATION.
> 
> ***
> 
> No, I don't like to include things in all-caps, but that's what everyone
> else seems to do in these licenses.
> 
> If we make the foregoing changes, each XEP would contain a four-part
> legal notice, as follows:
> 
> ******
> 
> Legal Notices
> 
> IPR Conformance
> 
> This XMPP Extension Protocol has been contributed in full conformance
> with the XSF's Intellectual Property Rights Policy (a copy of which may
> be found at <http://www.xmpp.org/extensions/ipr-policy.shtml> or
> obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).
> 
> Copyright
> 
> This XMPP Extension Protocol is copyright (c) 1999 - 2007 by the XMPP
> Standards Foundation (XSF).
> 
> Permissions
> 
> Permission is hereby granted, free of charge, to any person obtaining a
> copy of this specification (the "Specification"), to make use of the
> Specification without restriction, including without limitation the
> rights to implement the Specification in a software program, deploy the
> Specification in a network service, and copy, modify, merge, publish,
> translate, distribute, sublicense, or sell copies of the Specification,
> and to permit persons to whom the Specification is furnished to do so,
> subject to the condition that the foregoing copyright notice and this
> permission notice shall be included in all copies or substantial
> portions of the Specification. Unless separate permission is granted,
> modified works that are redistributed shall not contain misleading
> information regarding the contributor, title, number, or publisher of
> the Specification, and shall not claim endorsement of the modified works
> by the contributor, any organization or project to which the contributor
> belongs, or the XMPP Standards Foundation.
> 
> Warranty
> 
> THIS SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
> IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
> CLAIM, DAMAGES OR, OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
> TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE
> SPECIFICATION OR THE IMPLEMENTATION, DEPLOYMENT, OR OTHER USE OF THE
> SPECIFICATION.
> 
> ******
> 
> I realize this is all rather long-winded, but it seems to be the right
> thing to do so that people can do things like re-use XEPs (or parts
> thereof) when distributing software, specifically in Debian.
> 
> Feedback is welcome as always.
> 
> /psa
> 
> [1] I don't like the term intellectual property, but everyone uses it.
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/members/attachments/20071217/0719b725/attachment.bin 


More information about the Members mailing list