??™) to extend their name description. For example:
The generic FQSN template is straightforward:
source/structure/context
An expanded FQSN template looks like this:
source.subsource/structure.substructure/context.subcontext
A few examples below:
To describe services, it is not necessary to use their FQSN structure. Simply use one of
the typing groups to identify a particular service. This general description style, however, is not
recommended when a more descriptive service type is required. For example: atomic or composite
can be used to type a service.
The following FQSN rudimentary example depicts a legacy origin (source), identified as
a composite entity (structure), and is defined as business type (context).
Legacy/composite/business
To denote subcategories in service typing namespace hierarchies, use a dot (???.??™) to delineate
each descending level. The next example describes a legacy service (source), identified as atomic
(structure), which is business affiliated (context). ???Claims??? is the name of the organization??™s
division, ???autos??? is the name of the claims??™ subdivision, and ???registration service??? is the name
of the service.
legacy/atomic/business.claims.autos.registration service
The following example, defines the business loan verification service (context), which is
identified as a process abstraction (source), and consists of cluster-related services (structure).
Pages:
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238