Changes

[[CPA AUSTRALIA LTD]] (CPA Australia) represents a membership of 139,000 Certified Practicing Accountants (CPAs) spread across 114 countries, with a particularly strong presence in the fast growing Asia-Pacific region including China, Hong Kong and Singapore. Registration will be open to full CPA members and students; and "[a]t some point in the future, the CPA Australia community may review and consider expanding the community to include practicing accountants and other members of various CPA organisations around the world which also use a similar CPA designation."<ref>Application 1-1744-1971</ref>

[[CPA AUSTRALIA LTD]] (CPA Australia) represents a membership of 139,000 Certified Practicing Accountants (CPAs) spread across 114 countries, with a particularly strong presence in the fast growing Asia-Pacific region including China, Hong Kong and Singapore. Registration will be open to full CPA members and students; and "[a]t some point in the future, the CPA Australia community may review and consider expanding the community to include practicing accountants and other members of various CPA organisations around the world which also use a similar CPA designation."<ref>Application 1-1744-1971</ref>

4. <big>'''[[.eco]]'''</big>, There are 4 applications for [[.eco]], including the one community application from [[Big Room Inc.]]. "In 2009, Big Room, itself a Certified B Corporation obliged to consider environmental, social and financial interests, launched an international multi-year stakeholder consultation process with the Community on the potential for .ECO to exist as a Community TLD. The process included 7 in-person consultations on 5 continents. Draft policies were published for 3 public comment periods of at least 30 days each...Since establishment, this international multi-stakeholder community council, made up of leading environmental organizations including WWF International, Greenpeace International, Green Cross International and others, has worked to define the mission, purpose and policies for a .ECO Community TLD that reflects the Community’s interests. The council’s work included 2 in-person meetings (Brussels ⁄ Washington, DC) and more than 20 conference calls between members. In September 2010, the council unanimously adopted a charter for the .ECO Community TLD - the .ECO Policy Consensus. The purpose and principles outlined in the .ECO Policy Consensus define what .ECO will mean as an active expression of the goals, values and interests of the Community. The Consensus has been reviewed and affirmed by the Big Room board of directors."

4. <big>'''[[.eco]]'''</big>, There are 4 applications for [[.eco]], including the one community application from [[Big Room Inc.]]. "In 2009, Big Room, itself a Certified B Corporation obliged to consider environmental, social and financial interests, launched an international multi-year stakeholder consultation process with the Community on the potential for .ECO to exist as a Community TLD. The process included 7 in-person consultations on 5 continents. Draft policies were published for 3 public comment periods of at least 30 days each...Since establishment, this international multi-stakeholder community council, made up of leading environmental organizations including WWF International, Greenpeace International, Green Cross International and others, has worked to define the mission, purpose and policies for a .ECO Community TLD that reflects the Community’s interests. The council’s work included 2 in-person meetings (Brussels ⁄ Washington, DC) and more than 20 conference calls between members. In September 2010, the council unanimously adopted a charter for the .ECO Community TLD - the .ECO Policy Consensus. The purpose and principles outlined in the .ECO Policy Consensus define what .ECO will mean as an active expression of the goals, values and interests of the Community. The Consensus has been reviewed and affirmed by the Big Room board of directors."

17. <big>'''[[.swiss]]'''</big>, There are two applicants for the [[.swiss]] TLD; [[Swiss International Air Lines Ltd.]] and the [[Swiss Confederation]], the latter is a [[Community TLD|Community Priority Applicant]]. The .swiss registry is fully recognized by the Sovereign Confederation of Switzerland. It has secure [[CORE]] at its backend registry operator. "The purpose of the TLD .swiss is to serve the Swiss community, defined as the community of individuals, legal entities and public institutions with a bona fide presence in Switzerland."

17. <big>'''[[.taxi]]'''</big>, There are 3 applicants for [[.taxi]], including a community priority application submitted by [[Taxi Pay GmbH]]. Its primary supporters include taxi organizations and associations in Germany and Austria. It identifies four type of taxi community members: The core industry of taxi drivers and offices; the related industries involved in hardware and software suppliers, automotive repair shops, and insurance companies; subordinate organizations affiliated with government supervision and policy development; and major institutions and locations that rely heavily on taxi services in and around their venue(s).  

 

 

 

 

18. <big>'''[[.taxi]]'''</big>, There are 3 applicants for [[.taxi]], including a community priority application submitted by [[Taxi Pay GmbH]]. Its primary supporters include taxi organizations and associations in Germany and Austria. It identifies four type of taxi community members: The core industry of taxi drivers and offices; the related industries involved in hardware and software suppliers, automotive repair shops, and insurance companies; subordinate organizations affiliated with government supervision and policy development; and major institutions and locations that rely heavily on taxi services in and around their venue(s).  

