Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-42580

Explain canonical URL pattern

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot [deprecated]
    • Clinical Decision Support
    • Naming Conventions
    • 11.1
    • Hide

      The pattern is required for CQL libraries, since it's part of how CQL library resolution works, but we're also proposing it as a best practice for knowledge artifacts generally. The convention cannot be tied to the 'id' since that is context/site dependent, so we're proposing a pattern for canonical that ties to the name element as a best practice to help facilitate resolution and to provide consistency.

      We will add this documentation to the discussion.

      Show
      The pattern is required for CQL libraries, since it's part of how CQL library resolution works, but we're also proposing it as a best practice for knowledge artifacts generally. The convention cannot be tied to the 'id' since that is context/site dependent, so we're proposing a pattern for canonical that ties to the name element as a best practice to help facilitate resolution and to provide consistency. We will add this documentation to the discussion.
    • Floyd Eisenberg/Greg White: 13-0-0
    • Clarification
    • Non-substantive

    Description

      In my experience, artifacts rarely have an end that matches their name. Names are supposed to be UpperCamelCase. Most canonicals align with the 'id' in the package and usually are lower-case, lowerCamelCase or lower-dash-case. Also, not clear if this is setting rules or giving advice. (Or what the point of the advice is if it's not a rule)

      (Comment 40 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: