Why use URLs instead of URNs? - 2016-09 core #51

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Terminology Infrastructure
    • Terminologies
    • 4.2.0 code systems
    • Hide

      URLs are much more implementer friendly than OIDs or GUIDs and are less subject to transcription and other errors. Plus they have the benefit of resolvability. As well, a large part of the FHIR community does not have the legacy of the use of OIDs and should not be forced to mount that learning curve. Finally, URLs are typical in RESTful and semantic web technologies with which FHIR is trying to align. Implementers are not prohibited from using URNs for content they control, but should think seriously about the trade-off between short-term mapping costs and long term maintenance/implementation costs

      Show
      URLs are much more implementer friendly than OIDs or GUIDs and are less subject to transcription and other errors. Plus they have the benefit of resolvability. As well, a large part of the FHIR community does not have the legacy of the use of OIDs and should not be forced to mount that learning curve. Finally, URLs are typical in RESTful and semantic web technologies with which FHIR is trying to align. Implementers are not prohibited from using URNs for content they control, but should think seriously about the trade-off between short-term mapping costs and long term maintenance/implementation costs
    • Ted Klein/Grahame Grieve: 6-0-0
    • Clarification

      Comment:

      Many code systems alreay have URNs. Why is it necessary to invent another set of identifiers (FHIR URIs) to maintain and map to? Is there an assumption that all system identifiers should also be URLs to support service identification? If not, use the identifiers that already exist.

      Summary:

      Why use URLs instead of URNs?

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

              Created:
              Updated:
              Resolved: