[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm] interesting article - relevant to services and data model aspects of our RM
Sorry - I missed this earlier.
The writer was thinking
along the same pragmatic lines we were.
"To understand and apply the
principles of SOA, you’d think we would
have to agree first on what we mean
by a “service"
while he didn't actually suggest a definition, he added a
though that
clearly separates services from processes. (re: our thread on
service
being consumed as part of a process, POA et al)
"Services cross
both process and environment boundaries."
I felt the latter may be of use
to Vikas " SOA extends the tradition
along two axes: data representation and
data communication.". It is
similar to what he wrote in his section for
Data Model. exploring this
concept however, it is unclear from the
article if the author has given
this as much thought as Vikas. I am
curious to know if Vikas thinks
this aligns with his
section.
Duane
Matthew MacKenzie wrote:
>
Joe,
>
> Regardless of who sent the article, I am not seeing the
relevance. By
> being vague on the addressee, I had hoped that someone
would explain
> the relevance of the article to RM, or perhaps enlighten
me to
> alternative definitions of the word "relevance".
>
>
:-)
>
>
> Thanks,
> Matt
>
> On 3-May-05, at
5:15 PM, Chiusano Joseph wrote:
>
>
>
Matt, I believe you meant to address that to Duane per the
subject
> of the e-mail (?) Just pointing that out
so that there is no
>
confusion.
>
>
Joe
>
> Joseph
Chiusano
> Booz Allen
Hamilton
> Visit us online@ http://www.boozallen.com
>
>
From: Matthew MacKenzie [mailto:mattm@adobe.com]
>
Sent: Tue 5/3/2005 4:12 PM
> To: Chiusano
Joseph
> Cc: Duane Nickull;
SOA-RM
> Subject: Re: [soa-rm] interesting article
- relevant to services
> and data model aspects of
our RM
>
>
> Define
"relevant".
>
-Matt
>
> Chiusano Joseph
wrote:
>
> > I found this passage toward
the end (3rd par. from bottom)
>
perplexing
> > in terms of where he was leading
- it follows the discussion of
>
using
> > RSS and
REST:
> >
> >
"In fact, this low-tech approach is so appealing that
many
> people are
>
> now discounting the WS-* stack. That’s understandable and in
many
> > cases valid. While we argue about
which WS-* standards will
> stick
to
> > the wall, a set of key capabilities is
emerging. Broadly speaking,
> > WS-* pushes
aspects of data communication -- security,
asynchrony,
> > reliability, routing, and
proxying -- up into the application layer
> >
where we can reason about these things as businesspeople
rather
> than
> >
wrestle with them as network plumbers."
>
>
> > The first 3 sentences seem to support
the notion of using RSS
> and
REST
> > as alternatives to the WS-* stack (I
see the basic point, but there
> > are aspects,
such as security, that I believe he is discounting
and
> > should not). But then, starting with
"Broadly speaking,", he
> seems
to
> > be a fan of
WS-*.
> >
> >
Does anyone see this differently?
>
>
> > Joe
>
>
> > Joseph
Chiusano
> >
>
> Booz Allen Hamilton
>
>
> > Visit us online@ http://www.boozallen.com
>
<http://www.boozallen.com/>
>
>
> >
>
>
>
------------------------------------------------------------------------
>
>
> *From:* Duane Nickull [mailto:dnickull@adobe.com]
>
> *Sent:* Tue 5/3/2005 3:16 PM
> > *To:*
SOA-RM
> > *Subject:* [soa-rm] interesting
article - relevant to services and
> > data
model aspects of our RM
>
>
> > http://www.infoworld.com/article/05/03/11/11FEstateofarch5_1.html
>
>
> > --
>
> ***********
> > Senior Standards
Strategist - Adobe Systems, Inc. -
> http://www.adobe.com
>
> Vice Chair - UN/CEFACT Bureau Plenary -
> http://www.unece.org/cefact/
>
> Adobe Enterprise Developer Resources -
> >
http://www.adobe.com/enterprise/developer/main.html
>
> ***********
>
>
>
>
--
***********
Senior Standards Strategist -
Adobe Systems, Inc. - http://www.adobe.com
Vice Chair - UN/CEFACT
Bureau Plenary - http://www.unece.org/cefact/
Adobe
Enterprise Developer Resources - http://www.adobe.com/enterprise/developer/main.html
***********
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]