A single targetNamespace "urn:dss.hssp.org" is used in all of the following
machine readable files for the DSS submission:
wsdl file dss_minimum_functional_profile.wsdl (subset of full set of operations)
wsdl file dss_core_functional_profile.wsdl (subset of full set of operations)
wsdl file dss.wsdl (full set of operations)
xsd file HsspDssSchema.xsd (xs:include in wsdl:types element of each wsdl file)
The common wsdl:message definitions are repeated in each of the three wsdl files. This will cause a maintenance headache. These should be pulled out into a separate wsdl file which can be referenced by a wsdl:import into each of the three wsdl files above.
Is it necessary to keep the same namespace for both the schema and wsdl? It might be easier for ongoing maintenance to give the schema a different target namespace from the wsdl descriptions. This is a design decision that the FTF should consider.
Of greater significance, the targetNamespace used is not an OMG rooted namespace.
Solution proposed by originator:
The FTF should use OMG rooted namespaces, as opposed to continuing to use
hssp.org rooted namespaces?
Rather than using urn values for namespaces, the OMG has recommended strongly, the
use of URLs which resolve to a RDDL file which has pointers to the
wsdl and/or schema files which define that namespace?