This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4492 - Canonical fragments and targetNamespace
Summary: Canonical fragments and targetNamespace
Status: CLOSED FIXED
Alias: None
Product: WSDL
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: WSDL Mailing List
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2007-04-25 17:13 UTC by Jonathan Marsh
Modified: 2007-04-26 15:35 UTC (History)
0 users

See Also:

Attachments

Description Jonathan Marsh 2007-04-25 17:13:53 UTC 
I'm also implementing the creation of the fragment identifiers and I found the following small (maybe editorial) problems in Appendix C:

1) the canonical form does not say that no xmlns() pointer part should define the namespace same as the namespace of the WSDL 2.0 document, so it doesn't seem that the following would be uncanonical, while it should be:

http://example.com/wsdl#
    xmlns(ns1=http://example.com/wsdl#)
    wsdl.interfaceFaultReference(iface/op/In/ns1:Foo)
Comment 1 Jonathan Marsh 2007-04-26 15:33:13 UTC 
Add the constraint: "No xmlns() pointer part defines a namespace for the targetNamespace of the WSDL 2.0 document."