- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 13 Apr 2015 10:56:38 -0400
- To: David Booth <david@dbooth.org>, w3c semweb HCLS <public-semweb-lifesci@w3.org>
- Message-ID: <552BD926.4000905@openlinksw.com>
On 4/13/15 10:31 AM, David Booth wrote: > FYI, in case some of you are not on the HL7 ITS list. > > -------- Forwarded Message -------- > Subject: RDF developments > Date: Sat, 11 Apr 2015 09:11:19 +1000 > From: Grahame Grieve <grahame@healthintersections.com.au> > Reply-To: Grahame Grieve <grahame@healthintersections.com.au> > To: HL7 ITS <its@lists.hl7.org> > > hi > > A few of us have put in a little background technical work to push the > development of an RDF format for FHIR along. As outcomes, we've produced > an RDF representation of the FHIR specification itself, the start of a > formal mapping to the RIM, and a serialization of the resources in RDF > consistent with that class definitions in the FHIR specification. > > You can see all this here: http://hl7-fhir.github.io/rdf.html > > This is all very draft; there's some open issues the RDF group has been > looking at which this work doesn't touch on (yet) and there's some open > issues in the page as well. Anyhow, this content is ready for people to > beat on, and for the RDF group to consider in depth. > > Grahame > > p.s. since I'm sure people will ask - where's the full examples? Well, > the answer is, that requires the development of code to do the > transform, and I'm holding off doing that until this has had a bit of > review - just to save myself some work. But here's a turtle example I > converted by hand from the basic example for the Flag resource: > > @prefix fhir: <http://hl7.org/fhir/> . > @prefix flag: <http://hl7.org/fhir/Flag.> . > > <http://hl7.org/fhir/Flag/example> a fhir:Flag; > flag:id "example"; > flag:text [ > fhir:Narrative.status fhir:narrative-status\#generated; > fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\">Large > Dog warning for Peter Patient</div>" > ]; > flag:category [ > fhir:CodeableConcept.coding [ > fhir:Coding.system <http://example.org/local>; > fhir:Coding.code "admin"; > fhir:Coding.display "Admin"; > ]; > fhir:CodeableConcept.text "admin" > ]; > flag:status fhir:flag-status.class\#active; > flag:patient [ > fhir:Reference.reference "Patient/example"; > fhir:Reference.display "Peter Patient"; > ]; > flag:author [ > fhir:Reference.reference "Practitioner/example"; > fhir:Reference.display "Nancy Nurse"; > ]; > flag:code [ > fhir:CodeableConcept.coding [ > fhir:Coding.system <http://example.org/local>; > fhir:Coding.code "bigdog"; > fhir:Coding.display "Big dog"; > ]; > fhir:CodeableConcept.text "Patient has a big dog at his home. > Always always wear a suit of armor or take other active counter-measures" > ]. Grahame, A few comments: [1] curl -I http://hl7-fhir.github.io/fhir.ttl -- returns Content-Type: application/octet-stream instead of Content-Type: text/turtle [2] curl -I http://hl7-fhir.github.io/fhir.rdf.xml -- returns Content-Type: text/xml instead of Content-Type: application/rdf+xml Correcting the issues above enables usability with existing Linked Open Data tools. For instance, I should be able to browse the data you've published at the aforementioned document locations, using existing Linked Open Data browsers. Note, I am note worried about Linked Open Data publication from your location, I am simply concerned about document content-type indication accuracy. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 13 April 2015 14:57:02 UTC