W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > February 2016

Re: Media type for FHIR RDF in Turtle

From: Martynas Jusevičius <martynas@graphity.org>
Date: Tue, 16 Feb 2016 23:07:10 +0100
Message-ID: <CAE35VmzDTpEH-GVEW3HheMo1LB+H5B1LRaZf7zKL=FWPY5EFrQ@mail.gmail.com>
To: David Booth <david@dbooth.org>
Cc: Grahame Grieve <grahame@healthintersections.com.au>, "its@lists.hl7.org" <its@lists.hl7.org>, w3c semweb HCLS <public-semweb-lifesci@w3.org>
I think it is better to rely on explicit relationships (properties)
than on RDF types.

E.g. if you dereference a document about allergy intolerance, then it
should explicitly say:

  <requestUri> foaf:primaryTopic <requestUri#intolerance> .
  <requestUri#intolerance> a fhir:AllergyInterance .

That way you can always get hold of your (FHIR) resource using request URI.

On Tue, Feb 16, 2016 at 11:02 PM, David Booth <david@dbooth.org> wrote:
> However, one thing the RDF does not do: it does not tell you the boundary of
> what is included in a document.  If a FHIR resource is represented in RDF,
> there is nothing explicit in it to indicate that the document contains all
> and only the RDF triples for that FHIR resource. This is a little different
> from the XML and JSON worlds, in which there is an explicit top element,
> with everything else nested inside.  But aside from that caveat, one should
> be able to look at the RDF triples to see that it contains a
> fhir:AllergyInterance resource, for example.
>
> Actually, I'm noticing that our current example is lacking the explicit
> mention of fhir:AllergyIntolerance, so I've raise an issue about that:
> https://github.com/w3c/hcls-fhir-rdf/issues/8
>
> David
>
> On 02/16/2016 03:11 PM, Grahame Grieve wrote:
>>
>> On Wed, Feb 17, 2016 at 6:27 AM, Martynas Jusevičius
>> <martynas@graphity.org <mailto:martynas@graphity.org>> wrote:
>>
>>     In what way can a piece of Turtle be a resource?
>>
>>
>> it represents a statement of the content of a fhir resource
>>
>> btw, I am presently using 'text/turtle; x-dialect=fhir', but I have no
>> particular feeling for this
>>
>> Grahame
>>
>>
>>     With RDF, you retrieve it and make rules that apply to the
>>     vocabularies used in it (properties, types etc).
>>
>>     On Tue, Feb 16, 2016 at 8:10 PM, Grahame Grieve
>>     <grahame@healthintersections.com.au
>>     <mailto:grahame@healthintersections.com.au>> wrote:
>>      > So how do you know that a piece of turtle is a resource? The
>>     theory of a
>>      > restful interface is that you make rules that apply to a mime
>>     type, but
>>      > evidently not in the case of rdf...
>>      >
>>      > Grahame
>>      >
>>      >
>>      > On Wednesday, 17 February 2016, David Booth <david@dbooth.org
>>     <mailto:david@dbooth.org>> wrote:
>>      >>
>>      >> Hi Grahame,
>>      >>
>>      >> On today's call
>>      >> http://www.w3.org/2016/02/16-hcls-minutes.html#action02
>>      >> we discussed what media type we should use for FHIR RDF
>>     serialized in
>>      >> Turtle.  The existing (generic) Turtle media type is text/turtle
>>     .  The
>>      >> consensus is that we should stick with that for FHIR in Turtle.
>>     Do you (or
>>      >> anyone else) see any problem in using that?  (And if so, what
>>     media type do
>>      >> you think we should use for FHIR in Turtle?)
>>      >>
>>      >> thanks,
>>      >> David Booth
>>      >>
>>      >>
>>      >>
>>
>> ***********************************************************************************
>>      >> Manage subscriptions - http://www.HL7.org/listservice
>>      >> View archives - http://lists.HL7.org/read/?forum=its
>>      >> Unsubscribe -
>>      >>
>>
>> http://www.HL7.org/tools/unsubscribe.cfm?email=grahame@healthintersections.com.au&list=its
>>      >> Terms of use -
>>      >> http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules
>>      >
>>      >
>>      >
>>      > --
>>      > -----
>>      > http://www.healthintersections.com.au /
>>     grahame@healthintersections.com.au
>>     <mailto:grahame@healthintersections.com.au> /
>>      > +61 411 867 065 <tel:%2B61%20411%20867%20065>
>>
>>
>>
>>
>> --
>> -----
>> http://www.healthintersections.com.au /
>> grahame@healthintersections.com.au
>> <mailto:grahame@healthintersections.com.au> / +61 411 867 065
Received on Tuesday, 16 February 2016 22:07:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 February 2016 22:07:54 UTC