"First, an applicant for a .taxi second level domain has to submit proof of his or her affiliation with the taxi industry to the desired registrar. This process does not involve any formalities on the side of TaxiPay GmbH except an official document, such as a taxi license or a commensurate certificate of registration stating the purpose of the company and aligning it with a strong affiliation to the taxi community."<ref>Application 1-1025-18840</ref>

"First, an applicant for a .taxi second level domain has to submit proof of his or her affiliation with the taxi industry to the desired registrar. This process does not involve any formalities on the side of TaxiPay GmbH except an official document, such as a taxi license or a commensurate certificate of registration stating the purpose of the company and aligning it with a strong affiliation to the taxi community."<ref>Application 1-1025-18840</ref>

19. <big>'''[[.tennis]]'''</big>, There are 4 applicants for [[.tennis]], including one community applicant, [[Tennis Australia Ltd]], which is the governing body for Tennis in Australia. "Only individuals and entities belonging to the Tennis Australia community will be eligible to register  a domain name within the .tennis TLD, as strict eligibility criteria will be introduced...Tennis Australia provides benefits to 2,176 affiliated tennis clubs and their over 180,000 tennis player members throughout Australia."

18. <big>'''[[.tennis]]'''</big>, There are 4 applicants for [[.tennis]], including one community applicant, [[Tennis Australia Ltd]], which is the governing body for Tennis in Australia. "Only individuals and entities belonging to the Tennis Australia community will be eligible to register  a domain name within the .tennis TLD, as strict eligibility criteria will be introduced...Tennis Australia provides benefits to 2,176 affiliated tennis clubs and their over 180,000 tennis player members throughout Australia."

Current language in its application does not seem to leave room for any registration of the [[.tennis]] TLD outside of Australia.<ref>Application 1-1723-69677</ref>

Current language in its application does not seem to leave room for any registration of the [[.tennis]] TLD outside of Australia.<ref>Application 1-1723-69677</ref>

20. <big>'''[[.webs]]'''</big>, two applications for [[.webs]] were submitted by the same applicant, [[Vistaprint Limited]]. They define their community as users of their online portal, webs.com: "The ‘WEBS’ community was created in late 2005 by Freewebs, now called Webs, Inc. Webs, Inc. presently is a subsidiary of the Applicant... Since 2006, the Applicant started by giving its users the option to publish their myWebs profile as a page on their website, making it accessible and searchable to all Freewebs – and later on Webs – visitors. The Applicant invested in creating the tools necessary for its members to simply create their Web presence and share their passions with the world. Since its inception, the name of the community was ‘WEBS’. This is shown by the mention of ‘myWebs’ and the mention of the name ‘Webs’ as such to refer to the blog that was used by the community to communicate with each other to share Webs experiences... In 2008 this resulted in the rebranding of the company name from Freewebs into Webs. The community only became stronger and the aim was to have visitors to become active participants. The Applicant, through the Webs platform lets site owners create community-driven sites that visitors can join as members. By giving site members the ability to comment on photos, post to a blog, add to a site calendar, and more, a site becomes more of a living, breathing entity and a reflection of the Webs community."

19. <big>'''[[.webs]]'''</big>, two applications for [[.webs]] were submitted by the same applicant, [[Vistaprint Limited]]. They define their community as users of their online portal, webs.com: "The ‘WEBS’ community was created in late 2005 by Freewebs, now called Webs, Inc. Webs, Inc. presently is a subsidiary of the Applicant... Since 2006, the Applicant started by giving its users the option to publish their myWebs profile as a page on their website, making it accessible and searchable to all Freewebs – and later on Webs – visitors. The Applicant invested in creating the tools necessary for its members to simply create their Web presence and share their passions with the world. Since its inception, the name of the community was ‘WEBS’. This is shown by the mention of ‘myWebs’ and the mention of the name ‘Webs’ as such to refer to the blog that was used by the community to communicate with each other to share Webs experiences... In 2008 this resulted in the rebranding of the company name from Freewebs into Webs. The community only became stronger and the aim was to have visitors to become active participants. The Applicant, through the Webs platform lets site owners create community-driven sites that visitors can join as members. By giving site members the ability to comment on photos, post to a blog, add to a site calendar, and more, a site becomes more of a living, breathing entity and a reflection of the Webs community."

To begin with the TLD will be a [[Single Registrant TLD]], meaning that the applicant will use it for their own commercial and internal profits and not offer registration to the wider community. "At a later stage, in addition to the Applicant and⁄or its subsidiaries, members of the Webs community will possibly be entitled to register domain names in .WEBS. That is to say, one of the main eligibility criteria will be that the interested party wishing to register a domain name in the .WEBS TLD is either a member of the Applicant or has a sufficiently close link to the Webs community."<ref>Application 1-1033-22687</ref>

