2015May core #1198 - Attachment.contentType has conflicting documentation

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology [deprecated]
    • Datatypes
    • 1.18.0.3
    • Hide

      fix the documentation so it is consitent with the formal definitions

      Show
      fix the documentation so it is consitent with the formal definitions
    • Eric Haas / Jean Duteau: 3-0-0
    • Correction
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: In Structure documentation: "Content in a format defined elsewhere

      It the Attachment has data, it SHALL have a contentType"

      contentType 0..1

      In description:

      "The contentType element SHALL always be populated. It can include charset information and other mime type extensions as appropriate. If there is no character set in the contentType then the correct course of action is undefined, though some media types may define a default character set and/or the correct character set may be able to be determined by inspection of the content."

      Proposed Wording: Make description agree with cardinaltiy and structure documentation

      Comment:

      Attachment.contentType is NOT required unless there is a url, but Attachment documentation conflicts

            Assignee:
            Unassigned
            Reporter:
            Jenni Syed
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: