SOA & Web Services
Services are shared process resources. Like all resources, SOA services have qualities and relations that define them. RQ
specifications are important to SOA and SOA is the current major trend. Still, RQ specifications exceed the sole domain of
SOA to reach most resources.
Crucial to SOA, RQs and governance (e.g. Enterprise Architecture) also require execution at all resource levels, with attributes
and roles that affect business and processes.
Generalized RQ specifications for resource and RQs provide better integration, and less incompatible specifications, as may
not be the case if there was a RQ standard for SOA, one for QoS, one for KPIs, one for ... Major contributor to the specification,
SOA also defines and manages its Web Services implementations.
Whether at the Web Service level or other resource levels, both RQs and governance are required. Both RQs and governance also
require resource recursion support to provide the required granularity, as they are resource level constructs.
It is in resource modeling, also inherited by its specializations and applications, like EA, BA, BPM, VCM, that RQs and governance
are defined and implemented. Like all resources, SOA services require RQs for governance, strongly and rightly so.
Most SOA RQ (e.g. service quality) challenges come mostly from issues related tomatchingservice offerings in servicenegotiations. The proposed RQSemanticsMatching and RQ Negotiation could offer a starting point and direction.