Uploaded image for project: 'Technical Advisory Board'
  1. Technical Advisory Board
  2. TAB-1221

Note in 5 Conformance

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0 CSPRD01
    • Fix Version/s: None
    • Component/s: Public reviews
    • Labels:
      None
    • Environment:

      Normative

    • Proposal:
      Hide

      Create a conformance clause that offers alternative ways to conform to the standard and be specific about what each type of conformance requires. Don't point to the schema and say be valid. Specified combinations are better for interoperablity.

      Show
      Create a conformance clause that offers alternative ways to conform to the standard and be specific about what each type of conformance requires. Don't point to the schema and say be valid. Specified combinations are better for interoperablity.

      Description

      From the note:

      "only messages that fully comply with the EDXL-HAVE 2.0 specification and that are complete and schematically valid may be referred to as a “EDXL-HAVE 2.0 Message”."

      only -> Only

      "fully comply?" Not defined.

      "that are complete..." Not defined.

      "may" - is this a requirement?

      Is conformance something separate from being complete and schematically valid?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              patrick Patrick Durusau
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: