RE: D-AG0005 - Simplicity Requirement

Mike's point is well taken.  I agree that it is difficult to measure interoperability before the specs are released but I guess one way of ensuring interoperability in the specs would be that they are written in a way that there is not much room left for different interpretations when implementing them.  The current wording of D-AG0005 requirement: "provides simplicity and ease-of-use that does not impose high barriers to entry for users of web services".  To me, one of the implications of "simplicity and ease-of-use" is "interoperability", i.e. no significant difference in web services components, minimal architectural and technology gaps, etc.  Any thoughts?  


-----Original Message-----
From: Champion, Mike [mailto:Mike.Champion@SoftwareAG-USA.com]
Sent: Monday, March 11, 2002 9:15 AM
To: www-ws-arch@w3.org
Subject: RE: D-AG0005 - Simplicity Requirement




> -----Original Message-----
> From: Dilber, Ayse, ALASO [mailto:adilber@att.com]
> Sent: Monday, March 11, 2002 8:53 AM
> To: Cutler, Roger (RogerCutler); Champion, Mike; www-ws-arch@w3.org
> Subject: RE: D-AG0005 - Simplicity Requirement
> 
> 
> could "supports interoperability" be one of the measurements?

Interesting thought: If the point of simplicity is to promote
interoperability, if it interoperates, it must be sufficiently simple!

The problem I see is that concrete interoperability is in the products based
on the specs based on the reference architecture, so it's not clear to me
how to measure interoperability before we release the spec.  Any
clarifications / ideas?

Received on Monday, 11 March 2002 10:19:08 UTC