- From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
- Date: Mon, 24 Feb 2003 10:41:45 -0600
- To: "David Booth" <dbooth@w3.org>, "Hugo Haas" <hugo@w3.org>, www-ws-arch@w3.org
OK, we've kicked this term around enough so that it seems pretty clear that it is not going to be a quick kill to get consensus on a general definition, and I think David is absolutely correct: we need to address the issue itself, but not necessarily this term as a general concept. So I suggest something along the following resolution to resolve the issue: "The WG is not currently using the term "a priori information" in the reference architecture, so we do not feel a need to come to an agreement about the meaning of the term in general. In the specific context in which it is used in the group charter, we understand it to mean "prior information". We interpret this as a requirement that the architecture support late binding." -----Original Message----- From: David Booth [mailto:dbooth@w3.org] Sent: Thursday, February 20, 2003 10:51 AM To: Hugo Haas; www-ws-arch@w3.org Subject: Re: Snapshot of Web Services Glossary ... 2. a priori information I suggest eliminate this term from the glossary. There is an issue regarding the INTENT of that term in the architecture document, and that issue does need to be resolved. But the term itself is not meant in any special sense that is specific to Web services. I think the way to resolve the issue is to add more explanation to our architecture document, rather than defining any special meaning for the term. ...
Received on Monday, 24 February 2003 12:20:16 UTC