The starting point
for the language could thus be based on already established domain-speci?¬?c concepts.
The names used by the XML schema were followed exactly as this made the task of
the generators easier. The naming needed for the generated output could be used
straightforwardly in the modeling language. Thus the generator could be simpler and
there would be no need to translate the names of the modeling concepts to those
needed in XML. Later, during generator implementation, this was discovered to not
be fully true as legal naming in XML required some string manipulation (see Section
11); for example, spaces are not allowed in the as names and special characters given
in the model can be treated as XML tags.
Often, the speci?¬?cation, service examples, and XML schema used different names
for the same domain concepts, such as ???signaling actions??? and ???signaling operations???
that both mean the same thing. This is a typical situation when the language is not
formally de?¬?ned and there is no reference implementation. Thus, creators of a DSM
solution need to make choices and have a major in?¬‚uence on naming policies and
establishing a vocabulary.
LANGUAGE FOR MODELING CALL PROCESSING SERVICES 101
5.3.1 Modeling Concepts
The modeling language was constructed based on a ?¬‚ow model, with a special root
element to start the script.
Pages:
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212