| views | |
|---|---|
| Doprovod dětských pacientů a jeho význam v průběhu hospitalizace | 1 |
| views | |
|---|---|
| October 2024 | 0 |
| November 2024 | 0 |
| December 2024 | 0 |
| January 2025 | 0 |
| February 2025 | 0 |
| March 2025 | 0 |
| April 2025 | 0 |
| views | |
|---|---|
| V_05115_Zb.pdf | 17 |
Answer the questions or use the search to find the license you want
What do you want to deposit?
The work identified as being free of known restrictions under copyright law, including all related and neighboring rights.
CC Zero enables scientists, educators, artists and other creators and owners of copyright- or database-protected content to waive those interests in their works and thereby place them as completely as possible in the public domain, so that others may freely build upon, enhance and reuse the works for any purposes without restriction under copyright or database law.
This is the standard creative commons license that gives others maximum freedom to do what they want with your work.
This creative commons license is very similar to the regular Attribution license, but requires you to release all derivative works under this same license.
The no derivatives creative commons license is straightforward; you can take a work released under this license and re-distribute it but you cannot change it.
A creative commons license that bans commercial use.
A creative commons license that bans commercial use and requires you to release any modified works under this license.
The most restrictive creative commons license. This only allows people to download and share your work for no commercial gain and for no other purposes.
NOTE: This license has been superseded by the Artistic License, Version 2.0. This is a license for software packages with the intent of giving the original copyright holder some measure of control over his software while still remaining open source. It is flexible and allows you to distribute or sell modified versions as long as you fulfill one of various conditions. Look at section 4 in the full text for a better explanation.
This is a license for software packages with the intent of giving the original copyright holder some measure of control over his software while still remaining open source. It is flexible and allows you to distribute or sell modified versions as long as you fulfill one of various conditions. Look at section 4 in the full text for a better explanation.
You may copy, distribute and modify the software as long as you track changes/dates of in source files and keep all modifications under GPL. You can distribute your application using a GPL library commercially, but you must also disclose the source code.
You may copy, distribute and modify the software as long as you track changes/dates of in source files and keep modifications under GPL. You can distribute your application using a GPL library commercially, but you must also provide the source code. GPL 3 tries to close some loopholes in GPL 2.
The AGPL license differs from the other GNU licenses in that it was built for network software. You can distribute modified versions if you keep track of the changes and the date you made them. As per usual with GNU licenses, you must license derivatives under AGPL. It provides the same restrictions and freedoms as the GPLv3 but with an additional clause which makes it so that source code must be distributed along with web publication. Since web sites and services are never distributed in the traditional sense, the AGPL is the GPL of the web.
This is a lenient license used by the Mozilla Corporation that allows you a variety of explicit freedoms with the software so long as you keep modifications under this license and distribute the original source code alongside executables. It is a good midway license; it isn’t very strict and has only straightforward requirements.
You may copy, distribute and modify the software provided that modifications are described inside the modified files and licensed for free under LGPL-2.1. Derivatives or non-separate (statically-linked) works of the software must be licensed under LGPL, but separate, parent projects don't have to be.
You may copy, distribute and modify the software provided that modifications are described inside the modified files and licensed for free under LGPL-2.1. Derivatives or non-separate (statically-linked) works of the software must be licensed under LGPL, but separate, parent projects don't have to be. LGPL 3 tries to close some loopholes in LGPL 2.1.
This license, made and used by the Eclipse Foundation, isn’t all too stringent and gives both copyright and explicit patent rights. Check the full text of the license to see how liability is accorded.
This is a very permissive and popular license made by Sun Microsystems that also includes explicit patent grants. It is relatively simplistic in its conditions, requiring only a small amount of documentation for redistribution (applying to source as well as modified code).
A short, permissive software license. Basically, you can do whatever you want as long as you include the original copyright and license.
The BSD 3-clause license allows you almost unlimited freedom with the software so long as you include the BSD copyright notice in it. "Use trademark" in this case means you cannot use the names of the original company or its members to endorse derived products.
The BSD 2-clause license allows you almost unlimited freedom with the software so long as you include the BSD copyright notice in it.
A license that allows you much freedom with the software, including an explicit right to a patent. "State changes" means that you have to include a notice in each file you modified.
License Agreement for Prague Czech English Dependency Treebank 2.0
License Agreement for the CNC
License Agreement for the HamleDT 1.0
Prague Dependency Treebank, version 2.0 License Agreement
Research-Usage License Agreement for the PDTSL