Intellectual Property Licenses - Revision history

Pinfold: /* Shared Source Licenses */

2025-05-23T06:04:56Z

Shared Source Licenses

← Older revision		Revision as of 06:04, May 23, 2025
Line 17:		Line 17:
	Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.		Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.

	===<span id="~~Proprietary~~">Shared Source</span> Licenses===		===<span id="shared%20source">Shared Source</span> Licenses===
	Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.		Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.

Pinfold: /* Open Source Licenses */

2025-05-23T06:04:21Z

Open Source Licenses

← Older revision		Revision as of 06:04, May 23, 2025
Line 37:		Line 37:
	This model can support innovation within a defined ecosystem (e.g., allowing hardware manufacturers to tailor drivers) but does not enable the same community-driven innovation seen in open-source projects. It maintains potential for proprietary lock-in, since recipients cannot freely distribute or fork the codebase.		This model can support innovation within a defined ecosystem (e.g., allowing hardware manufacturers to tailor drivers) but does not enable the same community-driven innovation seen in open-source projects. It maintains potential for proprietary lock-in, since recipients cannot freely distribute or fork the codebase.

	===<span id="~~Proprietary~~">Open Source</span> Licenses===		===<span id="open%20source">Open Source</span> Licenses===
	Open-source licenses allow users to access, modify, and distribute the software's source code. These licenses promote collaboration and sharing, fostering innovation and community-driven development. Open-source licenses are generally divided into two categories: permissive and copyleft.		Open-source licenses allow users to access, modify, and distribute the software's source code. These licenses promote collaboration and sharing, fostering innovation and community-driven development. Open-source licenses are generally divided into two categories: permissive and copyleft.

Pinfold: /* Proprietary LicensesShared Source Licenses */

2025-05-23T06:03:35Z

Proprietary LicensesShared Source Licenses

← Older revision		Revision as of 06:03, May 23, 2025
Line 17:		Line 17:
	Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.		Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.

	===<span id="Proprietary">~~Proprietary Licenses~~</span>~~Shared Source~~ Licenses===		===<span id="Proprietary">Shared Source</span> Licenses===
	Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.		Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.

Pinfold: /* Open Source Licenses */

2025-05-23T06:02:11Z

Open Source Licenses

← Older revision		Revision as of 06:02, May 23, 2025
Line 37:		Line 37:
	This model can support innovation within a defined ecosystem (e.g., allowing hardware manufacturers to tailor drivers) but does not enable the same community-driven innovation seen in open-source projects. It maintains potential for proprietary lock-in, since recipients cannot freely distribute or fork the codebase.		This model can support innovation within a defined ecosystem (e.g., allowing hardware manufacturers to tailor drivers) but does not enable the same community-driven innovation seen in open-source projects. It maintains potential for proprietary lock-in, since recipients cannot freely distribute or fork the codebase.

	===Open Source Licenses===		===<span id="Proprietary">Open Source</span> Licenses===
	Open-source licenses allow users to access, modify, and distribute the software's source code. These licenses promote collaboration and sharing, fostering innovation and community-driven development. Open-source licenses are generally divided into two categories: permissive and copyleft.		Open-source licenses allow users to access, modify, and distribute the software's source code. These licenses promote collaboration and sharing, fostering innovation and community-driven development. Open-source licenses are generally divided into two categories: permissive and copyleft.

Line 58:		Line 58:
	;Implications		;Implications
	Open-source licenses encourage transparency, collaboration, and rapid innovation. They allow developers to build upon existing work, reducing duplication of effort and fostering a community-driven approach to software development. However, the choice between permissive and copyleft licenses can influence how the software is used in commercial settings. Permissive licenses may be more attractive to businesses seeking to incorporate open-source code into proprietary products, while copyleft licenses ensure that improvements remain open and accessible to the community.		Open-source licenses encourage transparency, collaboration, and rapid innovation. They allow developers to build upon existing work, reducing duplication of effort and fostering a community-driven approach to software development. However, the choice between permissive and copyleft licenses can influence how the software is used in commercial settings. Permissive licenses may be more attractive to businesses seeking to incorporate open-source code into proprietary products, while copyleft licenses ensure that improvements remain open and accessible to the community.



	==Creative Works Licenses==		==Creative Works Licenses==

Pinfold: /* Shared Source Licenses */

2025-05-23T06:01:12Z

Shared Source Licenses

← Older revision		Revision as of 06:01, May 23, 2025
Line 17:		Line 17:
	Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.		Proprietary licenses can lead to vendor lock-in, where users become dependent on a single provider for software and support. This model can limit innovation and flexibility, as users cannot modify the software to suit their specific needs.

	===Shared Source Licenses===		===<span id="Proprietary">Proprietary Licenses</span>Shared Source Licenses===
	Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.		Shared source licensing represents a hybrid model that sits between proprietary (closed) and open-source licensing. Coined and popularized by Microsoft in the early 2000s, shared source allows select individuals or organizations to view and sometimes modify the source code of software, but under more restrictive terms than those found in open-source licenses.

Pinfold: /* Proprietary Licenses */

2025-05-23T06:00:38Z

Proprietary Licenses

← Older revision		Revision as of 06:00, May 23, 2025
Line 1:		Line 1:

	==Software Licenses==__NOTOC__		==Software Licenses==__NOTOC__
	===<span id="~~proprietary~~">Proprietary Licenses</span>===		===<span id="Proprietary">Proprietary Licenses</span>===
	Proprietary software licenses, also known as closed-source licenses, restrict access to the software's source code and limit how the software can be used, modified, or distributed. Under these licenses, the software is owned by an individual or company, and users are granted limited rights to use the software under specific conditions.		Proprietary software licenses, also known as closed-source licenses, restrict access to the software's source code and limit how the software can be used, modified, or distributed. Under these licenses, the software is owned by an individual or company, and users are granted limited rights to use the software under specific conditions.

