D-AG0005 - Simplicity

I fear that I did not express myself very well in the phone call.

We are talking here about goals for the work group.   I believe that there
are two goals involving simplicity that are reasonably separable:

1 - To develop a standard reference architecture for web services that, when
used by people who are specifying, creating or using web services does not
impose high entry barriers and encourages simplicity and ease of use of web
services for everybody concerned.

2 - To develop a standard reference architecture for web services that is
documented in such a manner that does not impose high barriers to usage of
the architecture document.

Perhaps the latter is trivial in some sense, but I think that it deserves
some mention as a goal for the work group.  Examples of possible
applications:

1 - Words (in the architecture document) should, when possible, be used to
mean what people commonly think that they mean.

2 - If possible the architecture should not be expressed in terms of a
formalism that requires a lot of work to learn.  That is, a person should be
able to understand the architecture, or at least a reasonable subset of it,
without taking some sort of university course first.

3 - Examples that illustrate concepts are really nice. So are simple,
declarative sentences.

4 - The document should be organized in such a way that one can find things,
one can dig into a hierarchy of detail, and so on.

I think (hope) that this is motherhood and apple pie -- but it seems to me
no less so than some of the other goals.