RE: Updated Primer for Editors and Chairs Sanity Check

Hi Paul,

 

Thanks for the quick review. We will get this done (hopefully in the near
future :-)

 

I have some questions and comments on your comments. Questions to understand
what is needed.

 

Please see below tagged with PY> 

 

  _____  

From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
Sent: Thursday, September 28, 2006 2:44 PM
To: Prasad Yendluri
Cc: public-ws-policy-eds@w3.org; fsasaki@w3.org; Christopher B Ferris
Subject: RE: Updated Primer for Editors and Chairs Sanity Check

 

Thanks for taking up this work.  Unfortunately I don't think we are quite
done yet.

 

1. Old comment

 

My comment about incorrect References does not appear to have been fixed:

 

20. Appendix C. References
 
[WS-Addressing Policy]
Web Services Addressing 1.0 - WSDL
Binding<http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/
<http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/> >, M. Gudgin, M.
Hadley, T. Rogers and Ü. Yalçinalp, Editors. World Wide Web Consortium, 29
May 2006. This version of the Web Services Addressing 1.0 - WSDL Binding is
http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/
<http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/> . The latest version
of Web Services Addressing 1.0 - WSDL
Binding<http://www.w3.org/TR/ws-addr-wsdl
<http://www.w3.org/TR/ws-addr-wsdl> > is available at
http://www.w3.org/TR/ws-addr-wsdl <http://www.w3.org/TR/ws-addr-wsdl> .
 
The short name of this reference should be [WS-Addressing WSDL Binding].
Change here and where it is used.
PY> Oops. I fixed this one now.

 

[Web Services Policy Framework]
Web Services Policy 1.5 -
Framework<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-frame
work.html
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html
> >, A. S. Vedamuthu, D. Orchard, M. Hondo, T. Boubez and P. Yendluri,
Editors. World Wide Web Consortium, @@, @@@@ @@@@. This version of the
specification of the Web Services Policy 1.5 - Framework specification is
ws-policy-framework.html. The latest version of Web Services Policy 1.5 -
Framework<http://www.w3.org/TR/ws-policy-framework
<http://www.w3.org/TR/ws-policy-framework> > is available at
http://www.w3.org/TR/ws-policy-framework
<http://www.w3.org/TR/ws-policy-framework> .
 
[Web Services Policy Attachment]
Web Services Policy 1.5 -
Attachment<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-atta
chment.html
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.htm
l> >, A. S. Vedamuthu, D. Orchard, M. Hondo, T. Boubez and P. Yendluri,
Editors. World Wide Web Consortium, @@, @@@@ @@@@. This version of the
specification of the Web Services Policy 1.5 - Attachment specification is
ws-policy-attachment.html. The latest version of Web Services Policy 1.5 -
Attachment<http://www.w3.org/TR/ws-policy-attachment
<http://www.w3.org/TR/ws-policy-attachment> > is available at
http://www.w3.org/TR/ws-policy-attachment
<http://www.w3.org/TR/ws-policy-attachment> .
 
Please check that these references are correct.  The Framework is found at
"http://www.w3.org/TR/ws-policy <http://www.w3.org/TR/ws-policy> " and the
Attachment is found at http://www.w3.org/TR/ws-policy-attach/
<http://www.w3.org/TR/ws-policy-attach/> . "framework" does not appear in
the Framework URI and "attachment" does not occur in the Attachment URI.
PY> I am not sure I quite understand what is the issue. In the previous pass
I thought I picked up the new URIs I am listing below what we have in the
Primer now. The hyperlinks do point to  <http://www.w3.org/TR/ws-policy>
http://www.w3.org/TR/ws-policy and  <http://www.w3.org/TR/ws-policy-attach/>
http://www.w3.org/TR/ws-policy-attach/. Was that the issue? The text you
have above seems to be old?
 

[Web Services Policy Framework] 

 <http://www.w3.org/TR/ws-policy/> Web Services Policy 1.5 - Framework, A.
