BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Standardization Content on InfoQ

  • XACML finally ready for prime time?

    XACML, the eXtensible Access Control Markup Language, an Oasis standard approved more than 2 years ago, has been demonstrated to work cross vendor platforms on Burton's Catalyst Conference last week.

  • WSDL 2.0 approved as an official W3C Recommendation

    WSDL 2.0 has finally been approved as an official World Wide Web Consortium (W3C) recommendation on June 27 2007. The Web Services Description Working Group has been working on the standards for more than 6 years. The recommendation was due on the 31st of December 2006 but has received an extension to the 30th of June this year.

  • WS-BPEL4People on its way to OASIS

    A group of several vendors suggests a new WS-* spec that goes by the interesting name "WS-BPEL4People". Compared to WS-BPEL which deals with automated business processes, the WS-BPEL4People spec, which has been under works for nearly two years now, aims to add human workflow capabilities to SOA in general and to the recently approved WS-BPEL 2.0 spec specifically.

  • Java and .NET Libraries for Open XML

    With the new OpenXML format, there is the promise of an clean and efficient way to manipulate Office documents via XML. But with a 6000+ page spec, finding the exact nodes one needs to manipulate is a non-trivial task. To address this, OpenXML libraries for both Java and .NET are in the works.

  • OASIS WS-RM closes

    The OASIS WS-RM technical committee has closed. This groups work should not be confused with OASIS WS-RX which is still going forward.

  • WS-BPEL 2.0 Becomes an OASIS Standard

    After nearly four years, WS-BPEL 2.0, the Web Services business process execution language, has become an approved OASIS standard.

  • WS-Context becomes an OASIS standard

    WS-Context, part of the OASIS WS-CAF suite of specifications, becomes an OASIS standard. However, because of the overlap with the OASIS WS-TX effort, the other specifications are unlikely to become standards.

  • Controlling SOA development in OASIS?

    The Open CSA group is formed within OASIS to oversee the development of SCA/SDO. There's a steering committee, but only 3 of the 7 seats are open for vote: the rest are stacked by some of the original authors.

  • Opinion: Steve Jones's SOA Vendor Ratings

    Steve Jones has written a blog entry where assesses the main SOA vendors' offerings, including IBM, BEA, Oracle, SAP, Sun, and Microsoft, using a wide range of categories.

  • Presentation: Rob High on The SOA Component Model

    In an InfoQ presentation, IBM's SOA Foundation Chief Architect Rob High introduces Service Component Architecture (SCA) and Service Data Objects (SDO) as the foundation for a SOA programming model.

  • SCA/SDO go to OASIS

    The proprietary SCA and SDO specifications, often seen as competing with JEE and JBI, are taken to OASIS. With Sun now a member, is this a case of happy families?

  • Web Services Standards Overview Poster

    innoQ has released a new version of their Web Services Standards Overview poster, covering more than 60 specifications and standards.

  • Psst ... got a SOA Reference Model? Want another one?

    The Open Group starts work on another SOA Reference Model. But what is wrong with the existing OASIS model?

  • How .NET Handles Standards Compliance that Result in Breaking Changes

    Two security classes in .NET, HMACSHA512 and HMACSHA384, have a bug. It isn't an earth-shattering bug, but it does produce results that are inconsistent with the standard. The .NET Security team shows how this will be handed so that current applications won't break when the code gets fixed.

  • Interview with Sanjiva Weerawarana: Debunking REST/WS-* Myths

    InfoQ had a chance to talk to WS-* expert and WSO2 CEO Sanjiva Weerawarana, one of the fathers and a firm advocate of the WS-* architectural vision, we questioned him on the WS-* platform and his views on Microsoft's role in standardization. Sanjiva also took the opportunity to address "WS-* and REST myths".

BT