Remove "todos" from datatype content. - 2018-May Core Norm Infrastructure #31

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Datatypes
    • 2.23.0
    • Hide

      remove todo

      Show
      remove todo
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Non-substantive
    • STU3

      Existing Wording: The FHIR specification defines a set of data types that are used for the resource elements. There are four categories of data types:

      • Simple / primitive types, which are single elements with a primitive value (below)
      • General purpose complex types, which are re-usable clusters of elements (below)
      • Metadata types: A set of types for use with metadata resources (todo: provide link when pattern is defined)
      • Special purpose data types - defined elsewhere in the specification for specific usages

      ...

      base64: ... Todo: is it possible to impose an upper absolute limit on a base64Binary (for denial of service reasons, like on string)?

      Comment:

      There should not be a "todo" in normative content.

      Define pattern and provide link in intro.

      Resolve question and update on base64

      Summary:

      Remove "todos" from datatype content.

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

              Created:
              Updated:
              Resolved: