Comments on the requirements document: editorial, on D-AG00{01,02,04,06,07,09,10,11,12,16,17,19,20} (was Re: Face-toface review draft of requirements document)

Hi Daniel, editors and WG.

I have finally got around to typing in an email the notes I took about
the requirements document.

Some comments are editorial (the first two or three comments), the
rest isn't. Some might have been superseded by edits made at the
face-to-face. I am putting them all here and you can choose to ignore
the comments that are not relevant anymore.

Top of the document:

  The note about the use of RFC 2119 should go in the introduction.
  There shouldn't be anything before the abstract.

Use of the term "Web service":

  I see in the document sometimes "Web Service", sometimes "Web
  service", sometimes "web service". Web is definitely capitalized,
  service should IMO be lowercase.

Abstract: 

  Typo at the end: s/\.\./\./

Status section:

  | The Web Services Architecture Working Group will not allow early
  | implementation to constrain its ability to make changes to this
  | document prior to final release.

  I am not sure that we can talk about implementations for the
  architecture document. I am struggling to find a better wording
  though. Maybe "application" instead of "implementation".

1.1 What is a Web Service?

  | The group has jointly come to agreement on the following definition:
  
  There was definitely no consensus on the definition. We should try
  to carry the message that we agree to use this definition for now.

2.2.1.2 Vision

  Typo: s/intendedto/intended to/

D-AG0001 AC0012-A

  There was some further discussion about that:
  http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0346.html

D-AG0002 AC0022

  This CSF doesn't seem to go in the direction of programming
  model/language Independence.

D-AG0004

  This goal talks about Web components. Are Web components resources
  identified by a URI? If yes, I would call them resources, not
  components. If not, what are they?

D-AG0006 WSASecReq001

  I had doubts about how DOS attacks is in our scope. I guess that Joe
  will bring this up.

D-AG0007 CSF RA3

  I wouldn't make a list of standards bodies. Who do you list here? Who
  do you not list?

D-AG0007 D-CSF RA*

  I think they should go away.

D-AG0007 CSF SA2

  I don't understand this CSF.

D-AG0007 CSF PE1

  Same comment.

D-AG0009

  I think that "and the overall existing web architecture" is covered
  by D-AG0011.

  The requirements for this should be (from Eric's presentation[1]):

      * All recommendations produced by the working group include a
	normative mapping between all XML technologies and RDF/XML.

      * All conceptual elements should be addressable directly via a
	URI reference.      

D-AG0010

  In light of the above requirement ("normative mapping between all
  XML technologies and RDF/XML"), I don't think that the "syntactic
  schema language" paragraph is necessary. An RDF Schema could be a
  valid description.

D-AG0011

  I don't think that "to the greatest extent possible" is necessary.
  This is true for all goals.

D-AG0011 CF1-*

  As I said during the F2F, I think those should be dropped as
  explained in:
  http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0475.html

D-AG0012

  I would: s/use cases/usage scenario and use cases/

D-AG0016

  This one was discussed during the 28 March teleconference[2] and
  people were not comfortable with "identify architectural and
  technology gaps that prevent interoperability".

D-AG0017

  Typo: s/frameword/framework/

D-AG0019

  | Web Services created using WSA can be reliably selected, accessed,
  | and executed.

  What does "selected" mean?

D-AG0020

  Requirement identified:

  It must be possible to advertise privacy policies for Web services.

Regards,

Hugo

  1. http://www.w3.org/2002/Talks/0408-ws-f2f-sweb/
  2. http://www.w3.org/2002/ws/arch/2/03/28-minutes
-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092

Received on Tuesday, 16 April 2002 17:18:43 UTC