[OASIS Issue Tracker] (EMERGENCY-98) TEP 1.1 - TAB-1328: Schema and namespace import issues

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Patti Aymond created EMERGENCY-98:
-------------------------------------

             Summary: TEP 1.1 - TAB-1328: Schema and namespace import issues
                 Key: EMERGENCY-98
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-98
             Project: OASIS Emergency Management TC
          Issue Type: Bug
          Components: TEP
         Environment: References
            Reporter: Patti Aymond
            Assignee: Patti Aymond
            Priority: Critical


While tracking down namespace issues I encountered in http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/xsd/edxl-tep-v1.1.xsd: 

<xsd:schema targetNamespace="urn:oasis:names:tc:emergency:EDXL:TEP:1.1" elementFormDefault="qualified"><xsd:import namespace="urn:oasis:names:tc:emergency:edxl:ct:1.0" schemaLocation="./supportingElements/edxl-ct-v1.0-csd06/edxl-ct-v1.0.xsd"/><xsd:import namespace="urn:oasis:names:tc:emergency:edxl:ciq:1.0:xal" schemaLocation="./supportingElements/edxl-ciq-v1.0-csd04/edxl_xAL.xsd"/><xsd:import namespace="urn:oasis:names:tc:emergency:edxl:extension:1.0" schemaLocation="./supportingElements/edxl-ext-v1.0/edxl-ext-v1.0.xsd"/> 

The default namespace reads: urn:oasis:names:tc:emergency:EDXL:TEP:1.1, shouldn't that read: 

urn:oasis:names:tc:emergency:EDXL:1.1:TEP ? 

The first and second namespaces, are references to committee drafts. 

BTW, shouldn't namespace="urn:oasis:names:tc:emergency:edxl:ct:1.0" 

read: namespace="urn:oasis:names:tc:emergency:edxl:1.0:ct"? 

And, namespace="urn:oasis:names:tc:emergency:edxl:extension:1.0" 

should read: namespace="urn:oasis:names:tc:emergency:extension:1.0:edxl" ? 

If you follow the link for supporting elements you will find: 

***** 
edxl-ciq-v1.0-csd04/ 04-Aug-2015 16:00 - 
edxl-ct-v1.0-csd06/ 04-Aug-2015 16:00 - 
edxl-ext-v1.0/ 04-Aug-2015 16:00 - 
edxl-gsf-v1.0-csd02/ 04-Aug-2015 16:00 - 
***** 

Following the first namespace import, ./supportingElements/edxl-ct-v1.0-csd06/edxl-ct-v1.0.xsd"/, you find: 

edxl-ct-v1.0.xsd 04-Aug-2015 16:00 13k 

Following that: 

<xs:import namespace="urn:oasis:names:tc:emergency:edxl:ciq:1.0:xpil" schemaLocation="edxl_xPIL.xsd"/><xs:import namespace="urn:oasis:names:tc:emergency:edxl:ciq:1.0:xal" schemaLocation="edxl_xAL.xsd"/><xs:import namespace="urn:oasis:names:tc:emergency:edxl:gsf:1.0" schemaLocation="edxl-gsf.v1.0.xsd"/> 

OK, but notice that the last namespace is incorrectly formed: 

urn:oasis:names:tc:emergency:edxl:gsf:1.0 

Should read: urn:oasis:names:tc:emergency:edxl:1.0:gsf 

*AND* the listing of the schema location files, edxl_xPIL.xsd, edxl_xAL.xsd, edxl-gsf.v1.0.xsd, implies that they occur in the same directory. Yes? 

But, if you back off the URL to: docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/xsd/supportingElements/edxl-ct-v1.0-csd06/ and press return, you will find: 

Parent Directory 
edxl-ct-v1.0.xsd 04-Aug-2015 16:00 13k 

That's what you call a fatal error, file not found. 

************************************************* 

For the second namespace: 

supportingElements/edxl-ct-v1.0-csd06/edxl-ct-v1.0.xsd" 

leads to: edxl-ct-v1.0.xsd 04-Aug-2015 16:00 13k 

Which is the same file as invoked for the first namespace and it shares the same errors. 

**************************************************** 

The third namespace was invoked from: ./supportingElements/edxl-ext-v1.0/edxl-ext-v1.0.xsd"/ 

which invokes a namespace: 

<xs:import namespace="urn:oasis:names:tc:emergency:edxl:ct:1.0" schemaLocation="./edxl-ct-v1.0-wd05.xsd"/> 

Err, again, the namespace error: urn:oasis:names:tc:emergency:edxl:ct:1.0 which should read: 

urn:oasis:names:tc:emergency:edxl:1.0:ct 

Not to mention that if you back off to: docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/xsd/supportingElements/edxl-ext-v1.0/ 

the referenced schema is no where to be found. 

The directory lists: edxl-ext-v1.0.xsd 04-Aug-2015 16:00 2k only. 

Apologies for the verboseness of this comment but it is difficult to be clear about namespaces even in real time, full bandwidth conversations, much less in comments. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)