Thanks
Joe,
Agree we need to use
our terms consistently and in-line with evolving industry use (figuring out and
agreeing on what that is may be the challenge)
I looked over the
Glossary of the Oasis-RM, there is good match but a bit of a theme difference in
that the Oasis document is very focused on “a service” where we tend to be more
focused on an architecture of a set of services in a community.
[JMC] Concur - that is expected at
this point in the SOA-RM TC's evolution as the reference model is not focused on
architecture; the reference architecture(s) that are in process will be focused
on this aspect. Having said that, those places below where you correctly point
out "not specified" for the SOA-RM spec will most likely be covered in the
reference architecture(s).
I would relate the
Oasis-RM terms to the terms in the document as
follows;
[JMC] Something for us to consider
might be to publish a mapping of these terms to the SOA-RM spec along with any
demo literature that we produce. This will also help facilitate adoption of
SOA-RM within the federal government and
elsewhere.
{SOA} Service
[Oasis-RM] The means by which the
needs of a consumer are brought together with the
capabilities
a provider. See Section 3.1.
[Demo] Corresponds to “Service
Interaction” in the document
[Suggestion] Ok with “service” but
would prefer a qualification to avoid confusion with the generic term and use in
the FEA. Perhaps we should use “SOA Service”.
[JMC] "SOA Service" sounds fine to
me.
{SOA} Service
Interface
[Oasis-RM] The means by which the
underlying capabilities of a service are accessed.
[Demo]
Same
{SOA} Capability
[Oasis-RM] A real-world effect
that a service provider is able to provide to a service
consumer.
[Suggestion] A real world effect
that an actor can provide to a community by playing a role in that
community
[JMC] Here are some thoughts
that were expressed within the SOA-RM TC, with which I tend to concur: While a service
is available to a community, we believe that the interaction is with a
specific consumer and not the community as an aggregate consumer.
Also, one can play a role in a community and have a real world effect
without ever interacting with an SOA service (the SOA-RM TC responder pointed
out that the e-mail that he sent me was such an example, the community being the
SOA-RM TC).
[JMC] End of
responses.
Thanks,
Joe
{SOA}
Role
[Oasis-RM] Not
Specified
[Suggestion] The responsibilities
and behavior of an actor in a community that is realized, in part, by providing
and/or using services. The role is specified in terms of responsibilities,
capabilities and interactions.
{SOA}
Community
[Suggestion] A collection of
actors that collectively realize business value by providing and/or using
services. The community is specified by the purpose of the community and
the roles various actors may play in realizing that purpose. Note that a
community can be very large or as small as 2
actors.
Other sources to be
considered;
[RM-ODP] The basic concepts of RM-ODP
Enterprise
language are object, role, community, objective,
behavior and action. An
object is a model of an entity, either an entity
of the system to be specified or
an entity of the system environment. Objects can be
grouped to form a
community. In that case, they exhibit the behavior needed to realize
the
objective of the community. By doing this, they
fulfill roles of the
community since a role identifies a behavior. This is a set
of actions
with
constraints on when they appear. Actions can be interactions
between
several objects or internal actions. Objects can
model people, organizations or systems.
Other comments on the Glossary
(not currently in demo, but may be)
Behavior
Model
[Oasis-RM] The characterization of
(and responses to, and temporal dependencies between)
the
actions on a service.
[Suggestion] The characterization
of (and responses to, and temporal dependencies between)
the
actions of an actor on or in
response to a set of services
From:
soa-forum-bounces@xxxxxxxxxxxxxx [mailto:soa-forum-bounces@xxxxxxxxxxxxxx]
On Behalf Of Chiusano
Joseph
Sent: Thursday, April
13, 2006 1:22 PM
To:
Service-Oriented Architecture CoP
Subject: [soa-forum] OASIS SOA-RM Committee
Draft
As discussed on our call today, I am
sending out this spec for our reference in terminology and other
areas.
Joseph
Chiusano
Associate
Booz Allen
Hamilton
700 13th St. NW, Suite
1100
Washington, DC 20005
O: 202-508-6514
C:
202-251-0731
Visit us online@ http://www.boozallen.com