Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25510

Need to set expectations for ER7 vs XML encoding when creating IGs

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive
    • Medium
    • V2+ Message Specification (V2)
    • Initial_Draft
    • V2 Mgmt Group
    • Conformance
    • Hide

      Proposed wording to add to the v2 Conformance document and for inclusion in the IGAMT authoring tool:  

       

      For use when XML encoding is not explicitly supported by the IG:

      The constraints and profiles described by this implementation guide are intended to be used with the message construction rules defined in Chapter 2 of the base standard (v2 pipe-delimited format). Use of this document for XML encoding is not explicitly supported. See the XML Encoding Rules for Version 2 Messages, Release 2 for additional details of XML encoding.

       

      For use when both XML and the standard encoding are supported by the IG:

      The constraints and profiles described by this implementation guide are intended to be used with both the message construction rules defined in Chapter 2 of the base standard (the common pipe-delimited format) and XML encoding. See the XML Encoding Rules for Version 2 Messages, Release 2 for additional details of XML encoding.

      Show
      Proposed wording to add to the v2 Conformance document and for inclusion in the IGAMT authoring tool:     For use when XML encoding is not explicitly supported by the IG: The constraints and profiles described by this implementation guide are intended to be used with the message construction rules defined in Chapter 2 of the base standard (v2 pipe-delimited format). Use of this document for XML encoding is not explicitly supported. See the XML Encoding Rules for Version 2 Messages, Release 2 for additional details of XML encoding.   For use when both XML and the standard encoding are supported by the IG: The constraints and profiles described by this implementation guide are intended to be used with both the message construction rules defined in Chapter 2 of the base standard (the common pipe-delimited format) and XML encoding. See the XML Encoding Rules for Version 2 Messages, Release 2 for additional details of XML encoding.
    • Clarification
    • Non-substantive

    Description

      Per the new v2 IG quality criteria IGs should indicate if they are expected to be implemented using ER7 and/or XML encoding. If XML encoding is expected, then additional requirements are added. Some combination of the Conformance methodology and/or authoring tools (IGAMT) should provide boilerplate verbiage for authors to use when declaring expected format types.

      Attachments

        Issue Links

          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              craig.newman Craig Newman
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: