Colleagues,
Please join me at 8am Pacific on Wednesday February 17, 2016 to
discuss your implementation of the HCLS dataset descriptions.
Join the call: https://www.uberconference.com/micheldumontier
Optional dial in number: 716-293-8697
PIN: 88433
Thanks!
m.
Michel Dumontier, PhD
Associate
but that is not the only way to get to a resource. There are many ways you
might get to something that might be a resource. A file, for instance. or
an attachment. Media types are used more widely than just in http headers
Grahame
On Wed, Feb 17, 2016 at 11:35 AM, James G. Boram Kim
wrote:
> Y
umm, there's no way to tell whether a URI represents a FHIR resource
Grahame
On Wed, Feb 17, 2016 at 11:26 AM, James G. Boram Kim
wrote:
> Hello all,
>
> Even though I don't have enough knowledge about FHIR RDF, I think sticking
> with the general media type is a better way than inventing some
hi David
So there's a few issues. The first is, given some rdf, is the only way to
find out whether it represents something worth treating as a FHIR resource
to actually parse it, and search it for FHIR resources? You seem to
think that the answer is yes
The second is, given some resources that d
I'm not familiar with the use of FOAF in this way - what does request URI
mean, where does it appear, , what's primary topic, etc?
thanks
Grahame
On Wed, Feb 17, 2016 at 9:07 AM, Martynas Jusevičius
wrote:
> I think it is better to rely on explicit relationships (properties)
> than on RDF type
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:
foaf:primaryTopic .
a fhir:AllergyInterance .
That way you can always get hold of your (FHIR) resource using
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 di
On Wed, Feb 17, 2016 at 6:27 AM, Martynas Jusevičius
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 RD
In what way can a piece of Turtle be a resource?
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
wrote:
> So how do you know that a piece of turtle is a resource? The theory of a
> restful
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 wrote:
> Hi Grahame,
>
> On today's call
> http://www.w3.org/2
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 y
Today's agenda will include FHIR RDF coordination about deliverables:
- Modify the FHIR spec build process to produce RDF artifacts -- Who
and how?
https://github.com/w3c/hcls-fhir-rdf/issues/7
- Downloadable FHIR ontology - Who maintains it and how?
https://github.com/w3c/hcls-fhir-rdf/is
12 matches
Mail list logo
