Issue 14856: DSS: single targetNamespace "urn:dss.hssp.org" (dss-ftf) Source: Fujitsu (Mr. Tom Rutt, tom(at)coastin.com) Nature: Uncategorized Issue Severity: Summary: 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? Resolution: The recommended changes have been made. Specifically: - The common WSDL definitions have been pulled into a new WSDL (dssBaseComponents.wsdl). This WSDL is then referenced through a wsdl:import into each of the WSDLs that correspond to the conformance profiles. - The namespaces for the schemas and WSDLs have been separated. - The targetNamespace has been changed to be an OMG rooted namespace. - For the namespaces, URLs that resolve to a RDDL which has pointers to the relevant WSDLs and XSDs are now provided, as described in the document authored by Tom Rutt on this topic, obtained form http://xml.coverpages.org/OMG-Rutt-NamespaceProposal- 20090917.pdf Revised Text: see pages 7 through 9 of OMG document dtc/2010-12-05 Actions taken: December 11, 2009: received issue April 25, 2011: closed issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 23 Dec 2009 14:03:05 -0500 To: issues@omg.org, dss-ftf@omg.org From: Juergen Boldt Subject: issue 14856 -- DSS FTF issue This is issue # 14856 From: Tom Rutt DSS: single targetNamespace "urn:dss.hssp.org" 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? Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org