${taskforce.name} Avatar
  1. OMG Task Force

hData REST Binding for RLUS 1.0 (hData) FTF — Open Issues

  • Key: HDATA
  • Issues Count: 2
Create Issue
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
HDATA-2 security negotiation through the use of custom HTTP headers Hdata 1.0 open
HDATA-1 separate the general RESTful pattern use from the hData specific features Hdata 1.0b1 open

Issues Descriptions

security negotiation through the use of custom HTTP headers

  • Key: HDATA-2
  • Legacy Issue Number: 18316
  • Status: open  
  • Source: LogMeIn, Inc ( Gerald Beuchelt)
  • Summary:

    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.

  • Reported: Hdata 1.0 — Thu, 13 Dec 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

separate the general RESTful pattern use from the hData specific features

  • Key: HDATA-1
  • Legacy Issue Number: 17375
  • Status: open  
  • Source: Anonymous
  • 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.
  • Reported: Hdata 1.0b1 — Sun, 20 May 2012 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT