- From: <Daniel_Austin@grainger.com>
- Date: Wed, 4 Jun 2003 11:54:52 -0500
- To: jdart@tibco.com
- Cc: public-ws-chor@w3.org, public-ws-chor-request@w3.org
I for one, am willing to go with 1.1.b. If we want to add the caveat
suggested by Jon, that's fine. I'd really rather not burn too much time on
this issue; let's take a stab at it and then let it go. We can revise it
later if circumstances require.
Regards,
D-
*************************************************
Dr. Daniel Austin
Sr. Technical Architect / Architecture Team Lead
daniel_austin@notes.grainger.com <----- Note change!
847 793 5044
Visit http://www.grainger.com
"If I get a little money, I buy books. If there is anything left over, I
buy clothing and food."
-Erasmus
"Jon Dart"
<jdart@tibco.com> To: public-ws-chor@w3.org
Sent by: cc:
public-ws-chor-req Subject: Re: Revised: Mission Statement
uest@w3.org
06/04/2003 10:58
AM
Please respond to
jdart
Nickolas Kavantzas wrote:
> I also agree with Assaf that the 2 definitions of our mission statement
are not bad, just a bit too generic.
I think 1.1b is ok. A mission statement is supposed to be generic. IMO
it should specify goals, not means.
Re 1.1a: I'm actually ok with the idea (I've generally been in the
pro-WSDL camp) but IMO it's specifying the means to reach the goal, not
so much the goal itself.
Perhaps we could pick 1.1b and follow it up with the statement that "It
is expected that this group's mission will be achieved by specifying one
or more XML-based languages [or insert better word - descriptive
systems?] building on the foundation of WSDL 1.2".
--Jon
Received on Wednesday, 4 June 2003 12:54:36 UTC