Issues for Mailing list of the hData REST Binding for RLUS 1.0 (hData) Finalization Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 17375: separate the general RESTful pattern use from the hData specific features
Issue 18316: security negotiation through the use of custom HTTP headers

Issue 17375: separate the general RESTful pattern use from the hData specific features (hdata-ftf)

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.

Issue clarified – section 6.1.3 will need to be revised

We had identified a potential issue for a future hData RTF regarding the security negotiation through the use of custom HTTP headers. A future version of hData should use the WWW-Authenticate header instead of any X-hdata-* custom headers.