Issue 17375: separate the general RESTful pattern use from the hData specific features (hdata-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: The specification as it is describes a particular pattern of use
that includes
aspects that are specific to hData. It would help us greatly to separate the
general RESTful pattern use from the hData specific features; this way, we could
reference the specification directly and it would be clear how we
could conform to it.


Resolution: 
Revised Text: 
Actions taken:
May 20, 2012: received issue
Discussion: 
Issue clarified – section 6.1.3 will need to be revised
End of Annotations:=====
M-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:cc:content-type:content-transfer-encoding;
        bh=RUsFF05TKHRKKFjWfzyZybpEznS7nFClSG3Hj2ARqSY=;
        b=VSZMiqwFDIg9E1/XNeXowoslxp6QCUYuISJRXQdhPmk9QsWftsms+mIivRQStxZCof
         ZtTkfaIJo3TUTBOqreWHFEK1UMRiFmDzirFqQkahs4Ct3q4V++mgDWEvhvUxzOO3SIqq
         O+N7Z7biorZG0e+CW7HrDeHuMDH7AmhddX/E8lJFyTsaAWRSgDzkOXvGDLOfqTH1bQQ8
         tm8jNlLUStjCUEE3yf6cNKDAwIiu3Yi645dGbijDIEA6spLqIV8tyy4sb7CKI18vw/s1
         CGEEDNwbNc4MMVIS7BCQoKD+tvEQT8RwtW6nEtEbMEaorL24PJibwaNpx5LUkA1xIE03
         2K0w==
Sender: grahameg@gmail.com
Date: Mon, 21 May 2012 13:35:04 +1000
X-Google-Sender-Auth: kclp1kfOO2QcAkq_OHdlQZr-CGA
Subject: FHIR: Several Issues with OMG hData RESTful Transport to support an
 alternative realization of the RLUS PIM
From: Grahame Grieve <grahame@healthintersections.com.au>
To: issues@omg.org
Cc: Ewout Kramer <e.kramer@furore.com>,
        "Beuchelt, Gerald" <beuchelt@mitre.org>
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id q4L3ZD9R024175


Dear OMG


We (Ewout Kramer and myself) are technical leads on the HL7
FHIR project (http://www.hl7.org/fhir), which is a very practically
orientated specification that has a RESTful component that overlaps
somewhat with hData. The overlap occurs in two different ways:


* FHIR uses a RESTful paradigm, and defines patterns of logical
  use of HTTP
* FHIR defines resource content that would be useful to use in
  hData - and hData is a useful way to use them


With regard to the first point, we believe that it would be useful for
the hData protocol and FHIR to use the same patterns of usage for
HTTP. this email identifies several issues where we believe that the
hData restful transport specification could be improved, that would
mean that we could act in harmony and refer to the OMG specification
directly. With regard to the second, we will continue to work with the
authors of hdata on that point.


Both hData and FHIR are realizing a RESTful resource-centric architecture
that implements the RLUS service functional model and the OMG PIM. In order to
ensure a single implementation strategy and strengthen the overall
technical quality
of the specification, we request to consider the following changes to
the OMH hData
specification:


1. The specification as it is describes a particular pattern of use
that includes
aspects that are specific to hData. It would help us greatly to separate the
general RESTful pattern use from the hData specific features; this way, we could
reference the specification directly and it would be clear how we
could conform to it.