Definition

Web Standards Project (WaSP)

The Web Standards Project (WaSP) is a grass roots effort to encourage the main browser makers to create a standard implementation of the Hypertext Markup Language (HTML) and other Web standards and recommendations of the World Wide Consortium (W3C). WaSP maintains that the adoption of these standards by both manufacturers can reduce development time and budgets required for Web-based applications by up to 25%.

In spite of the existence of the W3C's recommendations almost since the beginning of Web browsers, both Microsoft's Internet Explorer and Netscape's Navigator have insisted on promoting and supporting non-standard extensions and in implementing existing recommendations differently, forcing public Web site developers to create different versions of their site, one for each browser (and often additional versions to accommodate changes in evolving browser versions).

For future versions of today's browsers, the WaSP is pushing for full support for W3C recommendations related to the Document Object Model (DOM), Cascading Style Sheets (CSS), and Extensible Markup Language (XML).

This was last updated in September 2005
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com
Back to top