As a fellow member of the OASIS SOA-RM TC with Ken, I also suggest
having a look at the Reference Model, and keep in mind that we are
moving on to developing a somewhat more concrete but still highly
abstract reference architecture capable of supporting multiple models
for specific reference architectures. Since I also work with a
collaboratory that is developing an ongoing Semantic Interoperabiity
Architecture pilot which embodies a Service-Oriented Architecture
and, hence, a reference architecture instance demonstrating
aggregated web services in the emergency management and health
informatics domains, I can attest that the scope of our work in this
reference model is suitable for inter and intra enterprise
application of SOA principles. I think it is the applicability of
these principles, rather than specific architectural styles, which
makes the SOA conceptual framework compelling. (01)
Having worked with these concepts for a while now, I am a bit
concerned that the marketing engines of the major players in this
arena are primed to spread a lot of smoke around, so anywhere we can
achieve clarity without having our crispness tied to a specific, let
alone proprietary technology, whether that is an endorsement of an
architectural style such as WSDL & SOAP-based web services versus
REST and AJAX or a focus within or outside the organizational
boundaries, I think we better serve ourselves and the marketplace. (02)
Cheers,
Rex (03)
At 1:03 AM -0400 5/6/06, Ken Laskey wrote:
>Any interesting thread and certainly one that has occurred in
>numerous places at numerous times. Again, I'd like to point you to
>the SOA-RM, currently going through final editing to incorporate
>comments from its 60-day public review. The PR version can be
>downloaded
>from
><http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/16628/wd-soa-rm-pr1.pdf>http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/16628/wd-soa-rm-pr1.pdf.
>
>It is relatively short and provides compact descriptions of both SOA
>and service. As a reference model, it contains a minimum number of
>concepts (such as service in the singular) from which more advanced
>concepts (e.g. a combination of several services) can be readily
>derived. So far it has been found to be fairly robust acting as a
>basis for the continuing work in SOA reference architecture. As one
>of the editors, I'm not exactly impartial, but for those who haven't
>seen it, I think it is worth the read.
>
>Back to occasional lurking,
>
>Ken
>
>On May 5, 2006, at 7:11 PM, Charles Mosher wrote:
>
>>This could be addressed by generalizing the definition of "customer" and
>>"client" to include customers and clients within the organization, as
>>well as without. And I agree; it is often such internal customers that
>>first see the need and ROI for a service-based approach to the
>>integration of company systems.
>>
>>I did notice that the concept of service partitioning, i.e., various
>>specializations of services from the higher level business
>>process/functional level (perform credit check) to the lower level
>>(retrieve customer record) is hard to describe with the layers as they
>>are depicted. In particular, services which can uniformly serve up data
>>(semantically and structurally mediated and rationalized) to business
>>services that are built on top of them are likely an important first
>>step to realizing a SOA system. These fundamental services are not
>>really represented in this architecture, where such detail is relegated
>>to the standards/implementation layer. There is the "thinking about
>>services throughout" admonition, which perhaps ameliorates this concern
>>somewhat.
>>
>>My 2 centavos.
>>
>>Best regards,
>>
>>Chuck
>>
>>
>>-----Original Message-----
>>From:
>><mailto:soa-forum-bounces@xxxxxxxxxxxxxx>soa-forum-bounces@xxxxxxxxxxxxxx
>>[<mailto:soa-forum-bounces@xxxxxxxxxxxxxx>mailto:soa-forum-bounces@xxxxxxxxxxxxxx]
>
>>On Behalf Of Graham Meaden
>>Sent: Friday, May 05, 2006 3:33 PM
>>To: Andras Szakal; Chris Harding
>>Cc: Service-Oriented Architecture CoP;
>><mailto:soa@xxxxxxxxxxxxx>soa@xxxxxxxxxxxxx
>>Subject: [soa-forum] RE: Definitions of SOA
>>
>>FOR CONSIDERATION:
>>
>>I suggest an alteration to part of the definition enclosed with the
>>presentation.
>>
>>Having worked as an Architect for a number of organisations with 50,000+
>>personnel, the need to flatten organisations, remove silos and achieve
>>agility is a perennial theme. For organisations of such size, the
>>application of a service oriented approach to organisation and service
>>design of internal services is as valid to the application of S.O. to
>>the provisioning of external services. On slide 3, the phrase <business
>>layer> "A set of services that an enterprise wants to expose to
>>customers and clients" seems of exclude applying S.O. to the internal
>>design of organisations. I believe this to be too prescriptive. I
>>suggest a change.
>>
>>
>>Graham Meaden
>>DIRECTOR, Enterprise Architect
>>
>>
>>
>>Celestial Consulting Ltd.
>>Mobile: + 44 7770 672 442
>>Telephone: + 44 870 421 5601
>>Facsimile: + 44 20 7900 6547
>>Email: <mailto:gmeaden@xxxxxxxxxxxxxxx>gmeaden@xxxxxxxxxxxxxxx
>>Skype id: gmeaden.celestial.co.uk
>>Skype in: + 44 20 7193 0565
>>
>>
>>
>>-----Original Message-----
>>From: Andras Szakal [<mailto:aszakal@xxxxxxxxxx>mailto:aszakal@xxxxxxxxxx]
>>Sent: 05 May 2006 14:50
>>To: Chris Harding
>>Cc: <mailto:soa@xxxxxxxxxxxxx>soa@xxxxxxxxxxxxx; Service-Oriented
>>Architecture CoP
>>Subject: Re: Definitions of SOA
>>
>>Team,
>>
>>I offer this additional chart which depicts the outcome of our
>>discussion
>>last week. I am still working the chart but it's a decent start. We
>>agreed
>>that SOA is actually only one aspect of this very interesting industry
>>initiative that needs our focus.
>>
>>I think we need to focus on service orientation as a superset of the SOA
>>discussion. In fact one could argue that service orientation may be
>>implemented by a combination of architectural styles and not just
>>SOA/web
>>services.
>>
>>(See attached file: Service_Orientation_Def_v1.ppt)
>>
>>Regards,
>>
>>Andras
>>
>>
>>
>>Andras Robert Szakal
>>Chief Architect IBM Federal Software Group
>>Distinguished Engineer & Senior Certified IT Architect
>>Member Open Group Board of Directors
>>Tie Line: 930-9215
>>External Line: 202-595-1678
>>text message: <mailto:andras1@xxxxxxxxx>andras1@xxxxxxxxx
>>email: <mailto:aszakal@xxxxxxxxxx>aszakal@xxxxxxxxxx
>>
>>
>>
>>
>> Chris Harding
>>
>> <c.harding@opengr
>>
>> oup.org>
>>To
>> Service-Oriented Architecture CoP
>>
>> 05/05/2006 08:31
>><<mailto:soa-forum@xxxxxxxxxxxxxx>soa-forum@xxxxxxxxxxxxxx>,
>>
>> AM "'Service-Oriented Architecture
>>
>> CoP'"
>><<mailto:soa-forum@xxxxxxxxxxxxxx>soa-forum@xxxxxxxxxxxxxx>
>>
>>
>>cc
>>
>><mailto:soa@xxxxxxxxxxxxx>soa@xxxxxxxxxxxxx
>>
>>
>>Subject
>> Definitions of SOA
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>Hi -
>>
>>As a further update, here is the definition of SOA that was presented at
>>The Open Group conference last week (and which we have shared with the
>>OMG).
>>
>>SOA is an architectural style that supports service orientation
>>
>>*Service orientation
>>A way of a way of thinking in terms of services and service based
>>development and the outcomes that services bring
>>
>>*Service
>>A logical representation of a repeatable business activity that has a
>>specified outcome (e.g., check customer credit; provide weather data,
>>consolidate drilling reports), is self-contained and maybe composed of
>>other Services. It is a black box to consumers of the Service
>>
>>*Architectural Style
>>The combination of distinctive features in which Enterprise Architecture
>>is
>>done, or expressed
>>
>>*The SOA Architectural style's distinctive features:
>> - Based on the design of the services comprising an enterprise's
>> (or inter-enterprise) business processes. Services mirror
>>real-world
>> business activity
>> - Service representation utilizes business descriptions. Service
>> representation requires providing its context (including business
>> process, goal, rule, policy, service interface and service
>>component)
>> and service orchestration to implement service
>> - Has unique requirements on infrastructure. Implementations are
>> recommended to use open standards, realize interoperability and
>> location transparency.
>> - Implementations are environment specific, they are constrained or
>> enabled by context and must be described within their context.
>> - Requires strong governance of service representation and
>>implementation
>> - Requires a "Litmus Test", which determined a "good service"
>>
>>At 20:31 04/05/2006, Cory Casanave wrote:
>>
>> As an update from the OMG meeting last week, the SOA SIG adopted
>>the
>> following definition of SOA;
>>
>>
>>
>> Service Oriented Architecture is an architectural style for a
>> community of providers and consumers of services to achieve mutual
>> value, that:
>> Allows participants in the communities to work together with
>> minimal co-dependence or technology dependence
>> Specifies the contracts to which organizations, people and
>> technologies must adhere in order to participate in the
>> community
>> Provides for business value and business processes to be
>> realized by the community
>> Allows for a variety of technology to be used to facilitate
>> interactions within the community
>>
>>
>>
>>
>>
>> The corresponding definition of service has not yet been finalized
>> but the sense of the group is that there would be both a
>> business/domain centric notion of service as well as an
>>interaction
>> focused definition.
>>
>>
>>
>> In both cases this seems to fit well with the notion of SOA that
>>is
>> evolving in this group and in the SOA Demo.
>>
>>
>>
>> Regards,
>>
>> Cory Casanave
>> _________________________________________________________________
>> Subscribe/Unsubscribe/Config:
>>
>><http://colab.cim3.net/mailman/listinfo/soa-forum/>http://colab.cim3.net/mailman/listinfo/soa-forum/
>> Shared Files:
>><http://colab.cim3.net/file/work/soa/>http://colab.cim3.net/file/work/soa/
>> Community Portal: <http://colab.cim3.net>http://colab.cim3.net/
>> Community Wiki:
>>
>><http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP>http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>>
>>
>>Regards,
>>
>>Chris
>>+++++
>>
>>========================================================================
>>Dr. Christopher J. Harding
>>Forum Director for SOA and Semantic Interoperability
>>THE OPEN GROUP
>>Thames Tower, 37-45 Station Road, Reading RG1 1LX, UK
>><Mailto:c.harding@xxxxxxxxxxxxx>Mailto:c.harding@xxxxxxxxxxxxx
>>Phone (mobile): +44 774 063 1520
>><http://www.opengroup.org>http://www.opengroup.org
>>******************************************************************
>>IT Architecture Practitioners Conference
>>Hyatt Regency, Coral Gables, FL July 17-19, 2006
>>Member Meetings - July 17-21, 2006
>><http://opengroup.org/miami2006/>http://opengroup.org/miami2006/
>>========================================================================
>>TOGAF is a trademark of The Open Group
>>
>> _________________________________________________________________
>>Subscribe/Unsubscribe/Config:
>><http://colab.cim3.net/mailman/listinfo/soa-forum/>http://colab.cim3.net/mailman/listinfo/soa-forum/
>>Shared Files:
>><http://colab.cim3.net/file/work/soa/>http://colab.cim3.net/file/work/soa/
>>Community Portal: <http://colab.cim3.net>http://colab.cim3.net/
>>Community Wiki:
>><http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP>http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>>
>>
>> _________________________________________________________________
>>Subscribe/Unsubscribe/Config:
>><http://colab.cim3.net/mailman/listinfo/soa-forum/>http://colab.cim3.net/mailman/listinfo/soa-forum/
>>Shared Files:
>><http://colab.cim3.net/file/work/soa/>http://colab.cim3.net/file/work/soa/
>>Community Portal: <http://colab.cim3.net>http://colab.cim3.net/
>>Community Wiki:
>><http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP>http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>>
>
>---
>Ken Laskey
>MITRE Corporation, M/S H305 phone: 703-983-7934
>7515 Colshire Drive fax: 703-983-1379
>McLean VA 22102-7508
>
>
>
>
> _________________________________________________________________
>Subscribe/Unsubscribe/Config:
>http://colab.cim3.net/mailman/listinfo/soa-forum/
>Shared Files: http://colab.cim3.net/file/work/soa/
>Community Portal: http://colab.cim3.net/
>Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (04)
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309
_________________________________________________________________
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (05)
|