While inspecting the organization??™s operating environments and profiling the enterprise??™s
existing assets, practitioners may often find some implementations that do not maintain a
clear delineation between business and technical contributions, meaning they are tightly coupled.
These assets offer hybrid business and technical solutions. Consequently, there may be numerous
service-oriented software assets that do not fall into either the business or the technical category.
124 Ch. 6 Service-Oriented Typing and Profiling Model
Obviously, this is still a common practice with today??™s design and architecture disciplines. In
a perfect world, however, it should be feasible to decompose these entities, to deliver a more
agile operating environment for the organization. Therefore, when these crossbred service-oriented
assets are being categorized, their business and technical contribution ratios should be carefully
inspected to ensure a proper typing judgment.
SERVICE TYPING NAMESPACES
The recommended general structure for expressing service types is akin to the XML namespaces.
These declarations are named service typing namespaces. The fully qualified service name (FQSN)
always requires the previously discussed typing groups: source, structure, and context. For presentation
purposes, these groups should be delimited by forward slashes (???/??™). In addition, to expand
a group into subcategories, use the dot (???.
Pages:
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237