www-ws-arch@w3.org from March 2002 by subject

(jdm) Regrets - 21 March Mtg

[Fwd: Comments sought - Web Ontology Requirements Working Draft]

[R505][i54] No a priori knowledge Requirement

[W3-WSAWG] WS-Arch Requirements

AG0013: Coordination / liaison inside / outside W3C; result of D-AG0013 and D-AG0014

architecture question

Are Footnotes in Scope?

Article on Web Services

Back to Requirements (was RE: Web Service Definition [Was

Back to Requirements (was RE: Web Service Definition [Was "So me T houghts ..."])

Back to Requirements (was RE: Web Service Definition [Was "Some T houghts ..."])

D-AG0001-A - Conformance and Interoperability

D-AG0002 - Modularity of Web Services Architecture

D-AG0003: sufficiently extensible to allow for future evolution.. ..etc.

D-AG0005 - Simplicity

D-AG0005 - Simplicity Requirement

D-AG0007- reliable, stable, predictably evolvable - v0x1

D-AG0007.1- defining reliable and stable WS [was RE: Status: D-A G0007 - reliable, stable, predictable evolution]

D-AG0008:

D-AG0008: "is coherent and consistent in its definition"

D-AG0009 status

D-AG0009; Semantic Web & Web architecture

D-AG0010: Use XML

D-AG0011 - Consistency

D-AG0011 status

D-AG0012 Use Cases

D-AG0013: Coordination within W3C

D-AG0014

D-AG0014 - Consistency

D-AG0014 [coordination / liaison outside W3C]

D-AG0015 Time to Market Discussion

D-AG0016 - Technology Gaps

D-AG0016 Technology Gaps CSFs

D-AG0017

D-AG0017 - Business Infrastructure

D-AG0017 [was Re: Reliable Messaging and Business Requirements - [Was DAG006]]

D-AG0017 Revised

D-AG0017, should be D-AG0018

D-AG0018

D-AG0019 [RE: D-AG0007.1- defining reliable and stable WS ]

D-AG0020 Privacy (was Re: WS Privacy)

D-AG004: Ensures platform independence

D-AG004: Ensures platform independence: Summary

D-AG006 Security

DAG0010 - use of XML

DAG0012 Use Cases

Definitions

delay in publishing latest editor's draf tof WSAWG requirements

Emperor has no clothes (Observations on the Web Services Defi nition)

Emperor has no clothes (Observations on the Web Services Definiti on)

ESSW2002 - workshop on models/approaches for web services

Exemplars of a good "reference architecture"

fyi regarding use cases for wsdwg

hosting subsequent F2F meetings

HP Web Services Transactions

Introduction

Introduction, and 3/21 regrets

Latest version of requirements document posted in XHTML

Let us clothe the Emperor in Blue Jeans (was: Emperor has no clothes (Observations on the Web Services Definition)

Let's play "interpret the charter"!

Lteast version of requirements document uploaded

March 26 2002 version of requirements draft

Minutes of the 14 March teleconference

Minutes of the 2002-03-21 teleconference

Minutes of the 21 & 28 February teleconferences

Minutes of the 7 March teleconferences

Missing in Goals?

New Goals of the WSAWG

proposed redraft of DAG0005

Putting web services in context

Regrets 28 March concall

Regrets 4 April concall

Regrets for 3/28 call

regrets for call

Reliable Messaging and Business Requirements - [Was DAG006]

REPOST: D0003 status

Security?

service identification (was: Re: Web Services Definition and XML)

Status D-AG0019: reliable, stable, and predictably evolvable Web Services

Status of D-AG0005

Status of D-AG0013: Coordination within W3C

Status of D-AG0014, coordination / liaison outside W3C

Status of D-AG0016 - Technology Gaps

Status of D-AG0020: Privacy

Status of D-AG006

Status of D-AG006 + CSF

Status: D-AG0007 - reliable, stable, predictable evolution

Summary D-AG0007- reliable, stable, predictably evolvable

Summary: D-AG0006 -- Security

Summary: D-AG0011

Summary: D-G0017

Transaction Context [was Re: D-AG006 Security]

Transactions

Updated status of D-AG0014, coordination / liaison outside W3C

URI's

Web architecture

web service definition

Web Service Definition [Was "Some Thoughts ..."]

Web Services Architecture

Web Services Definition and XML

What is SOAP?

WS Privacy [Was RE: Status of D-AG006]

WSCL submission

Last message date: Saturday, 30 March 2002 20:00:55 UTC