. Middleware software could create and modify the services, and CPL would be
the back-end for their execution. Here, a CPL service could then be a
component for other services.
5.1.2 Why Create a DSM Solution for CPL?
The underlying objective for creating a DSM solution was to allow services to quickly
and reliably speci?¬?ed and generated to be executed in a CPL server. TheDSMlanguage
was not targeting end users as their service needs were considered to be solved better
by choosing prede?¬?ned services. The target users of the language were thus service
providers and administrators. The actual service speci?¬?cation for the server is speci?¬?ed
in XML. The de?¬?nition of the language for de?¬?ning services was available as an XML
schema (Lennox et al., 2004)??”a common starting point for de?¬?ning modeling
languages. It is not a bad starting point as many domain concepts are already identi?¬?ed.
However, and as Lennox et al. also acknowledge,XMLschemas alone are not adequate
to specify correctness of speci?¬?cations made with the language.
INTRODUCTION AND OBJECTIVES 99
5.2 DEVELOPMENT PROCESS
Development of the language started from the interest of one company to ?¬?nd an easy
way to specify CPL services. Writing the services in handwritten XML was
considered dif?¬?cult, error-prone, and as easily leading to internally inconsistent
speci?¬?cations.
Pages:
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208