Service Modeling Language: Difference between revisions

Revision as of 09:21, 26 April 2008

Revision as of 19:39, 29 June 2008

Line 1:

'''Service Modeling Language''' '''(SML)''' is a pair of [[XML]]-based specifications by leading [[information technology]] companies that define a set of [[XML]] instance document extensions for expressing links between elements, a set of [[XML Schema_(W3C)|XML Schema]] extensions for constraining those links, and a way to associate [[Schematron]] rules with global element declarations, global complex type definitions, and/or model documents. The SML<ref>[http://www.w3.org/TR/sml/ Latest draft of the SML specification]</ref> [[specification]] defines model concepts, and the SML-IF<ref>[http://www.w3.org/TR/smlif/ Latest draft of the SML-IF specification]</ref> [[specification]] describes a packaging format for exchanging SML models.

{{Cleanup|date=August 2006}}

SML is currently underbeing reviewstandardized in a [[W3C]] working group chartered to produce W3C Recommendations for the Service Modeling Language by refining the “Service Modeling Language” (SML) Member Submission <ref>[http://www.w3.org/Submission/2007/01/ “Service Modeling Language” (SML) Member Submission]</ref>, addressing implementation experience and feedback foron the specifications. The submission was from an industry group consisting of representatives from BEA Systems, BMC, CA, Cisco, Dell, EMC, HP, IBM, Intel, Microsoft, and Sun Microsystems.

'''Service Modeling Language''' '''(SML)''' is an [[XML]]-based specification by leading [[information technology]] companies that defines a consistent way to express how computer networks, applications, servers and other IT resources are described or modeled so businesses can more easily manage the services that are built on these resources.

== Fast Formal Facts about SML ==

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.

The '''Service Modeling Language (SML)''' is a language for building a rich set of constructs for creating and constraining models of complex IT services and systems. TheseSML-based 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.

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 representatives from BEA, BMC, CA, Cisco, Dell, HP, IBM, Intel, Microsoft.

AAn SML model in SML is realized as a set of interrelated [[XML]] documents. TheAn [[XML]]SML documentsmodel could contain information about the parts of an IT service, as well as the constraints that each part must satisfy for the IT service to function properly. Constraints are captured in two ways:

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.

; [[XML Schema_(W3C)|XML Schema]] documents : constrain the structure and content of the XML instance documents in a model. SML uses [[XML Schema_(W3C)|XML Schema]] 1.0, but allows later versions as well. SML also defines a set of extensions to [[XML Schema_(W3C)|XML Schema]] to constrain references, and identity constraints (key, unique, ...) that apply to sets of documents.

== Fast Formal Facts about SML ==

; RulesRule documents : are [[Boolean expression]]s that constrain the structure and content of documents in a model. SML uses a profile of [[Schematron]] and [[XPath]] 1.0 for rules, but allows later versions as well.

Once a model is defined, one of the important operations on the model is to establish its validity. This involves checking whether all data in a model satisfiesdocuments satisfy the [[XML SchemaSchema_(W3C)|schemasXML Schema]] and rulesrule document declaredconstraints.

==SML-Based Models==

The '''Service Modeling Language (SML)''' is 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.

One anticipated use for SML is to define a consistent way to express how computer networks, applications, servers and other IT resources are described or modeled so businesses can more easily manage the services that are built on these resources <ref>[http://www.cml-project.org/2.html Common Model Library]</ref>. 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.

Models 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 19 ⟶ 24:

# Models enable increased automation of management tasks. Automation facilities exposed by the majority of IT services/systems today could be driven by software – not people – for reliable initial realization of a service/system as well as for ongoing lifecycle management.

==References==

A model in SML is realized as a set of interrelated [[XML]] documents. The [[XML]] documents contain information about the parts of an IT service, as well as the constraints that each part must satisfy for the IT service to function properly. Constraints are captured in two ways:

<div style="font-size: 85%"><references/></div>

; Schemas : these are constraints on the structure and content of the documents in a model. SML uses a profile of [[XML Schema]] 1.0 as the schema language. SML also defines a set of extensions to [[XML Schema]] to support inter-document references.

; Rules : are [[Boolean expression]]s that constrain the structure and content of documents in a model. SML uses a profile of [[Schematron]] and [[XPath]] 1.0 for rules.

Once a model is defined, one of the important operations on the model is to establish its validity. This involves checking whether all data in a model satisfies the [[XML Schema|schemas]] and rules declared.

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.w3.org/XML/SML W3C Service Modeling Language Working Group home page]

* [http://www.w3.org/XML/SML/#public_drafts W3C public working drafts of SML/SML-IF specification]

* [http://www.cml-project.org/2.html Common Model Library]

* [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