S. Vedamuthu, D. Orchard, M. Hondo, T. Boubez and P. Yendluri, Editors.
World Wide Web Consortium, @@, @@@@ @@@@. This version of the specification
of the Web Services Policy 1.5 - Framework specification is
ws-policy-framework.html. The  <http://www.w3.org/TR/ws-policy/> latest
version of Web Services Policy 1.5 - Framework is available at
http://www.w3.org/TR/ws-policy/. 

WS_PolicyAttachment[Web Services Policy Attachment] 

 <http://www.w3.org/TR/ws-policy-attach/> Web Services Policy 1.5 -
Attachment, A. S. Vedamuthu, D. Orchard, M. Hondo, T. Boubez and P.
Yendluri, Editors. World Wide Web Consortium, @@, @@@@ @@@@. This version of
the specification of the Web Services Policy 1.5 - Attachment specification
is ws-policy-attachment.html. The  <http://www.w3.org/TR/ws-policy-attach/>
latest version of Web Services Policy 1.5 - Attachment is available at
http://www.w3.org/TR/ws-policy-attach/.

 

 

2. Missing spaces

 

Section 3.1 - "Other child elements ofPolicy"

PY>Got it this time around. The difficulty with find these is that there are
XML tags between the attached words, and hence they are hard to find the XML
text version of the spec we edit. 

 

3. New comments

 

a) Table B-1. Prefixes and XML Namespaces used in this specification

There appear to be two duplicate rows in this table:


 

http://www.w3.org/@@@@/@@/ws-policy 

[Web
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html#WS
-Policy#WS-Policy>  Services Policy Framework, Web
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html#WS
-PolicyAttachment#WS-PolicyAttachment>  Services Policy Attachment]


wsp 

http://www.w3.org/@@@@/@@/ws-policy 

[Web
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html#WS
-Policy#WS-Policy>  Services Policy Framework, Web
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html#WS
-PolicyAttachment#WS-PolicyAttachment>  Services Policy Attachment]

 

I think the blank prefix is supposed to imply that when there is no prefix
that this implies the http://www.w3.org/@@@@/@@/ws-policy
<http://www.w3.org/@@@@/@@/ws-policy>  URI.  See the text earlier "XML
elements without a namespace prefix are from the Web Services Policy XML
Namespace ". I think this note should be repeated in this section to explain
the empty prefix box.

 

Note as well that the left vertical border line and the top border line of
the prefix box that is empty also appear to be different than all other
border lines.

 

PY>Hmm, the blank-prefix line actually seems to be a typo. The table is
supposed to list the namespace prefixes used in the document. This table is
similar to what the Framework and Attachment document also contain. They do
not have a blank namespace prefix entry. Also, what the default namespace is
very context sensate, especially with examples etc. So, a blank namespace
prefix cannot always mean it is the WS-Policy Namespace. I suggest we simply
delete that row. Any concerns? 

 

/paulc

 

 

 

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:Paul.Cotton@microsoft.com <mailto:Paul.Cotton@microsoft.com> 




  _____  

From: Prasad Yendluri [mailto:prasad.yendluri@webmethods.com] 
Sent: September 28, 2006 4:07 PM
To: public-ws-policy-eds@w3.org; fsasaki@w3.org; Paul Cotton; Christopher B
Ferris
Subject: Updated Primer for Editors and Chairs Sanity Check

 

Folks,

 

I have made the remaining changes that Paul raised in his mail
(http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0165.html
<http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0165.html> )

The updated primer is available at:

 

http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html
<http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html> 

 

I thought I would send it for the quick sanity check review of the editors
and chairs this time around, prior to sending it to the WG.

 

1. I should note that the acknowledgements section is not fixed up yet.

The acknowledgements are all in a common file that is used by all
(Framework, attachment and primer) documents, to create the Acknowledgements
section.

It seems better done by the W3C staff. Both the membership and company
affiliations need to be reflected accurately.

 

2. Once Acknowledgements are updated we need to regenerate the HTML version
of the primer and Tag it in CVS so that we can give a hard pointer to the
team. 

 

Felix, could I request your help with the above two steps? 

 

Thanks,

Prasad