WSA constraints

( seems to be having mail forwarding troubles, so please CC

> I get nervous when people say things that imply they want
> the TAG to be the Court of Appeals for that process.  IMHO that's
> antithetical
> to the "consensus on means if not ends" idea that is at the heart of
> any effective industry consortium.  I see this WG as a place for the Web
> industry to get together, sort architectural issue out into what we can
> agree on and
> what we must agree to disagree on, all with the input from the public at
> large and the considered advice of the TAG.  There ain't no Final Authority
> here other than what works in the real world. 

I'm trying to get past that.  I'd hope that the suggestions I present
would be judged on their own merits.

With that in mind, I think documenting the constraints implicit in the
software developed to SOAP 1.1 + WSDL 1.1 is the best way to describe
the architecture of the system.  So far I've suggested that the existing
WSA includes these constraints on the relationships between components;

- layered
- client/server

and DaveO suggested;

- XML messages

I'm suggesting we continue this process, and include the results in the
architecture document.


Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.     

Received on Sunday, 22 September 2002 14:00:08 UTC