W3C home > Mailing lists > Public > www-ws-arch@w3.org > March 2002

RE: D-AG004: Ensures platform independence: Summary

From: <michael.mahan@nokia.com>
Date: Fri, 29 Mar 2002 11:04:32 -0500
Message-ID: <5C76D29CD0FA3143896D08BB1743296A072C49@bsebe001.NOE.Nokia.com>
To: <abbieb@nortelnetworks.com>, <www-ws-arch@w3.org>
Hi Abbie,
 
This summary does not respond to my concerns stated in [1] with the exception 
that you stated [2] that the goal is directly lifted from the charter [3]. The charter 
says: 
 
"The architecture designed by the Working Group must be platform independent, 
must not preclude any programming model nor assume any particular mode of 
communication between peers."
 
I still think it is wrong for this goal to reword the charter and make it sound like 
platform independence produces independent programming models or independent
modes of communication. I think the charter itemizes them as 3 separate issues.
 
I would like to see this goal specifically address independence of programming 
models and modes of communication besides platform independence - especially 
since the issue of platform independence overlaps with AG0008.
 
More inline comments:
                    
 > This is the summary of D-AG004: Ensures platform independence.
 
 > The goal as stated  
 
 > D-AG0004 
 > ensures platform independence of web services components in a way that does
 > not preclude any programming model nor assume any particular mode of
 > communication between the individual components 


 > 1. Goal statement stays as is.
 > 2. Crtitical Success Factors
 
 > a. Focus on using platform independent development tools and languages. 
 
I do not think this goal should focus at all on development tools and languages [4] 
 
 > b  Interfaces to web components must be properly defined and designed. 
 
I do not think this has anything to do with this goal.
 
 > c. Focus on defining the architecture in terms of components and the relationships between them.
 >     Components are defined in terms of interfaces, that defines their inputs and outputs and also the form 
 >    and constraints on those inputs and outputs. The relationships between components are described in terms 
 >     of messages and the protocols by means of which these messages are transmitted among the interfaces 
 >    of the components that make up the architecture. 
 
Again, I do not see strong relevance to programming models, modes of communication, or even platform 
independence.
 
 
> 3. Derived Requirements
> 
> a. Consistent definition of web components 
 
This is addressed by goal AG0008: "coherent and consistent in its definition". At least the way I read that goal.
 
> b. Good definition of web component Interfaces their inputs/outpus and their constraints. 
 
I do not think that the word "good" is sufficient  in a requirement.  I suggest the word "unambiguous". However,  
I believe  this requirement has little to do with this goal.
 
> c. Use XML based techniques for defining messages/protocols for invoking web components. 
 
 
 
> I have tried to summarize the points in concise format. I need feedback if I have not expressed the summary in a proper language and/or format. 

 
[1]  <http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0325.html> http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0325.html
[2]  <http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0327.html> http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0327.html
[3]  <http://www.w3.org/2002/01/ws-arch-charter> http://www.w3.org/2002/01/ws-arch-charter
[4] http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0319.html
 
 
 
 
 
 
Received on Friday, 29 March 2002 11:05:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:24:56 GMT