W3C home > Mailing lists > Public > public-hydra@w3.org > December 2016

an architectural diagram

From: Ruben Verborgh <Ruben.Verborgh@UGent.be>
Date: Fri, 30 Dec 2016 19:08:48 +0000
To: Hydra <public-hydra@w3.org>
Message-ID: <127BADFE-DE31-429C-8E6D-73EFE9A6DEB8@ugent.be>
Dear all,

Discussions on this list have brought a lot of knowledge,
most of which was not available when Hydra was first designed.
An architectural diagram allows us to take a step back,
and to re-design Hydra now that we better know what we need.

I have tried to create a high-level diagram
of the topics we aim to tackle and how they relate.
You can find the source code and resulting diagram here:

This is a work in progress and still requires your input,
in the form of replies, issues, pull requests, etc.

I have split the diagram in two large packages.
The first one concerns the modeling of an API's structure
(which an API would typically send as a separate document).
The second one concerns the description of hypermedia controls
(which an API would typically send as part of a representation).

Another purpose of the diagram is to allow us to divide the work:
there are clear parts that can be considered separately (at first),
and these could perhaps be part of different draft documents.

Please check whether you think this makes sense,
and if all parts are there and are meaningful.

Best regards,

Received on Friday, 30 December 2016 19:09:29 UTC

This archive was generated by hypermail 2.3.1 : Friday, 30 December 2016 19:09:30 UTC