resource seems ambiguous: could refer to the system or to the instance representation. It might be possible to adopt a terminology to preserve the distinction. - 2018-May Core Norm Conformance #57

XMLWordPrintableJSON

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

      clarify this as suggested.

      Show
      clarify this as suggested.
    • Rob Hausam/Carmela Couderc: 16-0-0
    • Non-substantive
    • STU3

      Existing Wording: content - "How much of the content of the code system - the concepts and codes it defines - are represented in this resource."

      Proposed Wording: How much of the content of the code system - the concepts and codes it defines - are represented in this resource instance.

      Comment:

      "resource" seems ambiguous: could refer to the system or to the instance representation. It might be possible to adopt a terminology to preserve the distinction.

      This is not a request to adopt a 303 URI forwarding approach to distinguish the real-world resource from its representation; it turns out that if we adopt the term "resource instance" whenever referring to an instance, which I recommend to disitinguish it from the "resource definition," then we have the added benefit of avoiding confusion with the real-world referent.

      Summary:

      resource seems ambiguous: could refer to the system or to the instance representation. It might be possible to adopt a terminology to preserve the distinction.

            Assignee:
            Unassigned
            Reporter:
            Jay Lyle
            Jay Lyle
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: