Break out section on representing types - N-Infra #114

XMLWordPrintableJSON

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

      ok, fix.

      Show
      ok, fix.
    • Ewout Kramer/Josh Mandel: 8-0-0
    • Enhancement
    • Non-substantive
    • STU3

      Comment:

      "Where an element can have a choice of data types, or is a Reference these are represented by showing the common type (Reference or Type), and then showing the applicable data type names or resource types in a stereotype, separated by the | character. Type is not formally otherwise defined by this specification, but is a super type of all the data types."

      Move this to a separate section (it applies to all views) and revise as follows:

      The data type for a particular element is typically expressed as the name of the specified type with a hyperlink to its definition. However, there are two exceptions:

      • If the element supports multiple types (name ends with [x]), then the type will be a list of data type options, each separated by "|"
      • If one of the types is Reference or canonical, the data type might be followed by a list of allowed targets the reference is allowed to be. These might be resource names, data type names, or profile URLs, depending on the context. As well, the following symbols may appear that represent expectations of where the referenced resource is located and/or whether the reference is versioned: .....

      In profiles, references to types may be profiled - i.e. Instances of the element must comply with a specified profile or one of a list of profiles. The canonical URLs of any applicable profiles are listed inside {}.

      Summary:

      Break out section on representing types

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

              Created:
              Updated:
              Resolved: