Web Services Need W3C

Escrito por
Eric Newcomer
Eric Newcomer
Published: Aug 16, 2004
Updated: Feb 2, 2021
3 minute read
eWeek mantém conteúdo e recomendações de produtos editorialmente independentes. Podemos ganhar dinheiro quando você clica em links de nossos parceiros. Saiba mais

As Web services standards evolve, those of us involved in their development and adoption are at a crossroads. We strive for open standards, unencumbered by patents and intellectual property rights. We want to compete not in the development of the standards but in how we use them in our products.

Our model for the successful use of standards is the World Wide Web. Tim Berners-Lee, director of the World Wide Web Consortium, was recently recognized with The Finnish Technology Award Foundations Millennium Technology Prize and a British knighthood for inventing the Web. Prominent recognition was given to his choice not to claim patents on his invention. His decision freed everyone to use Web standards easily and cheaply over the Internet to share information, educate, communicate and conduct commerce.

Under Sir Tims leadership, the W3C remains responsible for ensuring the Webs future. The W3C believes that standards should remain as free of patent and IP restrictions as possible and restricts adoption of specifications encumbered by patents.

/zimages/6/28571.gifClick here to read about the W3Cs patent advisory group.

At the advent of Web services, Iona and other vendors submitted the SOAP and WSDL specifications to the W3C, hoping to make them as open and widely adopted as the Web. We believed the W3C was the natural body to lead Web services and produce the specifications that would drive the adoption of this significant new technology.

Unfortunately, after the initial broad support and the success of SOAP and WSDL, the Web services standardization effort started to split. The W3C enacted a stricter IP policy, and many companies believed that the new policy did not sufficiently protect their contributions.

Perhaps because of this disagreement, no single standards body has been able to duplicate for Web services what the W3C did for the Web. Various organizations each control significant Web services standards (for example, OASIS, W3C, WS-I, OMG), and new specifications continue to be created by private consortia. But challenging IP issues remain. They range from public workshops, at which participants must sign over the IP rights of their contributions to the sponsoring companies, to specifications with licensing terms that are often unclear or undisclosed. I cant see any company being willing to contribute to a standard when theres a real prospect that theyd then owe license fees for its use.

Advertisement

Ideally, the industry should unconditionally commit to adopting standards unencumbered by IP rights and agree to vie for the best implementation of a specification, instead of worrying about license fees. However, since a large portion of the industry continues to be concerned about licensing, we need the W3C to find a compromise position, doing for Web services what it did for the Web, perhaps recognizing that an entirely patent-free approach isnt always going to work.

Eric Newcomer is chief technology officer of Iona Technologies plc. Free Spectrum is a forum for the IT community. Send submissions to free_spectrum@ziffdavis.com.

/zimages/6/28571.gifCheck out eWEEK.coms Developer & Web Services Center at http://developer.eweek.com for the latest news, reviews and analysis in programming environments and developer tools.

/zimages/6/77042.gif

Be sure to add our eWEEK.com developer and Web services news feed to your RSS newsreader or My Yahoo page

Eric Newcomer

Eric Newcomer is CTO of WSO2. He has more than 35 years of industry experience spanning a variety of senior architecture roles in various tech companies. In his current role, Eric is responsible for driving WSO2’s technical vision and helping to promote the adoption of products and projects, with a focus on enterprise customers. Before WSO2, he held senior architecture roles at Credit Suisse and Citibank in New York, where he focused on introducing new technologies and best practices, including open source, big data, microservices, and Docker/Kubernetes. Before that, he was CTO at IONA Technologies from 2002 until its acquisition by Progress Software in 2008. Prior to IONA Technologies, Eric was a Distinguished Engineer at Digital Equipment Corporation (now part of HP), specializing in database and transaction processing.

eWeek Logo

eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site's focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

Propriedade da TechnologyAdvice. © 2026 TechnologyAdvice. Todos os direitos reservados

Divulgação de anunciantes: alguns dos produtos que aparecem neste site são de empresas das quais a TechnologyAdvice recebe remuneração. Essa remuneração pode influenciar como e onde os produtos aparecem neste site, incluindo, por exemplo, a ordem em que aparecem. A TechnologyAdvice não inclui todas as empresas nem todos os tipos de produtos disponíveis no mercado.