OASIS announces an initiative to standardize SCA as OCSA

Discussions

News: OASIS announces an initiative to standardize SCA as OCSA

  1. OASIS, the international standards consortium, has announced the formation of the Open Composite Services Architecture (Open CSA) Member Section, a new initiative to advance standards that simplify Service Oriented Architecture (SOA) application development. Open CSA will promote the further development and adoption of the Service Component Architecture (SCA) and Service Data Objects (SDO) families of specifications, which will be provided to the community on a Royalty Free basis. SCA helps organizations more easily design and transform IT assets into reusable services that can be rapidly assembled to meet changing business requirements. SDO lets application programmers uniformly access and manipulate data from heterogeneous sources, including relational databases, XML data sources, Web services, and enterprise information systems. Both SCA and SDO were created by the Open SOA Collaboration, an informal group of 18 software vendors. After successfully shepherding the specifications through their incubation phase, these vendors selected OASIS as the most effective venue for advancing SCA and SDO through the open standardization process. It's in the JCP, but the JCP effort has stalled. The Open CSA Member Section will oversee several new OASIS Technical Committees for the SCA and SDO families of specifications. Everyone is invited to participate in this work. Charters for these new Committees will be available in the coming weeks. Members of the Open CSA Member Section include Active Endpoints, Avaya, BEA Systems, Hitachi, IBM, Oracle, Primeton, Progress Software, Red Hat, Rogue Wave Software, SAP AG, SOA Software, Sun Microsystems, TIBCO, Xcalia, and others. Message was edited by: joeo@enigmastation.com
  2. My involvement in the SCA and SDO work has been a good experience. The vendor community has worked well together on this, and I think it is a good set of specs that fill an unmet need (the only other thing out there like SCA is Microsoft's WCF). Of course both SCA and SDO will mature more now that they are on their way to being official standards, but we have a good starting point for real implementations. SOA has needed a way to describe the high level architecture that includes existing technologies - from multiple programming languages and frameworks. I encourage you all to take a look and see what you think. Patrick Leonard Rogue Wave Software

  3. Both SCA and SDO were created by the Open SOA Collaboration, an informal group of 18 software vendors. After successfully shepherding the specifications through their incubation phase, these vendors selected OASIS as the most effective venue for advancing SCA and SDO through the open standardization process. It's in the JCP, but the JCP effort has stalled.
    There's some minor factual errors: SDO was in fact created by BEA and IBM as part of the JCP in 2003, long before the OSOA was created. The JCP effort is about to be restarted for the Java SDO API. PJ Murray CodeFutures Software Data Access Objects and Service Data Objects