Re: [Specifications] expectHeader usage (#212)

>Indeed, I looked at the HTML spec and apparently it's not in sync.
>I that listing is generated from the JSON-LD

Well, it should be that way. I'll have to figure it out why it's not working as it should.

>I'm also surprised that the properties only allow one value

In RDF you can always come with more value. As @tpluscode provided an example for JSON-LD, you're free to give a set of values. I'd be cautions with RDF lists though.

>I notice that the HTTP in RDF draft spec includes some header classes
> but I saw in another issue that there was some reluctance to use those definitions in Hydra.

We didn't want to stick to HTTP to much. Headers are concept existing in various scenarios thus it felt OK to have it reflected in hydra, but digging deeper within the HTTP specification seemed to much for a generic vocabulary.

>I've been looking for some documentation on the expected usage of the
>hydra:expectsHeader and hydra:returnsHeader properties, but to no avail.

No special examples were provided as it seemed these terms were pretty simple.
Each just gives a set of header names either expected or returned by an operation. No more, no less.
It's more of a union of all possible header names that can be expected or returned as final set may vary at runtime, depending on various circumstances (i.e. user priviledges, etc.).

Feel free to ask for more details - we'll try to address these requirements of yours.

-- 
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/212#issuecomment-621789447 using your GitHub account

Received on Thursday, 30 April 2020 12:02:03 UTC