RLUS — EIS: single targetNamespace "urn:eis.hssp.org" is used

A single targetNamespace "urn:eis.hssp.org" is used in all of the following
machine readable files for the EIS submission, for both the wsdl and the schema used by the wsdl:

wsdl file swpEISMgmtAndQueryInterface.wsdl (platform dependent)
wsdl file swpEISAdminEditorInterface.wsdl (platform dependent)
wsdl file EISMgmtAndQueryInterface.wsdl (platform independent)
wsdl file EISAdminEditorInterface.wsdl (platform independent)
wsdl file EISMetaDataInterface.wsdl (platform independent)

Common wsdl:message definitions and schema definitions are repeated across several of the wsdl files. This will cause a maintenance headache. These should be pulled out into separate wsdl and/or xsd files which can be referenced by wsdl:import, xsd:import or xsd:include element in each of the 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?

At this time, change only the namespaces to adopt the OMG namespace conventions. The OMG EIS specification is part of HSSP project between HL7 and OMG. Further minor changes to the leading HL7 functional specification are anticipated and need to be incorporated by a follow-on RTF. Refactoring of the WSDL files to improve maintainability should be deferred and bundled with these anticipated changes to minimize disruption of already existing implementations of the current OMG EIS specification.