Difference between revisions of "Commentary:Use for Software"

From Model Trademark Guidelines
Jump to: navigation, search
(Section entitled "Uses for which we are granting a license")
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
===Commentary on Use for software===
+
The "Commentary" pages are are explanatory material relevant to those adopting the Model Trademark Guidelines, like Reporter's Notes for a Restatement or advisory committee notes for model laws. They provide information to the end users of the guidelines about the legal, practical and ideological rationale embodied in the guidelines.
  
These guidelines have taken the view that any modification to the software from that found in the official repository requires a trademark license. This includes binary code that is created by a third party from source, i.e., the third-party created binary will be considered modified code. Some open source software providers have had their product combined with malicious software, which negatively affects the reputation of the open source project. For this reason, any software is considered non-authentic if the modification is beyond what is permitted in the guidelines.
+
If you want to discuss what's on the Commentary page, use the "Discussion" tab for the Commentary page.
  
==== Uses for which we are granting a license ====
+
===Commentary on Use for software===
  
U.S: A licensee's use of a trademark on goods or services over which the trademark owner does not exercise adequate control may be considered a “naked license” and a form of abandonment of the trademark. In the U.S., this militates that the trademark owner must be able to argue that it has adequately exercised control over the quality of the goods and services with which its mark is used.
+
==== General principles ====
  
Although a license granted to unknown users where the quality is controlled solely by describing the attributes that the goods must has never been tested in court, this should be considered adequate control. Therefore, if the adopter of these Guidelines wants to allow the use of the Marks for modified software, the Mark owner must identify a limited number of changes that will not significantly affect the quality of the goods, so that it can say with certainty that any goods using the Marks are of a known quality with known features.
+
===== U.S. law =====
 
U.S. law: A license is a defense to an infringement claim, i.e., but for the license the accused use would be a trademark infringement.
 
  
U.S. law: Limitations on when trademark may be used should be expressed as condition of license, not covenant, so that a failure to meet the limitation is a basis for a trademark infringement claim.
+
It is not necessary that there be a sale for there to be trademark rights. ''See'' ''Planetary Motion, Inc. v. Techsplosion, Inc.'', 261 F.3d 1188, 59 U.S.P.Q.2d 1894, 51 Fed. R. Serv. 3d 294 (11th Cir. 2001) (distribution of COOLMAIL software over the Internet was sufficient to establish trademark rights: "[T]he existence of sales or lack thereof does not by itself determine whether an user of a mark has established ownership rights therein.").  
  
U.S.: Under current U.S. jurisprudence, it is unlikely that any use of a logo would be considered a nominative/referential fair use. Therefore, permission to use the logo may be found  under the licensing provisions, not as a non-infringing use
+
===== Law of other jurisdictions =====
  
====Uses we consider non-infringing====
+
==== Section entitled "Uses for which we are granting a license" ====
  
U.S. Under U.S. law, resale of genuine goods is not an infringement as long as the goods are not “materially different” from the original.
+
These guidelines have taken the view that any modification to the software from that found in the official repository requires a trademark license. This includes binary code that is created by a third party from source, i.e., the third-party created binary will be considered modified code. Some open source software providers have had their product combined with malicious software, which negatively affects the reputation of the open source project. For this reason, any software is considered non-authentic if the modification is beyond what is permitted in the guidelines.
  
Because the goods discussed in this section, software, are identical to the trademark owner's goods and the trademark is identical, any use outside the scope of the resale (or redistribution) of authentic (unmodified) goods would be an infringement. Distribution of modified software requires a license.
+
===== U.S. law =====
  
===Official Branding Flag?===
+
A licensee's use of a trademark on goods or services over which the trademark owner does not exercise adequate control may be considered a “naked license” and a form of abandonment of the trademark. In the U.S., this militates that the trademark owner must be able to argue that it has adequately exercised control over the quality of the goods and services with which its mark is used.
  
I wonder if it is good practice to encourage software projects to build their software with a compile-time flag which makes it easy to include or exclude their trademarks? This would then allow the trademark policy to say "we as a project guarantee that if you don't enable this flag, then our trademarked logos and names won't be used in the package in a way which requires permission. And if we accidentally do include a logo in the non-branded version, we won't give you grief about it." That enables people to opt into or out of trademark use easily.
+
Although a license granted to unknown users where the quality is controlled solely by describing the attributes that the goods must has never been tested in court, this should be considered adequate control. Therefore, if the adopter of these Guidelines wants to allow the use of the Marks for modified software, the Mark owner must identify a limited number of changes that will not significantly affect the quality of the goods, so that it can say with certainty that any goods using the Marks are of a known quality with known features.
  
Mozilla software has a "--enable-official-branding" flag (so official branding is disabled by default) although I'm not sure we provide the guarantee in that form.  
+
A license is a defense to an infringement claim, i.e., but for the license the accused use would be a trademark infringement.
  
