On July 31, 10 IT vendors published the Service Modeling Language specification to improve the automation of management systems. SML provides a consistent way to describe system information about networks, applications, servers and other IT resources. The authors plan to submit SML to a yet-to-be-chosen standards body by the end of 2006.
SML provides rich support for capturing constraints that are part of the model (for example, the fact that a certain operating system runs on only a certain type of CPU) and excellent alignment with an existing Web services infrastructure. These features increase its ability to automate management tasks.
The language is well aligned with XML. Unlike object-oriented models that need to go through unnatural transformations to be represented in XML, an SML model is defined natively in XML. Better yet, SML uses XML Schema Definition (XSD), minus a few of XSD's quirks, as its syntax constraint language. Because XML and XSD are the foundation of the Web services architecture, SML models fit very well within this infrastructure. This fit gives SML users easy access to the transformation, messaging, reliability, transactionality and security infrastructure built around XML document exchange, along with rich metadata support.
The primary goal of SML is to increase the level of automation in IT systems management. SML takes automation one step further than previous modeling languages by offering powerful support for constraints with Schematron, a language to describe conditions that XML documents must respect. To unlock its power, SML defines a few extensions that allow constraints to span several documents. For example, the sml:ref type represents references between documents. In addition, SML adds a deref( ) function extension to XPath to let these references be navigated inside XPath expressions. These references can be constrained further to not create cycles in a model (sml:acyclic) and to target specific elements (sml:target Element) or elements of a specific type (sml:TargetType).
An SML model is a set of XML documents, some of which (called genic documents) have the special status that they contain constraints on other documents. Nongenic documents are called phenic documents. The constraints contained in genic documents can apply to both genic and phenic documents. The only action defined by SML is the validation of a model.
Partner Content
NetScout and analyst Jim Metzler have teamed to deliver a series of IT Briefs on Network and Application Performance Management leveraging research from NetScout's nGenius & Sniffer users.
www.netscout.com
Metzler on Service Delivery Management
Delivering IT business value by evolving our thinking from managing application performance to focusing on services.
Learn More
2009 Handbook of Application Delivery
Successful IT organizations must know how to make the right application delivery decisions in these tough economic times.
Download the Handbook
Metzler on the Modern IP Network
Discusses the growing emphasis on network management and the need to implement a holistic view of the end-to-end experience of the user.
Read the Brief