OASIS Emergency Management TCIcon indicating the project type

OASIS Emergency Management TC

Uploaded image for project: 'OASIS Emergency Management TC'
  1. OASIS Emergency Management TC
  2. EMERGENCY-105

Solve the multi-schema import problem for each EDXL Schema

    Details

    • Proposal:
      Hide

      (1) Ideally, all of our schema should validate standalone in BOTH XMLSpy and Oxygen.
      (2) Any import statements in any of the schemas in our EDXL standards, where the imported schema isn't used, should be removed.
      (3) All imports should be local (so that everything validates standalone, i.e. disconnected from the web)
      (4) Only one schema file should be imported into one namespace.
      (5) Make a RIM recommendation to the EMTC that the EMTC "Require that any new EDXL standard have a zip with a standardized folder structure, including "schema", "ImportedSchema","examples", and "Require that everything in the zip file must be tested to validate with BOTH XMLSpy and Oxygen"

      Show
      (1) Ideally, all of our schema should validate standalone in BOTH XMLSpy and Oxygen. (2) Any import statements in any of the schemas in our EDXL standards, where the imported schema isn't used, should be removed. (3) All imports should be local (so that everything validates standalone, i.e. disconnected from the web) (4) Only one schema file should be imported into one namespace. (5) Make a RIM recommendation to the EMTC that the EMTC "Require that any new EDXL standard have a zip with a standardized folder structure, including "schema", "ImportedSchema","examples", and "Require that everything in the zip file must be tested to validate with BOTH XMLSpy and Oxygen"

      Description

      The practice of allowing multiple imports of external helper schema supporting the main schema of EDXL specifications has led to problems with duplication and with missing imports from imported schema that are not available locally. These problems are exacerbated by differences in the way xml parsers handle imported schema.

        Attachments

          Activity

          Hide
          Permalink
          rexbrooks Rex Brooks added a comment -

          The Proposal comes from Jeff Waters, but I (Rex Brooks) support it. We will start by correcting the problem with EDXL-CT (Common Types) then use that corrected version along with appropriate corrections to EDXL-DE-v2.0. Then we will apply the changes to each of the EDXL specifications to achieve a fully harmonized suite of specifications. This also applies to any specifications still in process, such as EDXL-HAVE-v2.0.

          We will track this effort through the RIM SC so as not to constantly be re-activating older SCs.

          Show
          rexbrooks Rex Brooks added a comment - The Proposal comes from Jeff Waters, but I (Rex Brooks) support it. We will start by correcting the problem with EDXL-CT (Common Types) then use that corrected version along with appropriate corrections to EDXL-DE-v2.0. Then we will apply the changes to each of the EDXL specifications to achieve a fully harmonized suite of specifications. This also applies to any specifications still in process, such as EDXL-HAVE-v2.0. We will track this effort through the RIM SC so as not to constantly be re-activating older SCs.

            People

            • Assignee:
              rexbrooks Rex Brooks
              Reporter:
              rexbrooks Rex Brooks
            • Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: