Service Modeling Language: Difference between revisions

Revision as of 22:34, 13 April 2007

Revision as of 15:53, 5 April 2008

Line 5:

This enables a hierarchy of IT resource models to be created from reusable building blocks rather than requiring custom descriptions of every service, thus reducing costs and system complexity for customers.

SML is currently under review in a [[W3C]] working group chartered to produce W3C Recommendations for Service Modeling Language by refining the “Service Modeling Language” (SML) Member Submission, addressing implementation experience and feedback for the specifications. The submission was from an industry group consisting of representives from BEA, BMC, CA, Cisco, Dell, HP, IBM, Intel, Microsoft.

SML is currently proposed jointly by [[BEA Systems]], [[BMC Software]], [[Cisco Systems]], [[Dell]], [[EMC Corporation]], [[Hewlett Packard|HP]], [[IBM]], [[Intel]], [[Microsoft]] and [[Sun Microsystems]].

SML addresses a growing industry need as a result of the numerous methods of representing the same IT resource. Besides being inefficient, the use of different formats leads to two problems. First, because the tools and management applications use different formats, they don’t speak the same language. Therefore the information must be translated, which can lead to the loss or misinterpretation of technical details. Second, the use of different formats may require IT architects to use written descriptions or sketches to convey information about resources. Such descriptions must then be translated into a form that tools and management applications can consume, which is a manual, error-prone process.

Line 11:

== Fast Formal Facts about SML ==

The '''Service Modeling Language (SML)''' providesis a language for building a rich set of constructs for creating models of complex IT services and systems. These models typically could include information about configuration, deployment, monitoring, policy, health, capacity planning, target operating range, [[service level agreement]]s, and so on. Models could provide value in several important ways.

# Models focus on capturing all invariant aspects of a service/system that must be maintained for the service/system to be functional. They capture as much detail as is necessary, and no more.

Line 26:

The SML [[specification]] focuses primarily on defining the profile of [[XML Schema]] and [[Schematron]] used by SML, as well as the process of model validation.

In addition to SML itself, the SML project includes the SML Interchange Format (SML-IF), an XML document format that can be used to exchange complete or partial SML models across implementations.

==External links==

* [http://www.servicemlw3.org/XML/SML serviceml.org]W3C Service Modeling Language WorkWorking Group main sitehome page]

* [http://www.servicemlw3.org/XML/SML-200607.pdf/#public_drafts ServiceW3C Modelingpublic Languageworking Specification]drafts Specificationof draftSML/SML-IF for downloadspecification]

* [http://schemas.serviceml.org/sml/2006/07 Service Modeling Language Schema] SML Schema

* [http://basman.wordpress.com/2006/08/01/technology-leaders-release-new-specification-to-simplify-it-management/ Service Modeling Language (SML): New Specification to Simplify IT Management] The announcement of the planned standard in the wording of the official joint press text of the initiators and original quotes of their respective managers in charge