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

TEP 1.1 - TAB-1341: 5 Conformance - lack of specifics

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: EDXL-TEP
    • Labels:
      None
    • Environment:

      Conformance

    • Proposal:
      Hide

      Extract and list "additional mandatory requirements" that are not reflected and enforced by the XSD schema.

      Show
      Extract and list "additional mandatory requirements" that are not reflected and enforced by the XSD schema.
    • Resolution:
      Hide

      For consistency across the EDXL suite of standards and specifications, the additional manditory requirements will be detailed in the Constraints property of the data dictionary. The 5 Conformance section will be modified to clarify this point: "c) if its namespace name is "urn:oasis:names:tc:emergency:edxl:tep:1.0", then its content (which includes the content of each of its descendants) meets all the additional mandatory requirements provided in the specific subsection of Section 4 corresponding to the element’s name, as defined in Constraints".

      Show
      For consistency across the EDXL suite of standards and specifications, the additional manditory requirements will be detailed in the Constraints property of the data dictionary. The 5 Conformance section will be modified to clarify this point: "c) if its namespace name is "urn:oasis:names:tc:emergency:edxl:tep:1.0", then its content (which includes the content of each of its descendants) meets all the additional mandatory requirements provided in the specific subsection of Section 4 corresponding to the element’s name, as defined in Constraints".

      Description

      5 Conformance reads in part:

      " c) if its namespace name is "urn:oasis:names:tc:emergency:edxl:tep:1.0", then its content (which includes the content of each of its descendants) meets all the additional mandatory requirements provided in the specific subsection of Section 4 corresponding to the element’s name."

      Given the questions about "must," "should," etc. that is a bit vague.

      I don't recall seeing that many "additional mandatory requirements" beyond those of the schema (some co-occurrence constraints, etc.) so why not list them here with references (that's where the sections for elements would be handy).

      It will insure that all implementers get the same set of "additional mandatory requirements" which will improve the odds of interoperability and more importantly, adoption.

        Attachments

          Activity

            People

            • Assignee:
              pattiaymond Dr. Patti Aymond (Inactive)
              Reporter:
              pattiaymond Dr. Patti Aymond (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: