RE: Comments on WSA "Architectural Style" section 1.2

I followed Roy's style of derivation.  That is, a number of exclusive axis
are refined indpendently then joined together.  For example, Client-Server
is refined by Layering, to produce LCS style.  Then LCS is combined with
other axis, such as $, UI, etc., to form REST style.

I'd be curious as to what is wrong with that?  Seems like what's good for
REST is good for SOA.
Cheers,
Dave

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Mark Baker
> Sent: Wednesday, March 12, 2003 5:48 PM
> To: Walden Mathews
> Cc: [email protected]
> Subject: Re: Comments on WSA "Architectural Style" section 1.2
>
>
>
> On Wed, Mar 12, 2003 at 06:42:25PM -0500, Walden Mathews wrote:
> > Assuming we know something about the method used for deriving
> > one style from another, namely that it's purely about adding more
> > constraints
> > to derive new styles.  Although Fielding prefers that
> method in his REST
> > thesis, we have no right to assume it's the preferred method here.
>
> If you permit derivation in a manner that doesn't carry forward the
> constraints with it, then that's equivalent to saying that all styles
> derive from all others.  Not particularly useful.
>
> I can't fathom any other means of style derivation than by constraint
> extension.
>
> > What this means for SOA is both good news and bad news.  The bad
> > news is that the architecture document is in error when it says that
> > "mediated
> > SOA" doesn't use URIs to identify resources.  The good news
> is, yes it
> > does.  It does because SOA resources are "services", hence
> always abstract
> > and dynamic, as distinct from data representations.  It's a
> trivial test, as
> > compared with some REST cases.
>
> Whoa.  I'd prefer not to go there.  I'll just let my comments stand.
>
> MB
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>
>