-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
Canonical Resource Management Infrastructure (FHIR)
-
1.0.0-ballot2
-
Clinical Decision Support
-
Naming Conventions [deprecated]
-
3.1.1.1
-
-
Paul Denning/Jen Seeman: 14-0-1
-
Correction
-
Non-substantive
The guidance for constructing the canonical URL indicates that the resource name SHOULD be used instead of the id. It concedes that this is not typical, but suggests it is necessary since the id may change when the artifact is hosted in different environments.
I think the fact that the id may change during exchange is irrelevant, because the canonical never changes (even if the id does). Since the canonical is constructed at design-time, it reflects the original id – not the id after it has been exchanged.
IMO, it is better to either follow the established convention (SHOULD be constructed as {_}
{package-canonical-base}/{resource.resourceType}/{resource.id}{_}) or to not provide any guidance at all (which is only a little different since the SHOULD strength already requires consuming systems to expect anything). Recommending an approach that goes against convention seems to provide little value.
- is voted on by
-
BALLOT-58525 Affirmative - Paul Denning : 2024-Jan-FHIR IG CRMI E1 STU
- Balloted
-
BALLOT-59529 Affirmative - Mark Kramer : 2024-Jan-FHIR IG CRMI E1 STU
- Balloted
-
BALLOT-59533 Affirmative - Yunwei Wang : 2024-Jan-FHIR IG CRMI E1 STU
- Balloted