Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Web Standards Project

From Wikipedia, the free encyclopedia
Campaign for adoption of W3C web standards
"WaSP" redirects here. For other uses, seeWasp (disambiguation).
Web Standards Project
Company typeProject
IndustryInformation technology
Founded1998; 28 years ago (1998)
FounderGeorge Olsen
Defunct2013
FateDissolution
Key people
Jeffrey Zeldman,Tim Bray,Glenn Davis, Steven Champeon,Eric Meyer,Tantek Çelik,Matt Mullenweg,Molly Holzschlag,Simon Willison,[1]Dave Shea,Christopher Schmitt
Websitewww.webstandards.org

TheWeb Standards Project (WaSP) was a group of professional web developers dedicated to disseminating and encouraging the use of theweb standards recommended by theWorld Wide Web Consortium, along with other groups and standards bodies, with a primary focus on web clients (web browsers).

Founded in 1998, The Web Standards Project campaigned for standards that reduced the cost and complexity of development while increasing theaccessibility and long-term viability of any document published on the Web. WaSP worked with browser companies, authoring tool makers, and peers to encourage them to use these standards, since they "are carefully designed to deliver the greatest benefits to the greatest number of web users".[2] The group dissolved in 2013.

Organization

[edit]

The Web Standards Project began as agrassroots coalition "fighting for standards in our [web] browsers" founded by George Olsen,Glenn Davis, andJeffrey Zeldman in August 1998.[3] By 2001, the group had achieved its primary goal of persuadingMicrosoft,Netscape,Opera, and other browser makers to accurately and completely supportHTML 4.01/XHTML 1.0,CSS1, andECMAScript. Had browser makers not been persuaded to do so, the Web would likely have fractured into pockets of incompatible content, with various websites available only to people who possessed the right browser. In addition to streamlining web development and significantly lowering its cost, support for common web standards enabled the development of the semantic web. By marking up content in semantic (X)HTML, front-end developers make a site's content more available to search engines, more accessible to people with disabilities, and more available to the world beyond the desktop (e.g. mobile).

The project re-launched in June 2002 with new members, a redesigned website, new site features, and a redefined mission focused on developer education and standards compliance in authoring tools as well as browsers.[4]

Project leaders were:

  • George Olsen (1998—1999)
  • Jeffrey Zeldman (1999—2002)
  • Steven Champeon (2002—2004)
  • Molly Holzschlag (2004—2006)
  • Kimberly Blessing and Drew McLellan (2006—2008)
  • Derek Featherstone, Aaron Gustafson, and Glenda Sims (2008—2013)

There were members that were invited to work on ad hoc initiatives, theBuzz Blog and other content areas of the site.

The group announced its dissolution on March 1, 2013.[5]

Task forces

[edit]

The Web Standards Project hosted projects focused on bringing relevant organizations closer to standards-compliance, dubbed Task Forces.

Adobe Task Force
Focused on improving web standards compliance in products fromAdobe Systems. Was named theDreamweaver Task Force until 2008-03-10.[6]
Education Task Force
Worked with institutions of highereducation to promote instruction of Web standards and standards-compliant public sites.
Microsoft Task Force
Worked with theInternet Explorer and Web platform tools team.
Accessibility Task Force
Worked with organizations, vendors and others to promote Web accessibility.
International Liaison Group
A member was "an active advocate for Web standards and best practices either in theircountry of origin or domicile."[7]
The Street Team
Organized community events to promote web standards.
DOM Scripting Task Force
Focused on interoperableclient-side scripting, through explaining and promoting theDOM standards from W3C and theECMAScript Standard, and concepts likeprogressive enhancement,graceful degradation,accessibility, standards-drivenJavaScript.[8] These best practice approaches have been called "DOM scripting" to differentiate them from earlier perceived bad uses of "Dynamic HTML". The task force became inactive before the group disbanded.

Activities

[edit]
  • TheAcid1 test allows browsers and other rendering engines to test compliance with HTML 4 and CSS 1 specifications.
  • TheAcid2 test allows browsers and other rendering engines to test compliance withCSS 1 and 2 specifications.
  • TheAcid3 test allows browsers and other rendering engines to test compliance with CSS 2.1,DOM, andEcmaScript specifications.
  • TheWeb Compatibility Test for Mobile Browsers allows mobile browsers and other rendering engines to test for web page rendering issues.

Browse Happy

[edit]

Browse Happy is awebsite urging users to upgrade theirweb browsers. The site was initially created by the Web Standards Project in August 2004 to convince users to switch to a web browser other thanMicrosoft'sInternet Explorer.[9] It focused onsecurity issues in Internet Explorer and suggested four alternatives:Mozilla Firefox,Opera,Safari andGoogle Chrome. The core of the site was a collection of testimonials by people who had switched from Internet Explorer to alternative web browsers.[10]

In June 2005, the Web Standards Project decided that an anti-Internet Explorer campaign did not fit with their mission, and they handed the site over toMatt Mullenweg.[11] Since then, the site has been maintained byWordPress.com[12] with collaboration fromHTML5 Boilerplate team members.

See also

[edit]

References

[edit]
  1. ^Cederholm, Dan (2004-06-10).Web Standards Solutions: The Markup and Style Handbook. Berkeley: Apress. p. 236.ISBN 978-1-59059-381-3.
  2. ^"WaSP: Fighting for Standards (WaSP mission statement)". Web Standards Project. 2006. Retrieved2008-03-10.
  3. ^Sliwa, Carol (1998-08-17). "Browser standards targeted".Computerworld. Vol. 32, no. 33. p. 76.ISSN 0010-4841.
  4. ^Pruitt, Scarlet (2002-06-12). "Web Standards Project aims to educate developers".InfoWorld.
  5. ^Gustafson, Aaron (2013-03-01)."Our Work Here is Done".The Web Standards Project. Retrieved2019-04-09.
  6. ^Announcing the Adobe Task Force - The Web Standards Project
  7. ^"ILG Members - The Web Standards Project".webstandards.org.
  8. ^"Manifesto - The Web Standards Project".webstandards.org.
  9. ^Festa, Paul (2004-08-24)."Browser campaign slams IE".CNET News. Archived fromthe original on 2008-10-07. Retrieved2019-03-22.
  10. ^heise - "Glücklich browsen" ohne Internet Explorer - Staff Writer - 25.08.2004[1]
  11. ^Holzschlag, Molly E. (1 June 2005)."BrowseHappy Now Part of WordPress as WaSP Refocuses Mission".Web Standards Project.Archived from the original on 2005-06-03. Retrieved2025-04-17.
  12. ^"Browse Happy".GitHub. 7 September 2021.

External links

[edit]
Features, standards & protocols
Features
Web standards
Protocols
Active
Blink-based
Proprietary
FOSS
Gecko-based
Goanna-based
WebKit-based
Multi-engine
Other
Discontinued
Blink-based
Gecko-based
MSHTML-based
WebKit-based
Other
Retrieved from "https://en.wikipedia.org/w/index.php?title=Web_Standards_Project&oldid=1311390533"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp