Is whitespace still an issue for signatures? - N-Infra #137

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: High
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • JSON
    • Hide

      Change: "JSON whitespace is not part of the contents of a resource. Applications MAY preserve the whitespace when handling resources, but are not required to do so. Note that digital signatures may depend on the whitespace"

      to: "JSON and XML whitespace (whitespace introduced for rendering purposes - aka "pretty printing") is not part of the contents of a resource. Applications MAY preserve the whitespace when handling resources, but are not required to do so. Note that digital signatures following [HL7's signature guidance] (section in data types on signatures & canonicalization) and using the defined canonicalization mechanisms will ignore formatting whitespace"

      Show
      Change: "JSON whitespace is not part of the contents of a resource. Applications MAY preserve the whitespace when handling resources, but are not required to do so. Note that digital signatures may depend on the whitespace" to: "JSON and XML whitespace (whitespace introduced for rendering purposes - aka "pretty printing") is not part of the contents of a resource. Applications MAY preserve the whitespace when handling resources, but are not required to do so. Note that digital signatures following [HL7's signature guidance] (section in data types on signatures & canonicalization) and using the defined canonicalization mechanisms will ignore formatting whitespace"
    • Rick Geimer/Eric Haas: 11-0-0
    • Correction
    • Non-substantive

      Comment:

      "Note that digital signatures may depend on the whitespace" - is this still true, or did we address it with canonicalization?

      Summary:

      Is whitespace still an issue for signatures?

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: