Content deleted Content added
Fixing header errors per the Manual of Style |
|||
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 proposed jointly by [[BEA Systems]], [[
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 32:
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.
== External
* [http://www.serviceml.org/ serviceml.org] Specification and scheme on the SML (Service Modeling Language) site
*
*
[[de:Service Modeling Language]]
|