Nick Holland wrote: > I'm not entirely sure what you are asking... Then ask for clarification.
The default in the Berne convention countries is to restrict distribution, unless specified otherwise. I want to specify otherwise. I'm looking for a short notice, ideally one line notice (pref short URL), that matches (or is) OpenBSD's ISC-variant that I can use for written works that are not code. e.g. technical writing, documentation, howtos, etc. Daniel, William and Theo pointed out in separate messages the ISC-style license is used for code in the OpenBSD project. http://www.openbsd.org/cgi-bin/cvsweb/src/share/misc/license.template?rev=1.2&content-type=text/x-cvsweb-markup I would like to be sure which statement, if any, for non-code material is already used in OpenBSD, or if there is any established practice. Anyone can write a copyright statement. It's simply more convenient for me to use one that is already written. It's even better if it is the same one as is used in an existing project. It's also convenient for the recipient(s) to see wording they've seen before. Licenses, or more accurately, copyright statements are a tool to do one thing or another. The most visible ones, like Creative Commons, are as Theo pointed out, overly long and complex. Further, for *my* purpose in just this particular case, though I have used it for other things, CC does not do what I want. > ... publish on other people's site, you follow their rules > or guidelines... I looked around in the OpenBSD manpages first using 'apropos' and missed the ISC license template provided in the base distribution because /usr/share/misc/license.template was not in whatis.db with apropos nor elsewhere I looked. > ... Usually, I prefer that what I write either stay under > regular copyright law... In Berne Convention countries, it is all under regular copyright law, or else it remains unpublished. If no copyright statement is provided with the work, then the default is restriction on re-redistribution, etc. As said above, I a) want to specify otherwise, and b) would prefer to use wording already hashed out [1] by others c) am dealing with technical writing and documentation, not code Regards, -Lars [1] "If you're going to re-invent the wheel at least try to re-invent a better one."
