W3C home > Mailing lists > Public > www-tag@w3.org > May 2002

RE: [WhenToUseGet-7] Re: TAG document: SOAP HTTP GET binding avai lable

From: <noah_mendelsohn@us.ibm.com>
Date: Thu, 16 May 2002 13:26:59 -0400
To: "Williams, Stuart" <skw@hplb.hpl.hp.com>
Cc: "'Tim Bray'" <tbray@textuality.com>, www-tag@w3.org, www-tag-request@w3.org
Message-ID: <OF1B513A7B.DA0DE16E-ON85256BBB.00602140@lotus.com>
Stuart Williams writes:

>> I also think that the TAG should focus on the 
>> articulation of Web Architecture and arhitectural 
>> principles. I think we can help WG's like XMLP
>> in resolving issues of Web Architecture, *but* IMO 
>> the WG itself must be allowed to own the problem 
>> and to take responsibility for its resolution.

+1, I agree completely. 

IMO, the Tag should be responsible for clarifying architectural 
principles, and should help workgroups to succeed in producing 
specifications consistent with that architecture.  First of all, this 
approach helps to ensure that, over time, everyone doing the work is 
"bought in" to the overall architecture.  Secondly, it is the individual 
workgroups that have essential expertise in the particular specifications 
being developed. 

For both of those reasons, I strongly urge the Tag to work with the XMLP 
workgroup to agree on the pertinent Web architecture principles and to 
explore any tradeoffs involved in various approaches.  I think the XMLP 
workgroup should be responsible for drafting any SOAP-specific 
recommendations or notes.  The Tag should be responsible for drafting 
notes and recommendations having to do with overall Web architecture. Just 
my opinion, but I do feel quite strongly about it.  Thank you.

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
Received on Thursday, 16 May 2002 13:46:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:51 UTC