Service Modeling Language: Difference between revisions

Content deleted Content added
OatFarm (talk | contribs)
Brought up to date that the spec is now with the W3C, removed dangling links to defunct consortium site, added W3C links, added mention of SML-IF. Still needs much work. ~~~~
m Typo/date fixing , typos fixed: representives → representatives using AWB
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 representivesrepresentatives from BEA, BMC, CA, Cisco, Dell, HP, IBM, Intel, Microsoft.
 
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 30:
 
==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]