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

Re: Media type for FHIR RDF in Turtle

From: Grahame Grieve <grahame@healthintersections.com.au>
Date: Thu, 18 Feb 2016 11:47:57 +1100
Message-ID: <CAG47hGaRCkXdV0vw2ErSJQ8b_2s8FZXJTjMkqW+opYCJ2Y0mOQ@mail.gmail.com>
To: David Booth <david@dbooth.org>
Cc: "Eric Prud'hommeaux" <eric@w3.org>, "James G. Boram Kim" <james@snu.ac.kr>, Martynas Jusevičius <martynas@graphity.org>, "its@lists.hl7.org" <its@lists.hl7.org>, w3c semweb HCLS <public-semweb-lifesci@w3.org>
hi David

I think my comment may have created more concern than is warranted.  RDF
> does have named graphs, which we could use to delineate a certain set of
> triples.  But we haven't been doing that for FHIR RDF and I don't think it
> is needed either.  In practice, the FHIR resource that you get contains
> whatever data it contains, whether it's in XML, JSON or RDF. And if it
> somehow requires anything that isn't there, then it is non-conformant,
> whether it is XML, JSON or RDF.  If something is not there but not
> required, then that just means that the sender didn't include that
> information, whether it is in XML, JSON or RDF.  So I think the question of
> missing data boils down to a question of conformance, which would be the
> same whether it is in XML, JSON or RDF.

ok, fine. I can go with that.

and mine about how you know
>> where to start are probably more serious
> I think we addressed this on yesterday's 5pm call.  We decided to add a
> fhir:resourceType property (analogous to the JSON resourceType property),
> which would identify the starting instance data element (as its subject)
> and its FHIR resource type (as its value):
> https://www.w3.org/2016/02/16-hcls-minutes.html#resolution03

so you don't add this to contained resources, or resources in an entry in a

ok. I'll update my code.

Received on Thursday, 18 February 2016 00:48:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:21:56 UTC