Data
Junction systems are often used in conversion efforts. This probably
refers to the kind of mapping one might do given say, two different
vocabularies
for
the same ontogical types, so effectively, what one can do with XSLT if
it were datatype aware.
Think of the countless Indian dialects as the backend server system
languages,
and
a mapper as a transformer conversant with the subtleties of not
only
the phonemic structures of each, but also the shades of meaning.
This
is only the beginning of the issues. Consider the complexities of
the
court processes and ask how a case that spans several states
could be tried fairly and judiciously. That is kind of
challenge a
web
service might be posed to solve, but will be quite difficult to
meet.
len
Would anybody
like to comment on the following Para from the same PDF
I could not
understand it properly
"In order to enable application
integration
today's businesses require a very
nimble and
powerful integration engine that
can rapidly
and reliably connect one
application to any
other SOAP-enabled (or
non-SOAP-enabled)
program or application. Many of
today's businesses
also need a powerful engine that
has a
small footprint and doesn't
dominate the
business' server. But an engine's
nimbleness
and efficiency should not
sacrifice much needed
mapping functionality - Web
services
demand robust mapping
capabilities"