To begin with the TLD will be a [[Single Registrant TLD]], meaning that the applicant will use it for their own commercial and internal profits and not offer registration to the wider community. "At a later stage, in addition to the Applicant and⁄or its subsidiaries, members of the Webs community will possibly be entitled to register domain names in .WEBS. That is to say, one of the main eligibility criteria will be that the interested party wishing to register a domain name in the .WEBS TLD is either a member of the Applicant or has a sufficiently close link to the Webs community."<ref>Application 1-1033-22687</ref>

===Contested Brand Community Apps===

===Contested Brand Community Apps===

21. <big>'''[[.merck]]'''</big>, There are three applications from two applicants for [[.merck]]. The American healthcare company, [[Merck & Co. Inc.]], applied twice, once through a community application and once as a general applicant. This was clearly done as a way to edge out any competition that may have also applied for a Merck community application, or keep a stake in the [[.merck]] TLD should its own community status be denied. The competitive community applicant is the German-based [[Merck KGaA]] pharmaceutical company, which employes over 40,000 people in 70 countries.

20. <big>'''[[.merck]]'''</big>, There are three applications from two applicants for [[.merck]]. The American healthcare company, [[Merck & Co. Inc.]], applied twice, once through a community application and once as a general applicant. This was clearly done as a way to edge out any competition that may have also applied for a Merck community application, or keep a stake in the [[.merck]] TLD should its own community status be denied. The competitive community applicant is the German-based [[Merck KGaA]] pharmaceutical company, which employes over 40,000 people in 70 countries.

"[[Merck & Co. Inc.]], parent of Merck Sharp and Dohme Corp., Whitehouse Station, New Jersey, USA (collectively “Merck”), is a Fortune 100 company and one of the largest healthcare companies in the world. Merck has operated under the Merck name and trademark in the United States and Canada since as early as 1920." It defines its community as its own healthcare and pharmaceutical business but also its philanthropic and corporate responsibility programs, and its publications and websites. Registration will be restricted to the company, its subsidiaries, and authorized partners.<ref>Application 1-1702-73085. Retrieved 15 November 2012</ref>

"[[Merck & Co. Inc.]], parent of Merck Sharp and Dohme Corp., Whitehouse Station, New Jersey, USA (collectively “Merck”), is a Fortune 100 company and one of the largest healthcare companies in the world. Merck has operated under the Merck name and trademark in the United States and Canada since as early as 1920." It defines its community as its own healthcare and pharmaceutical business but also its philanthropic and corporate responsibility programs, and its publications and websites. Registration will be restricted to the company, its subsidiaries, and authorized partners.<ref>Application 1-1702-73085. Retrieved 15 November 2012</ref>

===Contested IDN Community Apps===

===Contested IDN Community Apps===

22. <big>'''[[.广东]]'''</big>, there are two applicants for the [[IDN]] [[.广东]], which translates as "Guangdong", China's most populous province. The two applicants are the [[Xinhua News Agency Guangdong Branch]] and the [[Guangzhou YU Wei Information Technology Co., Ltd.]]; the former applied as a community priority applicant.

21. <big>'''[[.广东]]'''</big>, there are two applicants for the [[IDN]] [[.广东]], which translates as "Guangdong", China's most populous province. The two applicants are the [[Xinhua News Agency Guangdong Branch]] and the [[Guangzhou YU Wei Information Technology Co., Ltd.]]; the former applied as a community priority applicant.

[[Xinhua News Agency Guangdong Branch]], the community applicant, applied with consultive help from [[CNNIC]], the Chinese national registry, and the [[DotAsia Organisation]]. The application's contact is [[Edmon Chung]], CEO of the DotAsia Organisation. "With a population of over 100 million, a GDP of over US$800 Billion, and established since AD 226, the community is sizable and has considerable longevity." The applicant defines the community as the individuals, organizations, and companies in Guangdong province, the international Cantonese language community, which originated from Guangdong originally, and companies interested in expanding into Guangdong. The applicant lists a number of organizations and regional representatives to which it intends to reach out and serve. "the Registry will work closely with community organizations and will invite community organizations in its policy development processes.  Furthermore, the Applicant is official government agency of the Guangdong province." Their registration policy will be based off of the [[.asia]] charter.<ref>Application 1-1309-35206. Retrieved November 15.</ref>

[[Xinhua News Agency Guangdong Branch]], the community applicant, applied with consultive help from [[CNNIC]], the Chinese national registry, and the [[DotAsia Organisation]]. The application's contact is [[Edmon Chung]], CEO of the DotAsia Organisation. "With a population of over 100 million, a GDP of over US$800 Billion, and established since AD 226, the community is sizable and has considerable longevity." The applicant defines the community as the individuals, organizations, and companies in Guangdong province, the international Cantonese language community, which originated from Guangdong originally, and companies interested in expanding into Guangdong. The applicant lists a number of organizations and regional representatives to which it intends to reach out and serve. "the Registry will work closely with community organizations and will invite community organizations in its policy development processes.  Furthermore, the Applicant is official government agency of the Guangdong province." Their registration policy will be based off of the [[.asia]] charter.<ref>Application 1-1309-35206. Retrieved November 15.</ref>

===Contested Geo Community Apps===

===Contested Geo Community Apps===

23. <big>'''[[.osaka]]'''</big> Interestingly, the government of Osaka, Japan, gave permission to four different entities to apply for the [[GeoTLD]], [[.osaka]]. In the end, two companies applied, [[GMO Registry]] and [[Interlink Co. Ltd.]]. The later is a ISP and [[registrar]], while the former is a company formed to apply for new TLDs and provide TLD consultancy services.<ref>[http://domainincite.com/7936-four-companies-given-ok-for-osaka Four Comapnies Given Ok for Osaka]DomainIncite.com. Retrieved 15 November 2012</ref>

22. <big>'''[[.osaka]]'''</big> Interestingly, the government of Osaka, Japan, gave permission to four different entities to apply for the [[GeoTLD]], [[.osaka]]. In the end, two companies applied, [[GMO Registry]] and [[Interlink Co. Ltd.]]. The later is a ISP and [[registrar]], while the former is a company formed to apply for new TLDs and provide TLD consultancy services.<ref>[http://domainincite.com/7936-four-companies-given-ok-for-osaka Four Comapnies Given Ok for Osaka]DomainIncite.com. Retrieved 15 November 2012</ref>

However, [[Interlink Co. Ltd.]] applied for community priority whereas [[GMO Registry]] did not. Beyond securing the Government's support, Interlink also recieved letters of support from organizations and companies around Osaka, which is itself a requisite of a community priority application.  "The Osaka community has been in existence for thousands of years, and is known as Japan’s oldest capital.  Osaka has been an economic and cultural center of the Japan for over a long span of time, though formally, the geographic area that defines the community, Osaka Prefecture, was formally established in 1868... The community is best defined by its geographic boundaries. The Osaka Prefecture is currently the 3rd most populous area in Japan with a community of over 8.8 million people." The applicant delineates the community along as including legal entities, citizens, governments and public sectors; it proposed creating a Domain Advisory Committee composed of members from each area in order to create, enforce, and oversee its registration policies.

However, [[Interlink Co. Ltd.]] applied for community priority whereas [[GMO Registry]] did not. Beyond securing the Government's support, Interlink also recieved letters of support from organizations and companies around Osaka, which is itself a requisite of a community priority application.  "The Osaka community has been in existence for thousands of years, and is known as Japan’s oldest capital.  Osaka has been an economic and cultural center of the Japan for over a long span of time, though formally, the geographic area that defines the community, Osaka Prefecture, was formally established in 1868... The community is best defined by its geographic boundaries. The Osaka Prefecture is currently the 3rd most populous area in Japan with a community of over 8.8 million people." The applicant delineates the community along as including legal entities, citizens, governments and public sectors; it proposed creating a Domain Advisory Committee composed of members from each area in order to create, enforce, and oversee its registration policies.

"All registrants of an “.osaka” name must satisfy at least one the following: Osaka municipalities and local governments; Public and private institutions in Osaka; Organizations, companies, and other businesses in Osaka; Residents of Osaka; Others community members who have a bona fide purpose for registering and using a “.osaka” domain. Registrants who purchase “.osaka” names will be required to certify that meet one of the categories above.  Meeting these requirements is on a continual basis, and therefore the registrant re-certifies compliance with the above during each subsequent renewal term.  In other words, registrants must ensure they remain in compliance with the Nexus Requirement."<ref>Application 1-901-9391. Retrieved 15 November 2012</ref>

"All registrants of an “.osaka” name must satisfy at least one the following: Osaka municipalities and local governments; Public and private institutions in Osaka; Organizations, companies, and other businesses in Osaka; Residents of Osaka; Others community members who have a bona fide purpose for registering and using a “.osaka” domain. Registrants who purchase “.osaka” names will be required to certify that meet one of the categories above.  Meeting these requirements is on a continual basis, and therefore the registrant re-certifies compliance with the above during each subsequent renewal term.  In other words, registrants must ensure they remain in compliance with the Nexus Requirement."<ref>Application 1-901-9391. Retrieved 15 November 2012</ref>

==Uncontested Community Applications==

==Uncontested Community Applications==