[Bug 240] Anish editorial (1)

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=240





------- Additional Comments From mark.little@arjuna.com  2005-02-28 12:29 -------
10) Section 2.3 (page 6), refers to WS-CAF.  This is the first reference to WS-
CAF.  It will throw-off the reader unless she knows the name of the TC.  
Suggestion: s/WS-CAF/this specification.
EDITORIAL, but the text needs to explain what the CAF family is.

11) Figure 1 (page 6), the title "service-ref Element" is incorrect.  There is 
only a complexType defined in the figure.
EDITORIAL

11) Figures/XML snippets typos: some of the xml/wsdl/soap snippets are not 
valid XML.  Verifying the examples with a parser would help avoid typos.  
Examples of invalid example: page 6, figure 1, last line (closing '>' missing) 
page 9, figure 5, 6th line (invalid schema type)
EDITORIAL

12) Consistent indentation in the examples would help readability.
EDITORIAL

13) In the spec text using a different font/bold/italics/emphasis for XML 
element names/attributes would also help readability.  It would also help to 
prefix the element names/attributes with the "ctx:" prefix (or whatever is 
appropriate).
EDITORIAL

14) page 7, first paragraph refers to "WSRef defined in WS-Addressing" (WSRef 
is used again in the following paragraph as well).  I suspect the first 
occurrence really means wsrm-ref:reference-scheme and the second occurrence 
means a 'Web service reference'.
EDITORIAL: Covered by existing issue on WS-Addressing

15) page 7, 2st para:
s/reference schema/wsrf-ref:reference-scheme
EDITORIAL

17) Figure 3 and figure 4, page 7, it is not clear to what the prefix "ex:" 
refers.
EDITORIAL




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.