Prescriptive Guidance for SOA Peter Roden Director of















- Slides: 15
Prescriptive Guidance for SOA Peter Roden Director of Technology Development OASIS
What is OASIS? • OASIS = Organization for the Advancement of Structured Information Standards • OASIS has been developing e-Standards since 1993 • OASIS is a member-led, international non-profit standards consortium concentrating on structured information and global e-business standards. • Close to 5000 members and 500 organizations • Supports over 60 technical committees producing royalty-free and RAND standards in an open process. “The largest standards group for electronic commerce on the Web”
OASIS Member Distribution 50% Technology Providers • Software vendors • Industry organisations • Individuals / small developers 15% Government & Academic • Governments • Universities • Research centres & related nonprofits 35% Users and influencers • User companies • Vertical industry organisations • Individuals / small consultancies
OASIS Membership Expanding Globally
Functional Categories to Track Standards Work ORCHESTRATION & MANAGEMENT SECURITY & ACCESS MESSAGING SOA DATA CONTENT DESCRIPTION DISCOVERY COMMON MESSAGE (XML) COMMON TRANSPORT
OASIS Technical Standards ASAP, BTP, eb. XML-BP, WSBPEL, WSCAF CIQ, CGM, Doc. Book, Open. Document, UBL ORCHESTRATION & MANAGEMENT DATA CONTENT DCML (x 3), WSDM, WSRF, WS-Notification SPML, XACML, (DSML) AVDL, e. GOV, Election, e. Proc, Emergency, Legal XML, Materials, PLCS, PPS, Tax. ML, Trans. Ws, WAS, XLIFF, (Auto Repair) ABCM, (Conformance), eb. SOA, FWSI, SOA Blueprints, SOA-RM SECURITY & ACCESS SOA DESCRIPTION eb. XML CPPA, Human. ML, UIML, WSRP DSS, PKI, SAML, WS -Security, XCBF DITA, Entity. Res, Topic Maps, Pub. Subj, XDI, XRI MESSAGING eb. XML MSG, eb. XML IIC, WS-Reliability, WS-RX DISCOVERY COMMON MESSAGE (XML) COMMON TRANSPORT eb. XML, Reg. Rep, UDDI Relax NG, XSLT Conformance
Technical trends in OASIS work ORCHESTRATION & MANAGEMENT SECURITY & ACCESS MESSAGING SOA DATA CONTENT DESCRIPTION DISCOVERY COMMON MESSAGE (XML) COMMON TRANSPORT • Infrastructure work is maturing • The action is moving up the "stack" to content and semantics • Stronger emphasis on service orientation: interoperability and reuse • End users are providing more of the content
Prescriptive: “to lay down as a guide, direction, or rule of action”
Business Centric Methodology TC 1. BCM templates for the Repository 2. Information architecture 3. Connections
SOA Blueprints TC • Methodology – “Open-Source” RFP • Built around Generico • Donation from Cap. Gemini for defining Business Requirements • Donation from Wells. Fargo – “Open-Source” POC • Vendor-Neutral source of information and benchmarks – Best Practices & Patterns • http: //dev. bea. com/technologies/soa/blueprint. jsp • Reference implementations from BEA, Microsoft, Oracle, Sun
SOA Blueprint Goals • Part of a long term project, SOA Blueprints aims to: – – – Define a baseline standardized set of enterprise applications Focus on SOA principles Highlight SOA design patterns and best practices Encourage SOA adoption Be industry agnostic Be applicable to as many organizations as possible • The specification will lead to: – – An agreement on SOA terminology A reference open source implementation An implementation by vendors Additional modules with particular industry focus
SOA Blueprints Implementation Environments • Definition of services independent of implementation, location or use • Implementation and hosting of services as a provider • Location and usage of services as a consumer • Assembly of services from other services and business rules • Support for synchronous, asynchronous and conversational services • Orchestration of application presentation built on services and rules • Automated data transformation between disparate data structures • Provisioning of local and remote services • Support for simulating, testing and debugging of services
More OASIS SOA Prescriptive Work • eb. SOA – Update the eb. XML Architecture in an SOA context • Framework for WS Implementation – design a template for Web services deployment to enable systems integrators, software vendors, and in-house developers to build e-commerce solutions more quickly • SOA Reference Model – define a reference model for Service Oriented Architecture • Semantic Execution Environment – guidelines, justifications and implementation directions for an execution environment for Semantic Web services
End-User Company Benefits • Influence direction and priorities of standards development by aligning your strategic requirements with the standards • Learn and adopt best practices • Improve Vendor and Partner selection through a better understanding of why they are choosing their implementation and product directions • Shift training expenses to standards participation to better educate technical staff on trends and developments of technology • Observe practical implementations from multiple vendors for given business scenarios • Speed up your implementations by participating in multivendor interoperability demonstrations with your specific use cases
Peter Roden Director of Technology Development OASIS 630 Boston Road Billerica, MA 01821 USA +1 978 667 5115 Ext. 210 (Voice) +1 978 761 1648 (Mobile) +1 978 667 5114 (Fax) Peter. Roden@oasis-open. org















