Repository navigation
Explain common terms like "copyright", "patent" and "license" #238
Description
Most people have a basic grasp of licensing-related stuff, but are hazy on the exact details of what the different terms mean. It would be nice if we could have a FAQ or something to explain all of it. I'd send a patch, but I'd like to solicit some feedback on what people think the exact format should be.
Here's a list of things we might want to put on such a page:
- "Copyright"
- "License"
- "Public Domain" (specifically the fact that waiving copyright law includes waiving your right to relicense, IIUC)
- "Patent" (especially since the distinction between a patent and a copyrighted work is lost on a lot of people)
- "Copyleft"
- Warranty disclaimers/liability (maybe?)
Activity
bhuga commentedon Jan 3, 2015
This is a good idea, but I'd like to hear your thoughts on two concerns I have:
strugee commentedon Jan 3, 2015
I think so? I'm not enough of an expert on non-US intellectual property law to say definitively, but I think if we make it general enough we can find a balance. E.g. "patent" could be defined as something along the lines of, "Something that places legal protections on ideas such that the law treats the patented idea similar to how it treats property. Patents " That blurb, while getting the main idea across, doesn't really say anything specific about the law.
Alternately, we could add a note stating that the definitions provided are based on U.S. IP law.
JeromSar commentedon Feb 3, 2015
I think it's also important to clarify several other terms which use the word "patent".
For example, the Apache license includes a so called "patent grant", but the term is never further explained. For me, this was confusing and raised several questions:
I think an explanation for some of these could be included in the popovers that appear at the right side of the screen when hovering over the different characteristics.
ionas commentedon Apr 9, 2016
distribution, installation, service should also be cleared.
waldyrious commentedon Apr 24, 2016
For future reference, individual entries in this glossary should be linkable, and linked from pages on the site where they are used.
benbalter commentedon Apr 25, 2016
Just thinking through implementation, we could have a
terms.ymlfile in the_datafolder, expose it as JSON, and have a client-side script to make any use of the word on the site a tooltip using the existing tool tip library that's already loaded.waldyrious commentedon Apr 25, 2016
Rather than a custom script, why not use the build system to replace all instances of those terms with HTML
<abbr>tags?ionas commentedon Apr 25, 2016
@waldyrious
<arconym>, deprecated and not fitting.<abbr>, abbreviation not deprecated but not really fitting.What abotu
<dfn>https://developer.mozilla.org/en/docs/Web/HTML/Element/dfntuespetre commentedon May 17, 2017
I agree with @JeromSar; I am pretty ignorant when it comes to licensing and I don't have a clue what 'patent rights' means in this context or how they apply. I was hoping to find an explanation here. 😉
karam72 commentedon Apr 1, 2022
It could be great if you can include Warranty disclaimers/liability term with one simple sentence.