Open Services as Part of the ISM Platform
JohnArwe 120000CAW7 Visits (2423)
Pulse 2011 Day 1 General Session time talking about "radical simplification" of Tivoli products, and how this would be enabled by open standards and communities that IBM is already participating in, like Open Services for Lifecycle Collaboration (OSLC). For those who missed it, use the preceding Pulse link. If you have the time, listen to the full session; if you want to focus on the subject of this post, move the slider right to 48:00 and then play it; the run time is 5-6 minutes.
Danny also mentioned how we'd be moving toward a Web-centric model of open protocols and open data. For those with a technical bent, that translates (using OSLC as an example) into technologies like HTTP-based interfaces (what the industry widely calls REST or RESTful) offering XML and/or JSON representations with embedded links using Linked Data (RDF).
There are many important aspects of that direction, depending on one's interests. The most important one though is your involvement. Venues like Service Management Connect and the OSLC community site allow our clients to have direct interaction one another and with the people writing code -- take advantage of it! The surest way to ensure that your needs are met is to engage in the process of getting consensus on the scenarios and use cases that drive the development process. When work on open standards is beginning in a specific area (what OSLC calls a domain), we'll make an announcement here. Since there are some existing domains for change management (think defects and tickets), you (or someone responsible for that area) may want to monitor that site as well.