Re: The state of hydra

> It is not an early stage project. Hydra is around since 2012. If it is
> not usable until now, I wonder if it will ever get there?
>
The draft can become a standard only with wide industry adoption. I think
that we are talking of a perspective of at least ~5-10 years, if we build
the right packages for the most popular languages in the next few years. I
suppose that the target is making Hydra become a standard for ~10-20% of
the installations around. Considering the current adoption and the public
tools available, we are still in an early phase, that is not so bad
considering the time span that Hydra should target. There are two possible
routes, both worthy: make vocabulary developers add Hydra to their spectrum
of tools; but also facilitate at most the use of Hydra for newly published
dataset that can link to existing ones. Hydra Ecosystem focuses on this
second option.


Actually it's me and two colleagues. But we cannot act in a vacuum, we
> need exchange and discussion with people working on the spec.
>
The best effort we can carry on at the moment is to publish as many OSS
tools and documentation as possible so people can experiment by themself as
you are. The real barriers (for new API developers) are not on Hydra
concepts but upstream for RDF and Semantic Web concepts. The specs (with
the addition of the use cases) are now pretty much self-explicative, maybe
we lack of examples about the use of `search` and `mapping` like the one on
this issue [0]; because of all the things said above, I would focus on
implementation matters as it is what we need at this point to move the
draft on.


> Best regards,
> Angelo
>
Best,

[0] https://github.com/HydraCG/Specifications/issues/171

>