Provide consistent use of markup/string - 2018-May Core Norm Infrastructure #48

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: High
    • FHIR Core (FHIR)
    • STU3
    • Modeling & Methodology
    • Datatypes
    • Hide

      Guideline is that we use 'string' unless someone provides a use-case for markdown. xhtml is limited to Narrative only.

      We will document (in substantive change section and notes on markdown data type) that converting string to markdown is not considered a breaking change for non-choice data types. (And adding markdown as an allowed choice in choice data types is also not a breaking change.) I.e. we reserve the right to support markdown for additional string elements in the future.

      Show
      Guideline is that we use 'string' unless someone provides a use-case for markdown. xhtml is limited to Narrative only. We will document (in substantive change section and notes on markdown data type) that converting string to markdown is not considered a breaking change for non-choice data types. (And adding markdown as an allowed choice in choice data types is also not a breaking change.) I.e. we reserve the right to support markdown for additional string elements in the future.
    • Ron Shapiro/Grahame Grieve: 2-0-0
    • Non-substantive
    • STU3

      Comment:

      It isn't clear why string, markdown and xhtml elements have been selected when they have. We should review current use, establish a consistent policy, and apply throughout.

      Summary:

      Provide consistent use of markup/string

            Assignee:
            Unassigned
            Reporter:
            Elliot Silver
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: