Service Modeling Language: Difference between revisions

Revision as of 23:50, 13 January 2013

Latest revision as of 23:06, 6 February 2024

(5 intermediate revisions by 4 users not shown)

Line 1:

{{Multiple issues|

'''Service Modeling Language''' '''(SML)''' and '''Service Modeling Language Interchange Format''' '''(SML-IF)''' are a pair of [[XML]]-based specifications created 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/sml-if/ Latest draft of the SML-IF specification]</ref> [[specification]] describes a packaging format for exchanging SML-based models.

{{Advert|date=February 2024}}

{{Tone|date=February 2024}}

{{Primary sources|date=February 2024}}

}}

'''Service Modeling Language''' ('''(SML)''') and '''Service Modeling Language Interchange Format''' ('''(SML-IF)''') are a pair of [[XML]]-based specifications created 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/sml-if/ Latest draft of the SML-IF specification]</ref> [[specification]] describes a packaging format for exchanging SML-based models.

SML and SML-IF were standardized 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 on 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. They were published as [[W3C Recommendation]]s on May 12, 2009.<ref>[http://www.w3.org/2009/04/sml-pressrelease.html.en SML and SML-IF Recommendation Press Release]</ref> In the market and in applying by vendors,{{whom|date=February 2024}} SML is seen as a successor/replacement for earlier developed standards like [[DCML (markup language)|DCML]] and Microsoft's (in hindsight) proprietary System Definition Model or SDM. See <ref>http://download.microsoft.com/documents/uk/msdn/architecture/infrastructure/infrastructure_and_business_priorities.ppt Powerpoint relating SDM and DCML</ref> for a historically helpful relation between SDM and DCML, and <ref>http://www.hp.com/hpinfo/newsroom/press/2006/060731b.html?jumpid=reg_R1002_USEN Joint press release about SML</ref> for the joint pressrelease announcing SML. In the Microsoft section of it the sequel role to SDM is mentioned.

== Fast Formal Facts about SML ==

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. SML-based models could include information about configuration, deployment, monitoring, policy, health, capacity planning, target operating range, [[service level agreement]]s, and so on.

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. SML-based models could include information about configuration, deployment, monitoring, policy, health, capacity planning, target operating range, [[service level agreement]]s, and so on.

An SML model is a set of interrelated [[XML]] documents. An SML model 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:

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

;* Rule documents : constrain the structure and content of documents in a model. SML uses [[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 model documents satisfy the [[XML Schema (W3C)|XML Schema]] and rule document constraints.

==SML-Based Models==

Models provide value in several important ways:<ref>[http://www.cml-project.org/2.html Common Model Library - link no longer resolves] {{webarchive|url=https://web.archive.org/web/20080622143643/http://www.cml-project.org/2.html |date=2008-06-22 }}</ref>

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 - link no longer resolves]</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 25 ⟶ 27:

==References==

{{Reflist}}

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

==External links==

Line 32 ⟶ 34:

[[Category:XML markup languages]]

[[de:Service Modeling Language]]