Meeting minutes
DICOM
detlef: Re UIR for private elements. I put a proposal in issue 145
… I think you can just use the element name. Create a URI from these two elements.
… But to search it, you need to go back to the private creator ID and the ID of that element.
… But since we don't use the URI for anything else, it's okay.
erich: I'll try that in my code.
detlef: I'll be out next week.
detlef: then I'll be out until returning Aug 21.
Issue 120
ericP: Both uri and canonical primitive datatypes extend URI.
dbooth: We realized that generating a fhir:link shoudl happen every time a primitive URI type is generated.
ericP: There is still an asymmetry because REference is s composite datatype, but canoncial is a primitive datatype.;
tim: This is where fhir:link is used (as different properties with the same name)
"TestScript.metadata.capability.link: Links to the FHIR specification" ,
"GraphDefinition.link: Links this graph makes rules about" ,
"DeviceDefinition.link: An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device" ,
"Person.link: Link to a resource that concerns the same actual person" ,
"Bundle.entry.link: Links related to this entry" ,
"Bundle.link: Links related to this Bundle" ,
"DiagnosticReport.media.link: Reference to the image or data source" ,
"TestScript.metadata.link: Links to the FHIR specification" ,
"Patient.link: Link to a Patient or RelatedPerson resource that concerns the same actual individual" ,
"URI of a reference" .
tim: If you are adding an RDF fhir:link, you should not do it where the other kind of link is used.
ericP: How about calling it fhir:n instead of fhir:link?
jim: Here is an example generated from the current code I think: https://
fhir:medication [
fhir:reference [
fhir:reference [ fhir:v "#med0303" ] ; # Linked to a RESOURCE Medication
fhir:display [ fhir:v "Alemtuzumab 10mg/ml (Lemtrada)" ]
]
] ; #
dbooth: If we put our fhir:link directly under capital R Reference, then there is the possibility that the other FHIR folks could put their own link property there, and we would have a clash.
… If so, could we distinguish them by type?
jim: Need to put the version in the query string for fhir:canonical
AGREED: generate a fhir:link as a sibling of fhir:v in each primitive uri object.
AGREED: as a special case, the version needs to be moved to a query string in canonical
ericP: I'll also proto the fhir:n option
169 Make R5 (and R6) HAPI parser/serializer for FHIR RDF easier to find
ericP: I was waiting until the shex and example fixes were done.
… I'll make the PR after those are done, to get the right version into HAPI
tim: The java core library does this to produce the spec. Does HAPI use the core one?
ericP: No, they do two different things. The one for the spec does pretty printing, keeping comments, etc.
jim: The core parser does not parse any more. Not used. It only serializes.
jim: There are round trip tests for RDF, but they're disabled.
dbooth: We should make sure the HAPI round tripping works.
ericP: It parses JSON, serializes as turtle, parses as turtle. Then it compares both of those objects for equality.
… It failed on a bunch of things because of the core POJOs regarding contained. The operator equals test requires the same order of elements in a list.
… But that is fixed now by James Agnew.
tim: Issue for next week maybe w3c/
ADJOURNED