If we do want to encourage this practice, what's the best way to do it? Include sample text in the policy, and encourage projects to alter their software to make the text true?
+
Limitations on when trademark may be used should be expressed as condition of license, not covenant, so that a failure to meet the limitation is a basis for a trademark infringement claim.
  
-- [[User:Gerv|Gerv]] ([[User talk:Gerv|talk]]) 10:20, 25 March 2013 (EDT)
+
Under current U.S. jurisprudence, it is unlikely that any use of a logo would be considered a nominative/referential fair use. Therefore, permission to use the logo may be found  under the licensing provisions, not as a non-infringing use.
  
===Media restrictions?===
+
===== Law of other jurisdictions =====
  
Is this section intended to restrict distribute only to "optical media, memory stick or download"? That sounds like a paragraph ripe for unintended technological obsolescence :-) There's already rotating magnetic media that you've missed out, and I'm sure people will invent new media forms.
+
==== Section entitled "Uses we consider non-infringing" ====
  
-- [[User:Gerv|Gerv]] ([[User talk:Gerv|talk]]) 10:33, 25 March 2013 (EDT)
+
===== U.S. law =====
  
===Porn problem?===
+
U.S. Under U.S. law, resale of genuine goods is not an infringement as long as the goods are not “materially different” from the original.
  
What if a community wants to restrict the logo from being used in pornographic or other themes, skins or personas? Do we provide an option for that? On a more general question, there doesn't seem to be a non-disparagement clause anywhere. Do we intend to have one?
+
Because the goods discussed in this section, software, are identical to the trademark owner's goods and the trademark is identical, any use outside the scope of the resale (or redistribution) of authentic (unmodified) goods would be an infringement.  Distribution of modified software requires a license.
  
-- [[User:Gerv|Gerv]] ([[User talk:Gerv|talk]]) 10:33, 25 March 2013 (EDT)
+
===== Law of other jurisdictions =====

Latest revision as of 17:21, 24 October 2022

The "Commentary" pages are are explanatory material relevant to those adopting the Model Trademark Guidelines, like Reporter's Notes for a Restatement or advisory committee notes for model laws. They provide information to the end users of the guidelines about the legal, practical and ideological rationale embodied in the guidelines.

If you want to discuss what's on the Commentary page, use the "Discussion" tab for the Commentary page.

Commentary on Use for software[edit]

General principles[edit]

U.S. law[edit]

It is not necessary that there be a sale for there to be trademark rights. See Planetary Motion, Inc. v. Techsplosion, Inc., 261 F.3d 1188, 59 U.S.P.Q.2d 1894, 51 Fed. R. Serv. 3d 294 (11th Cir. 2001) (distribution of COOLMAIL software over the Internet was sufficient to establish trademark rights: "[T]he existence of sales or lack thereof does not by itself determine whether an user of a mark has established ownership rights therein.").

Law of other jurisdictions[edit]

Section entitled "Uses for which we are granting a license"[edit]

These guidelines have taken the view that any modification to the software from that found in the official repository requires a trademark license. This includes binary code that is created by a third party from source, i.e., the third-party created binary will be considered modified code. Some open source software providers have had their product combined with malicious software, which negatively affects the reputation of the open source project. For this reason, any software is considered non-authentic if the modification is beyond what is permitted in the guidelines.

U.S. law[edit]

A licensee's use of a trademark on goods or services over which the trademark owner does not exercise adequate control may be considered a “naked license” and a form of abandonment of the trademark. In the U.S., this militates that the trademark owner must be able to argue that it has adequately exercised control over the quality of the goods and services with which its mark is used.

Although a license granted to unknown users where the quality is controlled solely by describing the attributes that the goods must has never been tested in court, this should be considered adequate control. Therefore, if the adopter of these Guidelines wants to allow the use of the Marks for modified software, the Mark owner must identify a limited number of changes that will not significantly affect the quality of the goods, so that it can say with certainty that any goods using the Marks are of a known quality with known features.

A license is a defense to an infringement claim, i.e., but for the license the accused use would be a trademark infringement.

Limitations on when trademark may be used should be expressed as condition of license, not covenant, so that a failure to meet the limitation is a basis for a trademark infringement claim.

Under current U.S. jurisprudence, it is unlikely that any use of a logo would be considered a nominative/referential fair use. Therefore, permission to use the logo may be found under the licensing provisions, not as a non-infringing use.

Law of other jurisdictions[edit]

Section entitled "Uses we consider non-infringing"[edit]

U.S. law[edit]

U.S. Under U.S. law, resale of genuine goods is not an infringement as long as the goods are not “materially different” from the original.

Because the goods discussed in this section, software, are identical to the trademark owner's goods and the trademark is identical, any use outside the scope of the resale (or redistribution) of authentic (unmodified) goods would be an infringement. Distribution of modified software requires a license.

Law of other jurisdictions[edit]