Re: Thinking about Web Services Architecture

Hi Daniel.

Thank you for the email. A few responses:

* Austin, Daniel <Austin.D@ic.grainger.com> [2002-02-11 12:56-0600]
[..]
> Issue #3 Is the processing model in-scope?
> This is an issue that occurred to me in my own pondering on the subject.
[..]
> Do we feel that this is in scope for us? It certainly will affect our work,
> but it's not clear if it should be under the "web services umbrella" or not.

I do not think that we need to go into that kind of detail. The "that
kind of detail" line will need to be defined though. :-)

[..]
> Issue #5 Editorial Work
[..]
> For editing the document I would suggest that we use XMLSpec [7] This may
> actually be required by W3C. Several WGs use this for their document
> production.

The use of XMLSpec, even though it is not required by the process, is
*strongly* encouraged. It comes with the set of tools which make it
easy to comply with the W3C publication rules and therefore will make
everybody's life easier.

> In terms of the actual output, I can foresee a Requirements document, a
> Technical Architecture document, a Rationale document, and of course the
> inevitable Errata list and a mechanism for making changes and modifications.
> Have I missed anything?

We should work on a roadmap too. Are there things that need to be
designed first, etc?

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092

Received on Wednesday, 13 February 2002 19:42:23 UTC