- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 3 Jul 2013 17:00:01 +0200
- To: <public-hydra@w3.org>
On Monday, July 01, 2013 12:31 PM, Robin Berjon wrote: > Hi all, > > just a quick word of introduction. My name is Robin Berjon. I'm a web > hacker, mostly JS these days, and I've worked on a number of > standards-related projects. > > I'm interested in reducing the impedance mismatch between the primary > uses of data on the Web, which tend to involve interacting with some > form of database, editing in HTML forms, exposing APIs, generating > pages, validating, and in general munging data. Hence my curiosity in > Hydra. Wow.. that sounds ambitious. Not sure what to do about the database but "editing [the data] in HTML forms, exposing APIs, generating pages" is definitely what Hydra tries to do. In fact, most of it can already be found (still very rough though) in the Hydra Console: http://www.markus-lanthaler.com/hydra/ Data validation is certainly another thing I would like to see us discuss. > I'm a big fan of linked data in all parts except the RDF data model, > which I think is a mistake. (That should set the tone right from the > start. ;) Let's try to avoid such discussions as much as possible. I already have them way too often for my taste :-) > I have my own (personal, unfinished, experimental, etc.) hack that I've > been using mostly to think about this space, Web Schema: > > https://github.com/darobin/web-schema Could you briefly explain how this is different from other approaches and in what direction you would like to see that move? Do you think it would make sense to somehow link Hydra definitions to web-schemas? If so, how would you do that? Just by referencing a web-schema or by integrating the web-schema directly into a Hydra API description? -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 3 July 2013 15:00:37 UTC