Canonical URI approach seems to overlap with Identifier data type - 2018-May Core Norm Infrastructure #3

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • References
    • 2.3.0.4
    • Hide

      The canonical datatype not only identifies conformance resources (which is indeed an overlap with uri or Identifier), but also makes explicit that elements marked as canonical have certain kinds of behaviour (they resolve to .url element of conformance resources, you can chain over them in a search, etc). We'd like this to remain explicit, and using Identifier would no longer do that.

      We appreciate the fact that this explanation cannot easily be understood from the spec, and that it is worth adding some wording of explanation around it. Also, the definition at, say, StructureDefinition.url (and other conformance structures) does not mention "canonical" but talks about "logical", it would be good te rephrase this as well to clarify.

      Show
      The canonical datatype not only identifies conformance resources (which is indeed an overlap with uri or Identifier), but also makes explicit that elements marked as canonical have certain kinds of behaviour (they resolve to .url element of conformance resources, you can chain over them in a search, etc). We'd like this to remain explicit, and using Identifier would no longer do that. We appreciate the fact that this explanation cannot easily be understood from the spec, and that it is worth adding some wording of explanation around it. Also, the definition at, say, StructureDefinition.url (and other conformance structures) does not mention "canonical" but talks about "logical", it would be good te rephrase this as well to clarify.
    • Isaac Vetter/Lloyd McKenzie: 11-0-1
    • Clarification
    • Non-substantive
    • STU3

      Comment:

      The canonical URI approach seems to overlap with the Identifier data type (2.26.0.11 Identifier) which provides a sever independent identification of a resource.

      The main difference seems to be the version indication which could be added as a optional field.

      Summary:

      Canonical URI approach seems to overlap with Identifier data type

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: