Transcript: New from BookNet Canada for 2024: BNC BiblioShare - Tech Forum 2024
Enterprise Linked Data, Open Services for Lifecycle Collaboration, and W3C Standards
1. Enterprise Linked Data, Open Services for
Lifecycle Collaboration, and the W3C Standards
Angel Luis Diaz, VP Software Standards, IBM Software Group
Steve Speicher, STSM and OSLC Chief Architect, IBM Rational
Session LS-1439
IBM IOD 2011 05/07/12 Prensenter name here.ppt 05/07/12 15:16
To help our clients navigate this complex environment, IBM has developed a smarter approach to standards development. First, cloud standards must be innovative in that we must carefully think about invention versus reinvention, new standard or reuse of an existing standard. Some competitors believe in the development of new standards regardless of the context, but IBM strives to reuse and extend existing standards where and when possible. Second, standards must be practical. Gone are the days of paper based technical specifications - today’s standards need to leverage real world implementations and open source code and today’s standards should be proven in practice through implementation, not based strictly on theory. For this reason, IBM works closely with open source communities to implement standards during the development phase in order to test and “prove” their value. Third, cloud standards should be set in the context of a standard architecture, allowing enterprises to manage change across market evolution cycles and extending the value of clients’ services based architectures and investments. Towards this goal, IBM has contributed the Cloud Computing Reference Architecture to The Open Group as the basis of an industry wide Cloud architecture. Finally and most importantly, cloud standards should be user-driven, based on real world client pain points. This is why IBM founded the Cloud Standards Customer Council, to create a cross-industry client based view of market-leading Cloud use cases and best practices. IBM’s Smarter Approach to Standards Development results in Cloud standards which are interoperable, flexible and customer driven. 135
18 customers participated in an onsite survey Almost all are managing 3 or more lifecycle tool vendors Almost 90% of customers are dealing with in-house developed lifecycle tools Majority are selective where they invest to integrate heterogeneous tools, but almost all would do more if it was easier and more cost-effective Vast majority supplement vendor-provided integrations with in-house development/integration effort Most define CCM, QM, RM, and ADC disciplines as core to their integration needs 1/2 depend heavily on integrating across breadth of “ Decide-Develop-Deploy ” The other 1/2 would integrate more broadly if there was a more effective way
Points: At the core is a set of Statements (aka facts) We can look up info about Steve to learn more about him, like facts about resources (Angel) that we already know.
Points: At the core is a set of Statements (aka facts) We can look up info about Steve to learn more about him, like facts about resources (Angel) that we already know.
OSLC is an open community of vendors, integrators, and users, that creates freely-available, scenario-driven, specifications for integrating software applications. Though OSLC’s initial focus for specification were ALM domains, the techniques used are universally applicable , and are already being applied in workgroups focused on PLM ( with leadership from Siemens ), and DevOps ( with leadership from IBM Tivoli ). (Optional for more technical presentations: All the specifications are based on the standard, and proven, architecture of the web: HTTP, REST, and Linked Data. This means integrations don’t have to copy and synchronize data, but can link to it where it “lives”. Wherever the data is, OSLC-based integrations let users work with data from their current context. ) Whether you want to work on the details of the specifications, get the community to focus on scenarios that are important to you, or use finalized OSLC specifications to integrate your own software, the OSLC community is open to you . (Links on this chart: open-services.net open-services.net/members open-services.net/participate )
Green == Existing capabilities Orange == New capabilities Dashed border and Italics == No OSLC provider specification but is aspirational
Initial code contributions live in September 2011 Reference Implementations for OSLC (RIOs) for the Change, Requirement and Architecture Management specifications. Provides samples of implementations Enable prototyping and experimentation during spec development Possible starting point for integration adapters or new service providers Co-developed with the OSLC test suite to improve both OSLC Test Suite and Reports Measure implementation compliance against Core and domain specifications Improve implementation quality by finding bugs Currently covers core and CM. Other domains will follow Initial focus is on MUST items, followed by SHOULD and MAY Reports provide both summary and detailed results Samples Change Management adapter for Bugzilla Change Management adapter for Microsoft Excel
Author Note: Optional Rational slide. Graphic is available in English only.
IBM IOD 2011 05/07/12 Prensenter name here.ppt 05/07/12 15:16
The Eclipse Lyo (pronounced “Leo”) project is providing the necessary infrastructure for all implementers to be successful . The test suites help implementers assess their implementation’s fidelity to the OSLC specifications, and play a critical role in the effort to bring predictability to integrations , they are an essential tool to help make the any provider to any consumer goal of OSLC a reality. Lyo is not just for Java or Eclipse users, OSLC’s Linked Lifecycle Data approach means that implementations can be created in any language with a library for HTTP (all of them!). OSLC is technology-neutral and that is Lyo’s goal too. All implementers, regardless of technology choice, can benefit from the test suite and reference implementations. Having built on top of the architecture of the web, the OSLC community is contributing some of its core innovations back to W3C for standardization , and moving forward to address new challenges in ALM, PLM, DevOps, and beyond. (Links: http://eclipse.org/lyo http://www.w3.org/Submission/2012/02/ )
Green == Existing capabilities Orange == New capabilities Dashed border and Italics == No OSLC provider specification but is aspirational