How does swagger-spec relate to hyper-media schema?

It seems to me that several swagger properties are actually implemented into the hyper-media schema but with different conventions (e.g. links [0]) . I’m wondering what are the reasons to use proprietary specifications (i.e. what swagger does and hyper-media can’t ).

[0] http://json-schema.org/latest/json-schema-hypermedia.html#anchor35

[handrews]

@ePaul @themihai if you are still interested in this, I am on the verge of publishing draft-07 of Hyper-Schema

This includes several new features including for working with request and response headers and content negotiation. It also has a top-to-bottom rewrite to explain its purpose more clearly, and generally read better. You might find the new introduction and overview to be relevant.

Hyper-Schema and OpenAPI are definitely looking at slightly different problems. If Hyper-Schema draft-07 is well-received, it may be worth looking at whether and how they might fit together. But it’s probably best for Hyper-Schema needs to prove itself useful (or not) on its own first.

[silkentrance]

I think that this is basically a data modelling issue. Whether or not your data supports the hyper-schema is up to the developer of the api. Of course, it would be nice to have a common set of mixins that one could use to model one’s data types, e.g.

components:
  Foo:
   allOf:
     - type: hyper-schema-object
     - type: object
        ...

The hyper-schema-object then could be a built-in of and also a hint to the code generators when generating required code.

I just found out that over at Swagger they already have something like that https://swagger.io/docs/specification/links/