-
Type:
Change Request
-
Resolution: Retracted
-
Priority:
Very High
-
FHIR Core (FHIR)
-
STU3
-
FHIR Infrastructure
-
Element
-
-
Clarification
Comment:
"This may be any string value that does not contain spaces." - So that means any unicode character? Tabs and line-breaks are ok? What about non-breaking spaces? Is that not likely to create challenges for some systems? Is there a good reason for leaving this so wide open? And we're comfortable with the <= 1MB too?
Summary:
Add constraints on Resource.id characters?
- is voted on by
-
BALLOT-6210 Affirmative - Ron G. Parker : 2018-Sep-FHIR R4 INFRASTRUCTURE
- Withdrawn