[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 240] New: Anish editorial (1)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=240 Summary: Anish editorial (1) Product: WS-Context Version: 1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Editorial AssignedTo: ws-caf-editors@lists.oasis-open.org ReportedBy: mark.little@arjuna.com QAContact: mark.little@arjuna.com 3) Section 1 (heading) is missing, the spec starts straight with 1.1 EDITORIAL 4) Appendix A should not be section 9? EDITORIAL 5) In "Note on terminology" it says: "Namespace URIs of the general form "some-URI" represents some application- dependent or context-dependent URI as defined in RFC 2396 [3]." Doug: is this editorial, or a proposal about the terminology. Mark: it is just editoral AGREED EDITORIAL (Replace "some-URI" with "http://example.org/..." and http://example.com/...) 6) Section 1.1.1 Prefix Namespace table should be expanded to include the prefix "soapbind" and "soap" and an entry for wsrm referencing scheme. Also the prefix "tns" has the namespace "targetNamespace. The tns entry should be moved outside the table with an explanation since "targetNamespace" is not a namespace URI. EDITORIAL 7) Section 2, line 2: s/operations/interactions EDITORIAL 9) Section 2.2, page 6 does not say anything about WSDL 2.0. It would be good to separate WSDL 1.1 and 2.0. The normative WSDL is indeed 1.1, but the wording in section 2.2 talks about WSDL generically. Previous decision was to target WSDL 1.1. EDITORIAL CLARIFICATION/restatement ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]