>> "If we want the RDF to be an equal sibling to xml and JSON then
round tripping needs to be signature safe."
�
David..
�
Lloyd's comment points out the need for a significant and non-trivial
"uptick" in the level of care that will have to be taken when generating RDF.
�
I certainly haven't been to every single FHIR RDF meeting (so please
correct me if I'm wrong), but I don't recall "signature safety" being discussed
much (if at all) when we've discussed aspects of round tripping.
�
TJL
�
---------------------------- Original Message ----------------------------
Subject: Re: Question on FHIR references - relative and absolute URIs
From: "Lloyd McKenzie" <[email protected]>
Date: Tue, April 26, 2016 3:00 pm
To: "Grahame Grieve" <[email protected]>
Cc: "David Booth" <[email protected]>
"[email protected]" <[email protected]>
"w3c semweb HCLS" <[email protected]>
--------------------------------------------------------------------------
> If we want the RDF to be an equal sibling to xml and JSON then round
> tripping needs to be signature safe. At the moment, that means retaining
> absolute vs. relative references.
>
> On Tuesday, April 26, 2016, Grahame Grieve <
> [email protected]> wrote:
>
>> well, this is tricky. technically, it's not strictly required, but it's a
>> lossy transform (lossy in both ways, in fact). One of the attractions of
>> fhir;reference for me is that you can have an absolute reference for RDF
>> and preserve the original fhir url
>>
>> Grahame
>>
>>
>> On Wed, Apr 27, 2016 at 3:01 AM, David Booth <[email protected]
>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>>
>>> Grahame and/or Lloyd,
>>>
>>> In today's FHIR RDF teleconference, a question came up about relative and
>>> absolute URIs in FHIR references.
>>>
>>> Must absolute and relative references be round tripped as is? I.e., do
>>> we need to maintain the distinction between relative and absolute
>>> references when round tripping, or can relative URIs be turned into
>>> absolute URIs and vice versa?
>>>
>>> I did not see any mention of normalizing references in the discussion of
>>> Canonical JSON:
>>> https://hl7-fhir.github.io/json.html
>>>
>>> Thanks,
>>> David Booth
>>>
>>>
>>
>>
>> --
>> -----
>> http://www.healthintersections.com.au / [email protected]
>> <javascript:_e(%7B%7D,'cvml','[email protected]');> /
>> +61 411 867 065
>>
>>
>> ***********************************************************************************
>> Manage your subscriptions <http://www.HL7.org/listservice> | View the
>> archives <http://lists.HL7.org/read/?forum=its> | Unsubscribe
>> <http://www.HL7.org/tools/[email protected]&list=its>
>> | Terms of use
>> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules>
>>
>
>
> --
>
> *Lloyd McKenzie*, P.Eng.
> Senior Consultant, Information Technology Services
> Gevity Consulting Inc.
>
> E: [email protected]
> M: +1 587-334-1110 <1-587-334-1110>
> W: gevityinc.com
>
>
> *GEVITY**Informatics for a healthier world *
>
> CONFIDENTIALITY – This communication is confidential and for the
> exclusive
> use of its intended recipients. If you have received this communication by
> error, please notify the sender and delete the message without copying or
> disclosing it*.*
>
> NOTE: Unless explicitly stated otherwise, the opinions and positions
> expressed in this e-mail do not necessarily reflect those of my employer,
> my clients nor the organizations with whom I hold governance positions
>
> ***********************************************************************************
> Manage subscriptions - http://www.HL7.org/listservice
> View archives - http://lists.HL7.org/read/?forum=its
> Unsubscribe -
> http://www.HL7.org/tools/[email protected]&list=its
> Terms of use - http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules
