Re: Spec priorities

I agree, I have the similar pressing points.
We should focus to get a final draft out of the door.

Am 03.10.2015 um 09:55 schrieb Dietrich Schulten:
> Hi,
>
> I think we need Markus' help to sort out priorities and it would really
> make me happy to see us working on the things which stop me from using
> Hydra in my field.
>
> Our status, as I see it:
>
> - the hydra:pagedCollection discussion has stopped. It was a heated
> discussion with some casualties along the way over the question if the
> client should be able to request an arbitrary range or if the server
> should send fixed pages. I am willing to give up the range idea for the
> moment because I would rather see us move forward.
>
> These two really cause me trouble:
>
> - hydra:collection is not in the spec yet. Some open questions come to
> my mind: naming of the managed block, handling of situations where the
> managed subject or object does not exist yet and therefore cannot be named
> - description of expected request bodies with nested properties, allowed
> values, default values
>
> Best regards,
> Dietrich
>
> P.S: admittedly, the problem+json discussion was not one of my pressing
> practical problems. We do use problem+json, so I thought to make one
> last attempt to align both closely, and failed :-)
> I still hope to get a statement into the spec that hydra:Error should
> not be used to invent proprietary or overload existing http status codes.
>