Washington Redskins name controversy
The Washington Redskins name controversy involves the name and logo of the National Football League (NFL) franchise located in the Washington, D.C., metropolitan area. Native American individuals, tribes and organizations have been questioning the use of the name and image for decades. Over 115 professional organizations representing civil rights, educational, athletic, and scientific experts have published resolutions or policies that state that the use of Native American names and/or symbols by non-native sports teams is a harmful form of ethnic stereotyping that promote misunderstanding and prejudice which contributes to other problems faced by Native Americans.[1] The Washington, D.C. team is only one example of the larger controversy, but it receives the most public attention due to the name itself being defined as derogatory or insulting in modern dictionaries, and the prominence of the team representing the nation's capital.
Native Americans officially demanding change include hundreds of tribal nations, national tribal organizations, civil rights organizations, school boards, sports teams, and individuals.[2] The largest of these organizations, the National Congress of American Indians, count the total enrollment of its membership as 1.2 million individuals. There is also a growing number of public officials, sports commentators and other journalists advocating a change. In addition to picketing and other forms of direct protest, opponents took legal action to cancel the trademarks held by the team. On June 18, 2014, the Trademark Trial and Appeal Board (TTAB) of the United States Patent and Trademark Office (USPTO) again voted to cancel the Redskins federal trademark registrations, considering them "disparaging to Native Americans".[3][4] On July 8, 2015 the U.S. District Court in Alexandria, VA upheld the TTAB decision.
Support for continued use of the name has come from the team's owners and a majority of fans, which include some Native Americans. Supporters say that the name honors the achievements and virtues of Native Americans, and that it is not intended in a negative manner. Some, such as team president Bruce Allen,[5] also point to the use of Redskins by three high school teams, two on reservations, that have a majority of Native American students.[6] Supporters have continually asserted that a majority of Native Americans are not offended by the name based upon a single national poll done by Annenberg Public Policy Center in 2004,[7] although it has been repeatedly discredited by public opinion professionals, now including the company that collected the data. In a commentary published soon after that poll, fifteen Native American scholars collaborated on a critique that stated that there were so many flaws in the Annenberg study that rather than being a measure of Native American opinion, it was an expression of white privilege and colonialism.[8] National public opinion polls consistently find that a majority of the general public support the team's continued use of the name, ranging from 60 to 79 percent in recent years. However, three separate DC metropolitan area polls have found that a small majority of fans think the term "redskin" is offensive to Native Americans in some contexts.
Contents
History
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
In 1933 the football team that shared both the name and playing field with the Boston Braves baseball team moved to Fenway Park, already home to the Boston Red Sox. Co-owner George Preston Marshall changed the name to the Redskins, more likely to avoid confusion while retaining the "Indian" imagery of the team[9][10] than to honor coach William Henry "Lone Star" Dietz.[11] The logo for the NFL Braves was similar to the current logo, a Native American head in profile with braids and trailing feathers.[12] The current logo, proposed by Walter Wetzel, a former Blackfeet tribal chairman and president of the National Congress of American Indians, was introduced in 1972 and is modeled after the likeness on the Buffalo nickel.[13] Members of the Blackfeet tribe today express a range of opinions, from support to indifference to strong opposition to the Redskins name based upon their personal experiences.[14]
Origin and meaning
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Much of the public debate is over the meaning of the word "redskin", with team supporters frequently citing a paper by Ives Goddard, a Smithsonian Institution senior linguist and curator emeritus, who asserts that the term was originally benign in meaning.[15] However, in an interview Goddard admits that it is impossible to verify if the native words were accurately translated.[16] But then "nigger" also began as a benign reference to skin color, only to become a racial slur through disparaging usage.[17] Dr. Darren R. Reid, a history lecturer at Coventry University also states that Native American usage was generally attributed to them by European writers. Reid states that the team logo works together with the name to reinforce an unrealistic stereotype: "It is not up to non-Indians to define an idealized image of what it is to a Native American." The "positive" stereotypes allow fans and supporters to honestly state that they are honoring Native Americans, but this is "... forcing your idea of what it is to honour those people onto them and that, fundamentally, is disrespectful."[18]
Advocates of changing the name emphasize current meanings in dictionaries of American English, which include "usually offensive",[19] "disparaging",[20][21] "insulting",[22] and "taboo".[23] Such meanings are consistent with the usage found in books in the period between 1875 and 1930, which is after that studied by Goddard.[24] In the Washington Redskins trademark litigation, the linguistic expert for the petitioners, Dr. Geoffrey Nunberg, successfully argued that whatever its origins, "redskins" was a slur at the time of the trademarks, based upon the passages from books and newspapers and the movie clips in which the word is inevitably associated with contempt, derision, condescension, or sentimental paeans to the noble savage.[17] John McWhorter, an associate professor of linguistics at Columbia University compares the name's becoming a slur to the other racial terms, such as "Oriental" which acquired implied meanings associated with contempt.[25]
Some defenders of the name point to Native American use of the term, including three predominantly Native American high schools with the Redskins mascot. Native American writer and attorney Gyasi Ross compares Native American use of variations of the r-word with African-American use of variations of the n-word. The use of these terms by some members of minority communities does not mean that these words may be used by outsiders. Ross also notes that while activism on the issue may be from a minority of Native Americans, this is due to most being concerned with more immediate issues, but also says "The presentation of the name 'Redskins' is problematic for many Native Americans because it identifies Natives in a way that the vast majority of Natives simply don't identity ourselves."[26]
A controversial etymological claim is that the term emerged from the practice of paying a bounty for Indians, and that "redskin" refers to the bloody scalp of Native Americans.[27] Although official documents do not use the word in this way, at least one historical association between the use of "redskin" and the paying of bounties can be made. In 1863, a Winona, MN newspaper, the Daily Republican, printed an announcement: "The state reward for dead Indians has been increased to $200 for every red-skin sent to Purgatory. This sum is more than the dead bodies of all the Indians east of the Red River are worth."[28] This association can evoke strongly negative sentiments. In a 2014 interview after the Trademark decision, Amanda Blackhorse the lead petitioner expressed her opinion: "The name itself actually dates back [to] the time when the Native American population was being exterminated, and bounty hunters were hired to kill Native American people ... So, in order to show that they made their kill, they had to bring back a scalp or their skin."[29]
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Controversy
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
The issue is often discussed in the media in terms of offensiveness, which reduced it to feelings and opinions, and prevents full understanding of the history and context of the use of Native American names and images and why their use by sports teams should be eliminated.[30] Social science research says that sports mascots and images, rather than being mere entertainment, are important symbols with deeper psychological and social effects.[31] Stereotyping may directly affect academic performance and self-esteem of Native American youth, whose people face high rates of suicide, unemployment, and poverty.[32] Euro-Americans exposed to mascots may be more likely to believe not only that such stereotypes are true, but that Native Americans have no identity beyond these stereotypes.[33] Research demonstrates the harm of stereotyping, with studies showing that exposure to any stereotypes increased the likelihood of stereotypical thinking among citizens with regard to other groups.[34][35]
Advocates of changing the team's name say that use of stereotypes of Native Americans must be understood in the context of a history that includes conquest, forced relocation, and organized efforts by federal and state governments to eradicate native cultures, such as the boarding schools of the late 19th and early 20th centuries.[36] "Since the first Europeans made landfall in North America, native peoples have suffered under a weltering array of stereotypes, misconceptions and caricatures. Whether portrayed as noble savages, ignoble savages, teary-eyed environmentalists or, most recently, simply as casino-rich, native peoples find their efforts to be treated with a measure of respect and integrity undermined by images that flatten complex tribal, historical and personal experience into one-dimensional representations that tells us more about the depicters than about the depicted."[37]
In addition to the names and images, Native Americans opposed to mascots point to the oversimplification of their culture by fans "playing Indian" with no understanding of the deeper meaning of feathers, face paint, chants, and dancing. Dr. Richard Lapchick, director emeritus of Northeastern University's Center for the Study of Sport in Society, in an article: "Could you imagine people mocking African Americans in black face at a game? Yet go to a game where there is a team with an Indian name and you will see fans with war paint on their faces. Is this not the equivalent to black face?" [38] The unofficial mascot of the Redskins team is Zema Williams (aka Chief Zee), an African American man who has attended games since 1978 dressed in a red, faux "Indian" costume, complete with feathered war bonnet and tomahawk. Other fans often dress in similar costume for the games.[39][40]
The Redskins controversy began receiving more attention in 2013, starting with a symposium[41] in February on the topic at the Smithsonian's National Museum of the American Indian in Washington, D.C. The Oneida Indian Nation of New York sponsored a series of radio ads in each city to coincide with games of the 2013 season, each featuring a targeted message.[42] A broader range of persons spoke out in favor of change or open discussion, including local government leaders, members of Congress, and President Barack Obama. Statements in support of a name change by civil rights and religious organizations were added to those that Native American groups have been making for decades. Direct action in the form of rallies and marches have become more frequent, with a larger number of participants.
The owner[43] and the NFL Commissioner, supporters of keeping the name and logo, say they believe that it refers positively to Native Americans, invoking qualities of strength and courage. The majority of scholars argue that the use of any stereotype, whether positive or negative, is a hindrance to the advancement of a group. Scott B. Vickers wrote, "the use of any stereotype in the portrayal of Indians is considered ... to be contributory to their dehumanization and deracination."[44] The national organizations representing several academic disciplines, after reviewing the research done on the issue, have passed resolutions calling for the end of all Native American mascots and images in sports. These include the Society of Indian Psychologists (1999),[45] the American Counseling Association (2001),[46] the American Psychological Association (2005),[47] the American Sociological Association (2007).[48] and the American Anthropological Association (2015).[49] The executive board of the nation's leading organization of scholars of U.S. history approved a resolution in April 2015: "The Organization of American Historians hereby adds its voice to the growing demands by Native American organizations, our sister disciplines, and conscientious people of all ethnic backgrounds, to change the name and logo of the Washington "Redskins."[50]
In a report published by the Center for American Progress summarizing the research on "The Real Impact of Native Mascots and Team Names on American Indian and Alaska Native Youth", a case is made that the public debate misses the point, since individual opinions on either side do not matter given the measurable effects on the mental health of Native American young people exposed to such misrepresentations of their ethnic identity, and the often hostile or insulting behavior of non-natives that occur when teams with such names and mascots play.[51][52][53] Clinical Psychologist Michael Friedman writes that the use of Native imagery, in particular the use of a dictionary defined slur, is a form of bullying, the negative impact of which is magnified by its being officially sanctioned.[54]
Native American advocates of change
In the 1940s the National Congress of American Indians (NCAI) created a campaign to eliminate negative stereotyping of Native American people in the media. Over time, the campaign began to focus on Indian names and mascots in sports.[55] The NCAI maintains that teams with mascots such as the Braves and the Redskins perpetuate negative stereotypes of Native American people, and demean their native traditions and rituals.[56] The NCAI issued a new report in 2013 summarizing opposition to Indian mascots and team names generally, and the Washington Redskins in particular.[57] In the trademark case, the TTAB placed significance on the NCAI opposition, estimating that the organization represented about 30% of the Native American population at the time the trademarks were granted, which met their criteria for a "substantial composite" of Native Americans finding the name disparaging.[58] In its amicus brief filed in the case, the NCAI states that the combined enrollment of its member tribes in 2013 as 1.2 million individuals.
In addition, many tribal councils have passed resolutions or issued statements regarding their opposition to the name of the Washington NFL team, including the Cherokee and Comanche Nations of Oklahoma, the Inter Tribal Council of Arizona,[59] the Inter-Tribal Council of the Five Civilized Tribes,[60][61] the Oneida Indian Nation (New York),[62] the Navajo Nation Council,[63] the Standing Rock Sioux Tribe (North Dakota) and the United South and Eastern Tribes (USET).[64]
Other Native American groups advocating change include: the American Indian College Fund, National Indian Child Welfare Association, National Indian Education Association, National Indian Youth Council, National Native American Law Student Association, Native American Journalists Association, and Native American Rights Fund (NARF).
Individuals Native Americans who are or have been actively opposed to the Redskins' name include author and recent Presidential Medal of Freedom recipient Suzan Shown Harjo (Cheyenne/Hodulgee Muscogee),[65] Former U.S. Senator Ben Nighthorse Campbell (Northern Cheyenne),[66] director of The Smithsonian Institution's National Museum of the American Indian Kevin Gover (Pawnee),[41] author Sherman Alexie (Spokane),[67] historian and author Vine Deloria, Jr. (Sioux),[68] co-founder of the American Indian Movement Clyde Bellecourt (Ojibwe),[69] and activist/actor Russell Means (Oglala Lakota).[70]
Civil rights and religious organizations
At its annual conference the Leadership Conference on Civil and Human Rights (LCCHR), which includes the National Association for the Advancement of Colored People and the American Civil Liberties Union as members, passed a unanimous resolution [71] of the 85 representatives present that, while recognizing that a business has the First Amendment right to use any name that it chooses, others need not be complicit in the use of a pejorative and insulting name; and calling upon all Federal, state and local government entities "to end any preferential tax, zoning, or policy treatment that could be viewed as supporting the franchise as long as it retains its current team name". The resolution also commended the "current and former government officials, media outlets, and other entities that have encouraged the Washington Redskins franchise to change its team name or that have refused to be complicit in promoting the current team name".[72] In response, the team released a brief statement reiterated their previous position, and quoting two individuals as being both Native American and Redskins fans who do not want the name to change.[73] The LCCHR issued a press release in 2014 applauding the decision to cancel the trademark protection for the team's name.[74] The NAACP issued their own press release supporting the TTAB decision stating "The NAACP has called specifically for this name change since 1992, and will continue to stand with the Native Indian community until the derogatory moniker has been changed."[75]
The Fritz Pollard Alliance, a non-profit organization closely allied with the NFL on civil rights issues, has decided to announce its support of a name change after repeated attempts to discuss the issue with the team owner and representatives. An attorney for the Alliance, N. Jeremi Duru, an American University law professor, made a study of the controversy in which he concluded that Native Americans are justified in finding the name offensive.[76]
In 1992, the Central Conference of American Rabbis issued a resolution calling for the end of sports teams names that promote racism, in particular the Atlanta Braves and the Washington Redskins.[77] The Anti-Defamation League was one of the organizations signing a letter to broadcasters urging them to avoid using the name.[78] The Religious Action Center of Reform Judaism also advocates a name change.[79]
In 2013 a group of sixty-one religious leaders in Washington, D.C. sent a letter[80] to NFL Commissioner Roger Goodell and team owner Dan Snyder stating their moral obligation to join the Change the Mascot movement due to the offensive and inappropriate nature of the name which causes pain whether or not that is intended.[80][81]
In June, 2015 the United Church of Christ General Synod passed a resolution calling for a stop to using images or mascots that could be demeaning to the Native American community.[82]
Protests
Although often assumed to be a debate of recent origins, the local Washington, DC newspapers have published news items on the controversy many times since at least 1971, all in response to Native American individuals or organizations asking for the name to be changed.[83][84] National protests began in 1988, after the team's Super Bowl XXII victory, prompting numerous Native Americans wrote letters to Redskins owner Jack Kent Cooke while others boycotted Redskins products and protested, but Cooke rejected the possibility of change.[85] There was a protest of about 2,000 people at the 1992 Super Bowl between the Redskins and the Buffalo Bills. The American Indian Movement's (AIM) Vernon Bellecourt was one of the main organizers of the protest.[86]
Since 2013 picketing at the stadiums has occurred occasionally when the Redskins have played, particularly in cities with a significant population of Native Americans; such as Dallas,[87][88] Denver[89] and Minneapolis.[90][91] The latter protest was supported by several Minnesota politicians.[92][93] Picketing resumed for the 2014 season in Glendale, AZ when the team played the Arizona Cardinals,[94] and again the largest rally was in Minneapolis.[95] where estimates of the number of protestors was between 3,500 and 5,000.[96]
FedEx owns the naming rights to the team's stadium, FedEx Field through 2026, and has been the only corporate sponsor officially subject to boycotts by Native Americans: the Osage Nation,[97][98] the Native American Rights Fund (NARF) [99] and the Central Council of Tlingit and Haida Indian Tribes, the largest tribe of Native Alaskan peoples.[100]
Team and NFL responses
Following the February 2013 symposium "Racist Stereotypes and Cultural Appropriation in American Sports" at the Smithsonian National Museum of the American Indian, ten members of Congress sent a letter to the team owner and the NFL Commissioner requesting that the name be changed since it is offensive to Native Americans. In response, team owner Daniel Snyder famously told USA Today: "We'll never change the name. ... It's that simple. NEVER—you can use caps."[101] Snyder sent an open letter to fans that was published in The Washington Post on October 9, 2013 in which he stated that the most important meaning of the name Redskins is the association that fans have to memories of their personal history with the team. Snyder also states that the name was chosen in 1933 to honor Native Americans in general and the coach and four players at that time who were Native American; and that in 1971 the then coach George Allen consulted with the Red Cloud Indian Fund on the Pine Ridge reservation when designing the logo.[43] In 2013 the Red Cloud Athletic Fund sent a letter to the Washington Post stating that "As an organization, Red Cloud Indian School has never—and will never—endorse the use of the name "Redskins." Like many Native American organizations across the country, members of our staff and extended community find the name offensive."[102]
In June 2013 Roger Goodell defended the name by citing its origins, traditions and polls that support its popularity.[103][104]
On their website the team states that the 2014 annual NFL poll showing 71 percent support for the name,[105] "along with the poll taken among Native Americans by the Annenberg Institute, demonstrates continued, widespread and deep opposition to the Redskins changing our name...We respect the point of view of the small number of people who seek a name change, but it is important to recognize very few people agree with the case they are making."[106]
The team's president, Bruce Allen addressed a letter dated May 23, 2014 to Senator Reid repeating the position that the name was originated by Native Americans to refer to themselves, that the logo was also designed and approved by Native American leaders, that the vast majority of both Native Americans and the public do not find the name offensive.[107]
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Native American support
In May 2013, the Redskins' website reported the opinions of a local fan, Stephen D. Dodson, who claimed to be a chief and "full-blooded American Inuit originally from the Aleutian Tribes of Alaska." He said that not only was "Redskins" not offensive to him and his "whole family", but it was a "term of endearment" that Indians "on the reservation ... would call each other".[108] NFL commissioner Roger Goodell wrote a letter to Congress, which in part pointed to "recent remarks from Chief Steven Dodson, an American Inuit chief" to indicate support for the nickname among Native Americans.[109] Soon it was reported that the Redskins' "full-blooded American Inuit chief" was "neither, and "Chief" was only a nickname, including being on a list of AKAs from court records related to "theft, paternity, and domestic violence matters." The executive director of the Inuit Circumpolar Council-Alaska, said that neither "Chief" nor "Indian" are terms used by Alaska's native peoples [110]
On November 25, 2013 as part of the NFL's "Salute to Service" month and Native American Heritage month, the Washington Redskins recognized four members of the Navajo Code Talkers Association briefly during a commercial break. One of them, Roy Hawthorne, has stated, "My opinion is that's a name that not only the team should keep, but that's a name that's American."[111][112] This action was criticized by Amanda Blackhorse, also Navajo,[113] and described as a publicity stunt.[114] In April 2014, Navajo Nation Council voted in favor of a statement opposing the name of the Washington team, as well as other disparaging references to American Indians by other professional sports franchises.[63]
The Redskins released a two-minute video on YouTube entitled "Redskins is a Powerful Name" in which a number of Native Americans express their support for the team. Of the fourteen individuals; five are members of the Chippewa Cree tribe on the Rocky Boy Indian Reservation in Montana and are associated with the Team Redskins Rodeo club. Two are Mike Wetzel and Don Wetzel, Jr. (Blackfeet), descendants of the logo designer, and the six others are members of various tribes and state that they are fans of the team and find nothing wrong with the name, or think it is positive.[115][116][117] One of the individuals in the video is Mark One Wolf, who was reported as being born Mark E. Yancey in Washington, DC of African-American and Japanese descent.[118]
Other teams that use the name Redskins
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Supporters note that three predominantly Native American high schools use the name Redskins for their sports teams, suggesting that it can be acceptable.[119] However, the principal of one of these, Red Mesa High School in Teec Nos Pos, Arizona, said that use of the word outside American Indian communities should be avoided because it could perpetuate "the legacy of negativity that the term has created."[120] The number of high schools using the Redskins name has been in steady decline, forty percent having had local efforts to change the name. From 1988 until April 2013, 28 high schools in 18 states had done so.[121] Subsequently, seven additional high schools changed, reducing the current usage to 55. A law signed on October 11, 2015 will require the four High Schools in California to change their name by January 1, 2017.[122]
Name change as a business decision
Two professors at the Goizueta Business School at Emory University summarized their research in a New York Times editorial. Studies of college teams that have changed their names and mascots indicate that doing so has a long-term financial benefit. While vocal opponents of change often threatened withdrawal of support, these never materialized. There have been no name changes by professional teams; however, a comparison of NFL teams shows the highest negative trend in brand equity being the Washington Redskins and the Kansas City Chiefs, calling into question the business logic of retaining Native American names or logos that are offensive to even a minority.[123] In a commentary for Forbes, Tom Van Riper states that research specifically considering the fan loyalty and traditions of the team indicates that the value of the name as a brand is significant, and unlikely to change for business reasons.[124] However, an alternative opinion is that the team would benefit from a re-branding, but any new name would need to be carefully selected.[125] Despite the name controversy, the value of the team has risen $700 million to $2.4 billion (40%) based upon the valuations published by Forbes magazine in 2014 and 2015.[126][127] However, 2014 sales of Redskins merchandise has shown a decline of 35%. "People are having a second thoughts about wearing a T-shirt with the logo or name that it has now been called racist," said Matt Powell, senior analyst for SportsSourceOne. A team spokesman attributes the decline to dismal performance in the 2013 season, but other teams with bad records have not seen such a steep decline in sales.[128] Corporate sponsors have either made no public response to media inquiries regarding the name or stated that they play no role in the decision, and defer to the team and the NFL.[129][130]
Governmental and regulatory action
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Political opinion
Although the majority of those advocating a name change are Democrats, there is no indication that the issue is of any real significance in electoral decisions given that Native Americans are such a small percentage of the electorate and are not likely to influence the outcome of any election. There are only eight states where Natives make up greater than 2 percent of the population: Alaska, Arizona, Montana, New Mexico, North Dakota, Oklahoma, South Dakota and Wyoming.[131] However, polls show a definite political difference in the opinion of the general public, with only 58% of Democrats opposing a name change versus 89% of Republicans.[132] Statements by political figures have generally been expressions of personal opinion rather than recommendations for government action. There have also been non-binding resolutions advocating name change proposed in New Jersey[133] and passed in Minneapolis,[134] New York State[135][136] and California.[137]
The topic came up in a 2013 interview of President Barack Obama, who stated that if he were the owner of the Redskins, he would consider changing the name because it offends many Native Americans, but that he didn't " have a stake " in the issue as he is not an owner of a professional sports team.[138] However, in November, 2015 Obama, speaking at the White House Tribal Nations Conference, stated "Names and mascots of sports teams like the Washington Redskins perpetuate negative stereotypes of Native Americans" and praised Adidas for a new initiative to help schools change names and mascots by designing new logos and paying for part of the cost of new uniforms.[139] On May 22, 2014, fifty U.S. Senators, forty-eight Democrats and two Independents, sent a letter[140] to NFL Commissioner Goodell asking the league, referencing the Donald Sterling case, "send the same clear message as the NBA did: that racism and bigotry have no place in professional sports." Five Democratic Senators declined to sign the letter, and Republicans were not invited to do so.[141] No Senators have publicly supported the name, but rather have either declined to give an opinion or stated their opposition to Senate involvement in the issue.[142][143]
DC Metro area jurisdictions
Much of the local political discussion has been about building a stadium, beginning in the 1990s when a Maryland location was chosen for the what is now FedEx Field.[144] With the possibility of building a new stadium in the near future, both the previous[145] and current mayors of the District of Columbia have stated that a name change must be part of the discussion,[146] however the team rejects that possibiltiy.[147] Virginia Governor Terry McAuliffe has met with the owner to discuss the building of a new stadium in Virginia.[148] For many years, beginning with the departure of the Baltimore Colts, the Redskins were the only NFL team in a large area from Maryland into the southern states. This is slowly changing as Maryland NFL fans move to the Baltimore Ravens.[149] Several Maryland politicians have stated that the name should change,[150][151][152] but the current governor opposes any change, also citing the desire to keep the stadium in Maryland.[153] Virginia fans are now the more numerous and dedicated supporters of the Redskins, and the state and local governments have used economic incentives to encourage the team's relocation of its facilities there, and maintain that the name is entirely a business decision for the team to make.[154][155][156][157]
Trademark cases
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
In 1992, Suzan Shown Harjo, with six other prominent Native Americans petitioned the U.S. Patent and Trademark Office (USPTO) to cancel the trademark registrations owned by Pro-Football, Inc. In 1999 the Trademark Trial and Appeal Board (TTAB) judges canceled the federal registration of the mark REDSKINS.[158] In 2005 the United States District Court for the District of Columbia reversed the TTAB's decision on the grounds of insufficient evidence of disparagement. Subsequent appeals were rejected on the basis of laches, that the Native Americans had pursued their rights in an untimely manner, in other words they were too old. A second case was filed[159] with younger plaintiffs led by Amanda Blackhorse.[160] On June 18, 2014, the TTAB again voted to cancel the six trademarks held by the team in a two to one decision that held that the term "redskins" is disparaging to a "substantial composite of Native Americans", and this is demonstrated "by the near complete drop-off in usage of 'redskins' as a reference to Native Americans beginning in the 1960s." [161][162] The TTAB majority held that the NCAI represented about 30 percent of Native Americans during the time in question, which the Board found satisfied the substantial composite test.[163][164] The TTAB also found that the term "redskin" refers to Native Americans (rather than having an "independent meaning" as the team sometimes claims) as shown by the costumes worn by both the cheerleaders and marching band from the 1960s until the 1980s, and the native imagery used on the press guides for many years.[165]
Evidence of disparagement include the frequent references to "scalping" made by sportswriters for sixty years when reporting the Redskins loss of a game,[166] and passages from movies made from the 1940s to the 1960s using "redskin" to refer to Native Americans as a savage enemy.[167] A linguistics expert for the team unsuccessfully argued that the name is merely a descriptive term no different than other uses of color to differentiate people by race.[168]
Reaction to the TTAB decision has often characterized it as government interference in a private business, or as an improper limitation on freedom of expression,[169][170] but in fact withdraws the government from the responsibility to regulate the use of the name by anyone.[171] The team retains other rights under common law, but must enforce them without Federal government assistance.
On July 8, 2015, District Court Judge Lee affirmed the decision of the Trademark Trial and Appeal Board,[172] denying the team's summary judgment motions challenging the constitutionality of the Lanham Act and granted the Blackhorse Defendants' summary judgment motions, finding that "the evidence before the Court supports the legal conclusion that ... the Redskin Marks consisted of matter that 'may disparage' a substantial composite of Native Americans." The decision does not bar the team from using the marks and taking other steps to protect other rights to their brand.[173] On October 30, 2015 Pro-Football, Inc. filed its appeal with the United States Court of Appeals for the Fourth Circuit. In addition to maintaining the validity of all the arguments rejected by both the TTAB and the first appeal,[174] the team has added a list of names they claim are offensive and racist that have been given trademarks, thus making the cancellation of their marks unequal treatment.[175][176]
In December 2015, the Federal Circuit Court of Appeals struck down the prohibition of "disparaging" trademarks in a separate case involving a similar denial of trademark registration to the Asian-American band The Slants.[177] The majority opinion stated, in part, that "[w]hatever our personal feelings about the mark at issue here, or other disparaging marks, the First Amendment forbids government regulators to deny registration because they find speech likely to offend others."[178]
Public opinion
While varying somewhat, national opinion polls consistently indicate that a majority of the general public do not advocate a name change: 79 percent (April 2013),[66] 60 percent (June 2014),[179] and 71 percent (September 2014). [180] While yielding overall results similar to national polls, with a majority supporting the team keeping the name, local surveys often ask additional questions. In three polls, although they supported the team name, 59 percent, [181] 56 percent, [182] and 53 percent[183] of DC, Maryland, and Virginia fans also said that the word "redskin" is offensive to Native Americans in at least some contexts. The September 2014 national poll found that 68 percent think the name is not disrespectful of Native Americans, 19 percent say it shows "some" disrespect, and 9 percent say it is "a lot" disrespectful.[180]
However, there are those that question the appropriateness of submitting minority rights to a majority decision. Louis Gray, president of the Tulsa Indian Coalition Against Racism and an Osage Indian: "You wouldn't [take a poll] with any other race. You wouldn't have African-Americans vote to decide whether or not any sort of racial epithet would be offensive."[184]
The survey most frequently cited by opponents of change as definitive of Native American opinion was performed in 2004 as part of the National Annenberg Election Survey. Among other questions regarding election year issues, respondents who identified themselves as being Native American were asked: "The professional football team in Washington calls itself the Washington Redskins. As a Native American, do you find that name offensive or doesn't it bother you?" In response, ninety percent replied that the name did not bother them, while nine percent said that it was offensive, and one percent would not answer.[7] The methods used in this survey and the conclusions that can be drawn from it has been criticized by social scientists,[185] Native American scholars[8] and legal experts[186] for years. In August, 2015, a memo written by senior researchers at the organization responsible for collecting the data for the survey which made it clear that it should not be taken as an accurate reflection of Native American attitudes at the time.[187]
An alternative method to standard opinion polls was used by the Center for Indigenous Peoples Studies at California State University, San Bernardino. A survey was conducted of 400 individuals, with 98 individuals positively identified as Native Americans, finding that 67% agreed with the statement that "Redskins" is offensive and racist. The response from non-natives was almost the opposite, with 68% responding that the name is not offensive.[188][189]
Other support for the name
Native Americans
A brother and sister in Oneida, New York, state they are both Native American (Mohawk) and ardent Redskins fans.[190] Three Virginia Indian leaders say they are not offended by the name Redskins, but are more concerned about other issues such as the lack of Federal recognition for any Virginia tribe.[191] Robert "Two Eagles" Green, retired chief of the Fredericksburg area Patawomeck Tribe, stated on a radio talk show he'd be offended if the team does change its name.[192] In an article in The American Spectator, the current chief of the Patawomeck Tribe, John Lightner, states that while he is not offended by the current name, he would support changing the team to the Washington Potomacs.[193]
In the media
Defense of the Redskins name has come mainly from conservatives, such as George Will,[194] Pat Buchanan,[195] W. James Antle III,[196] Rich Lowry,[197] Dennis Prager,[198] Rush Limbaugh,[199] and Glenn Beck.[200]
See also
Notes
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.(Carter Meland (Anishinaabe) and David E. Wilkins (Lumbee) are professors of Native American Studies at the University of Minnesota.)
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 66.0 66.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Dirk Lammers, "Russell Means, Indian Activist and Fighting Sioux Nickname Critic, Dies at 72," Associated Press (October 22, 2012), http://www.wdaz.com/event/article/id/15378/#sthash.E0OseRD4.dpuf
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 80.0 80.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 180.0 180.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.