Pinfold at 06:00, May 23, 2025

2025-05-23T06:00:16Z

← Older revision		Revision as of 06:00, May 23, 2025
Line 1:		Line 1:

	==Software Licenses==__NOTOC__		==Software Licenses==__NOTOC__
	===Proprietary Licenses===		===<span id="proprietary">Proprietary Licenses</span>===
	Proprietary software licenses, also known as closed-source licenses, restrict access to the software's source code and limit how the software can be used, modified, or distributed. Under these licenses, the software is owned by an individual or company, and users are granted limited rights to use the software under specific conditions.		Proprietary software licenses, also known as closed-source licenses, restrict access to the software's source code and limit how the software can be used, modified, or distributed. Under these licenses, the software is owned by an individual or company, and users are granted limited rights to use the software under specific conditions.

Pinfold at 05:32, May 13, 2025

2025-05-13T05:32:33Z

← Older revision		Revision as of 05:32, May 13, 2025
Line 189:		Line 189:

	Merchandising licenses are not only a revenue stream but also a way to enhance brand visibility and fan engagement. However, like franchise agreements, they must include quality control provisions. If the licensed goods are of poor quality or otherwise misrepresent the brand, the trademark’s reputation can suffer. U.S. trademark law requires licensors to exercise quality control over licensed products to avoid the risk of “naked licensing”—a legal term for when a trademark owner fails to maintain control, thereby potentially weakening or forfeiting the trademark’s protection.		Merchandising licenses are not only a revenue stream but also a way to enhance brand visibility and fan engagement. However, like franchise agreements, they must include quality control provisions. If the licensed goods are of poor quality or otherwise misrepresent the brand, the trademark’s reputation can suffer. U.S. trademark law requires licensors to exercise quality control over licensed products to avoid the risk of “naked licensing”—a legal term for when a trademark owner fails to maintain control, thereby potentially weakening or forfeiting the trademark’s protection.

	~~===By Degree of Openness===~~
	~~Closed/Proprietary: Restrictive; limits access and modification.~~

	~~Shared Source: Limited sharing under specific conditions.~~

	~~Open Source/Public Domain: Free to use, modify, and distribute.~~

	~~===By Intended Use===~~
	~~Commercial Licenses: For profit-driven activities.~~

	~~Non-Commercial Licenses: Restrict use to non-profit activities.~~

	~~Educational Licenses: Tailored for academic institutions.~~

	~~Government Licenses: Specific to public sector usage.~~

	~~===By Licensing Model===~~
	~~Royalty-Free: No ongoing payments required.~~

	~~Rights-Managed: Fees based on usage parameters.~~

	~~Sublicensable: Allows licensees to grant licenses to third parties.~~

Pinfold at 04:06, May 13, 2025

2025-05-13T04:06:44Z

← Older revision		Revision as of 04:06, May 13, 2025
Line 10:		Line 10:

	;Examples		;Examples
	[[Media:Microsoft EULA.pdf\|Microsoft End User License Agreement (EULA)]]: This license outlines the terms under which users can use Microsoft's software products. It typically restricts copying, modifying, or redistributing the software.		:[[Media:Microsoft EULA.pdf\|Microsoft End User License Agreement (EULA)]]: This license outlines the terms under which users can use Microsoft's software products. It typically restricts copying, modifying, or redistributing the software.
			:[[Media:Oracle Software Agreement.pdf\|Oracle License]]: Oracle's licensing agreements define how their software can be used, often including restrictions on usage in virtualized environments and specifying licensing metrics for different deployment scenarios.
	[[Media:Oracle Software Agreement.pdf\|Oracle License]]: Oracle's licensing agreements define how their software can be used, often including restrictions on usage in virtualized environments and specifying licensing metrics for different deployment scenarios.
	Oracle		Oracle

Line 26:		Line 25:
	*'''Retention of Control''': The software owner retains full rights over the source code and can dictate who can access it, how it can be used, and whether it can be redistributed.		*'''Retention of Control''': The software owner retains full rights over the source code and can dictate who can access it, how it can be used, and whether it can be redistributed.

	Examples: Microsoft’s Shared Source Initiative includes licenses like:		;Examples:
	[[Media:End User License Agreement (MS-RSL).pdf\|Microsoft Reference Source License (MS-RSL)]]: View-only for reference purposes.		Microsoft’s Shared Source Initiative includes licenses like:
	[[Media:End User License Agreement (MS-LPL).pdf\|Microsoft Limited Permissive License (MS-LPL)]]: Allows some modifications and redistribution under controlled conditions.		:[[Media:End User License Agreement (MS-RSL).pdf\|Microsoft Reference Source License (MS-RSL)]]: View-only for reference purposes.
	Microsoft Limited Community License (MS-LCL): Allows changes but only within a particular community (e.g., non-commercial developers).		:[[Media:End User License Agreement (MS-LPL).pdf\|Microsoft Limited Permissive License (MS-LPL)]]: Allows some modifications and redistribution under controlled conditions.
			:Microsoft Limited Community License (MS-LCL): Allows changes but only within a particular community (e.g., non-commercial developers).

	;Use Cases:		;Use Cases:

Pinfold at 04:03, May 13, 2025

2025-05-13T04:03:59Z

Show changes