- From: Ioseb Dzmanashvili <ioseb.dzmanashvili@gmail.com>
- Date: Fri, 28 Jun 2013 02:59:39 +0400
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-hydra@w3.org
Hi folks, Little introduction of myself: I'm ioseb, i've been a software engineer for over a decade now. In different times i was developing desktop, web and mobile applications as well as distributed systems of various kinds. My initial interest in REST and hypertext was mainly related to my PhD work, though i actively started applying these concepts in real applications. Time after time i contribute to WebKit and V8 JavaScript engines and work on some RFCs(only successful one for the moment is RFC6861). What i expect from this group: - Due to my minimal knowledge in the field of linked data i hope to learn something new - I hope to do some valuable contributions to this group Additionally: > - support for binary data (this may be as simple as creating specialized > classes) +1 > - data validation (declarative description of the criteria for valid data, > can be used to generate client-side and server-side validation code) +1 except code generation. > - "single-click actions", i.e., operations which do not require any use > input, such as a "like". Typically, I consider such things an anti-pattern > in terms of a RESTful architecture but sometimes they are really handy +1 even though i was highly criticised on other mailing list for my attempt to "standardise" single-click actions[1] i'm still interested in this topic and hope to find non anti-pattern ways to use this concept . [1] http://tools.ietf.org/html/draft-ioseb-dzmanashvili-action-link-relation-00 Cheers, ioseb -- Ioseb Dzmanashvili AzRy LLC Software Architect #8, Chachava str. Tbilisi, 0159, Georgia Mobile: +(995) 99753388 github.com/ioseb twitter.com/iosebi On Thursday, June 27, 2013 at 8:20 PM, Markus Lanthaler wrote: > Hi folks, > > The group has now 15 participants and probably a few more lurking on the > mailing list, so let's get started. I think the best way to begin is to > briefly introduce ourselves and to discuss our goals in order to flesh out a > small roadmap. > > Some of you probably already know me through various related mailing lists > or my work on JSON-LD. I have been a Web developer for more than a decade > now. In the beginning I built small, static web sites but decided very early > on that something more dynamic is needed. So I developed my first CMS about > the time of Drupal's first release - who hasn't implemented a CMS? :-) Since > then I've programmed almost everything from microcontrollers on Smart Cards > in assembler up to large-scale distributed systems. > > More recently, not least due to my brilliant idea to do a PhD, I focused > more and more on RESTful services and Linked Data. The result of this > research is Hydra and JSON-LD (of which I'm one of the core designers and > co-editor of the specifications). My (truly humble) hope is that they will > form the base for a thriving ecosystem for machine-to-machine communication > just as HTML does for the human Web. > > In the long term, I envision Hydra as set of modular vocabularies - that's > the reason why I called the current spec "Hydra Core Vocabulary". There are > a couple of things I would like to explore, for example: > > - support for binary data (this may be as simple as creating specialized > classes) > > - authentication/authorization (including things like quotas and rate > limits) > > - data validation (declarative description of the criteria for valid data, > can be used to generate client-side and server-side validation code) > > - "single-click actions", i.e., operations which do not require any use > input, such as a "like". Typically, I consider such things an anti-pattern > in terms of a RESTful architecture but sometimes they are really handy > > Another thing I hope we can achieve is to simplify the core vocabulary even > further. > > > What are your goals? What are your pain points with current approaches? What > do you think is still missing in the current core vocabulary? > > > Cheers, > Markus > > > -- > Markus Lanthaler > @markuslanthaler
Received on Thursday, 27 June 2013 23:01:01 UTC