Re: [designinghypermediaapis] Add discussion to each page
- From:
- Martin Wawrusch
- Date:
- 2012-03-11 @ 09:45
Haha, lets hope so.
Here are some suggestions about content that is important to me:
* Versioning (or how to do it right by not doing it - your future chapter
14)
* Meta Information (I settled for the google discovery mechanism, which is
an extended json schema version) and meta schema discovery.
* Error handling - how to provide meaningful error messages in APIs. Seems
to be completely neglected.
* Ideas about smart client API libraries that are able to adapt to server
API changes.
* How to best model/implement (transactional) operations in the API.
* Relationship between hypermedia API and graphs (especially how to best
implement a graph for xxx. like people graph, health graph, interest graph).
* Common ontologies for schema designs.
Cheers
Martin
On Sun, Mar 11, 2012 at 1:02 AM, Steve Klabnik <steve@steveklabnik.com>wrote:
>
>
> Like I said, just testing the waters. I have a feeling more people
> will share your opinion. :)
>
> On Sun, Mar 11, 2012 at 9:58 AM, Martin Wawrusch <martin@wawrusch.com>
> wrote:
> > One of the problems with mailing lists is that they are completely out of
> > context, which is really ironic given that the whole book is about
> creating
> > hypermedia APIs :-)
> >
> > Anyways, great idea to write this book. Something like it is long
> overdue,
> > and given the sorry state of most APIs badly needed.
> >
> > On Sun, Mar 11, 2012 at 12:46 AM, Steve Klabnik <steve@steveklabnik.com>
> > wrote:
> >>
> >> Sorry about that! Yeah, I only got one email.
> >>
> >> I personally really dislike commenting systems, and find email a much,
> >> much better way to have these kinds of discussions. That said, I can
> >> see why some people like it, but I didn't want to add both at first,
> >> because that would fragment feedback.
> >>
> >> I'm keeping track of this kind of feedback, though, and if enough
> >> people ask, I'll add in a commenting system. Thanks for pinging me
> >> about it!
> >>
> >> On Sun, Mar 11, 2012 at 9:25 AM, Martin Wawrusch <martin@wawrusch.com>
> >> wrote:
> >> >
> >> > The system told me that the first email did not go through, so lets
> try
> >> > again. I think it would be extremely important to add something like
> >> > disqus
> >> > to each page. I want to give feedback, but frankly mailing lists are
> so
> >> > 80ies...
> >> >
> >
> >
> >
>
Re: [designinghypermediaapis] Add discussion to each page
- From:
- Steve Klabnik
- Date:
- 2012-03-11 @ 10:04
Awesome, great list. Versioning is super important, for sure, I plan
on doing both the unfinished articles as soon as I can. I'm at two
conferences this week, though, so I have lots of time on planes to
write.
Some other thoughts:
> * Ideas about smart client API libraries that are able to adapt to server
> API changes.
I'm experimenting with this:
http://github.com/steveklabnik/hateoas
https://gist.github.com/1870730
I haven't completed my experiment, but once I do, I plan on writing
about it. Client stuff is actually quite the hot topic right now, with
Darrell Miller's recent post on hypermedia client maturity models:
http://www.bizcoder.com/index.php/2012/03/07/hypermedia-client-maturity-model/
Also, this rest-discuss thread:
http://tech.groups.yahoo.com/group/rest-discuss/message/18602
> * How to best model/implement (transactional) operations in the API.
I wrote a little bit about this on my blog:
http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http