Hi Tim,
I think a good point was made on the Virtual Summit meeting notes, namely "No
reason why we cannot have multiple APIs, or even different implementations (and
let the best one win out in the end)".
As part of a previous project, we took that approach and created our own DSpace
API based
Hi all,
I will comment a few points as I am not able to attend the summit.
---
https://dev.twitter.com/docs - Twitter specifically has a basic REST
API, Search API, Streaming API, etc. They even do OAuth / AuthZ via REST
API.
---
I think this is a good idea. In some cases Twitter has multiple
Hi All,
Just wanted to follow up on this thread from a while back about the
question of using the "Sakai bus for the REST API". I think Bojan gave
a great description of why this decision was made initially.
However, it's worth mentioning that this topic came up in today's
discussion at our "
Hi Mark,
Am 07.02.2012 17:36, schrieb Mark van Harmelen:
> * Many exceptions are being caught and thrown away. We predict that in
> times of trouble this will make the API impossible to debug.
Many of the exceptions are related to handling of access rights of
request sender and some other
Dear list members
We have recently gained some concerns of a serious nature regarding the
REST API:
- Many exceptions are being caught and thrown away. We predict that in
times of trouble this will make the API impossible to debug.
- We suspect that the API may fail under conditions of
