Hi, Hydra suffers from the same problem as REST (the original architectural concept, not the label loosely applied to anything using HTTP ;) It solves a problem most developers don’t have, in a way that’s harder to adopt, and with less tooling than the alternatives. Perhaps the advent of the "agentic web" (whatever that term ultimately comes to mean) could shift the demand. But that would also require rethinking the specification, evolving the core concepts, and adapting them to better reflect today’s realities and our expectations for the near future. Best regards, Filip https://www.linkedin.com/in/filipkolarik/ On Wed, May 21, 2025 at 12:28 AM Asbjørn Ulsberg <asbjorn@ulsberg.no> wrote: > On 21 May 2025, at 00:15, Judson Lester <nyarly@gmail.com> wrote: > > > I've been experimenting with Hydra in my side projects and am mostly > finding it to be a good framework for REST, JSON-LD, and RDF. I'd like to > see some changes to the specification, although from what I understand > they'd take significant changes to make work. I have time and inclination > to participate in discussion and write documentation, > > I’m glad to hear! > > > Are any of the original WG members available to continue the work? > > I would love to see the CG invigorated, and continue the ongoing > discussions in the open issues on GitHub. > > https://github.com/HydraCG/Specifications/issues > > > I feel like there'd be a lot of value in continuity there. > > Agreed! > > -- > Asbjørn Ulsberg. -=|=- asbjorn@ulsberg.no > «He's a loathsome offensive brute, yet I can't look away» > > > >
Received on Tuesday, 20 May 2025 22:42:22 UTC