TEP 1.1 - TAB-1337: 5 Conformance - vagueness

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

      Conformance

    • Hide

      Make the requirements implied by 4.1 explicit and reference them directly from the conformance clause and not just section 4 in general.

      Show
      Make the requirements implied by 4.1 explicit and reference them directly from the conformance clause and not just section 4 in general.
    • Hide

      Modify the 5 Conformance section to clarify that "additional manditory requirements" are captured in the "Constraints" property of the data dictionary: "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".

      Add EDXL-DE 1.0 to the normative references.

      Show
      Modify the 5 Conformance section to clarify that "additional manditory requirements" are captured in the "Constraints" property of the data dictionary: "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". Add EDXL-DE 1.0 to the normative references.

      5 Conformance reads in part:

      "it meets the general requirements specified in Section 4;"

      It isn't clear what "general requirements" you have in mind.

      Do you mean:

      4.1 "Routing Header" Elements?

      Be aware that Emergency Data Exchange Language (EDXL) Distribution Element v1.0, http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf

      DOES NOT appear as a normative reference in 1.5 Normative References

      When you correct that, consider whether conformance requires the TEP Message to appear as the content of ContentObject in EDXL-DE and/or reference EDXL-DE to establish the requirements for another delivery mechanism to carry a TEP Message.

            Assignee:
            Dr. Patti Aymond (Inactive)
            Reporter:
            Dr. Patti Aymond (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: