Should Resource cardinality be 1..1? - N-Infra #94

XMLWordPrintableJSON

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

      The cardinality shows as 1..1, but this differs from the cardinality in profiles-types.xml, and as the submitter states, other cardinalities are used at different places in the specification.

      Therefore, correct the cardinality of Resource and DomainResource to 0..*.

      Show
      The cardinality shows as 1..1, but this differs from the cardinality in profiles-types.xml, and as the submitter states, other cardinalities are used at different places in the specification. Therefore, correct the cardinality of Resource and DomainResource to 0..*.
    • Rick Geimer/Sean McIlvenna:9-0-0
    • Clarification
    • Non-substantive
    • STU3

      Comment:

      Are we sure the base cardinality for Resource, DomainResource, etc. should be 1..1? The reference Parameters.parameter.resource is 0..1 which would seem to violate this.

      Summary:

      Should Resource cardinality be 1..1?

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

              Created:
              Updated:
              Resolved: