This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
2. The inclusion of identifiers for element declarations and type definitions (which are not WSDL 1.1 elements) seems inappropriate in this spec. The presence of schema imports and includes makes associating type definitions with a particular WSDL document, and thus with a particular targetNamespace, problematic. These identifiers donât seem to be required by WS-Policy Attachment. We recommend removing them. If these identifiers remain, a number of issues related to them should be addressed, including: a. How imports and includes affect them. Are only in-lined schema elements considered? Only elements in a schema targetNamespace that is the same as the WSDL targetNamespace? If not, which ones? b. Clarification in the prose of the spec that WSDL element identifiers identify elements both in the WSDL and Schema namespaces. c. Correction of the âtypesâ? vs. âtype definitionsâ? issue, described at [1]. [1] http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0002.html
[13:49] paulc: Proposal: [13:49] paulc: 1. Remove the EIs for element declarations and type definitions [13:50] Zakim: -DOrchard [13:50] paulc: 2. Add a paragraph to the status section noting that EI's are not defined by element declarations and type definitions and why [13:50] paulc: 3. Ask for feedback on item 2. [13:50] cferris: +1 [13:50] Jonathan: +1 [13:50] cferris: RESOLUTION: 4332 closed with 1, 2 and 3 above [13:50] charltonb: +1 [13:51] * Ashok works for me [13:51] paulc: This proposal resolves 4045 differently than before [13:51] cferris: rrsagent, where am i? [13:51] RRSAgent: See http://www.w3.org/2007/03/07-ws-policy-irc#T18-51-52