On Oct 28, 2009, at 3:24 AM, Asger Askov Blekinge wrote:
> Hi
>
> Yes, the return values, both codes and format of return need to be
> more
> tightly specified. I have not decided if it should return xml or just
> simple lists.
>
> What I would like is for the /objects/{pid}/datastreams to return a
> list
> like
> /objects/{pid}/datastreams/{dsid1}
> /objects/{pid}/datastreams/{dsid2}
>
> so that you can follow the "links" directly
Sounds good, so a successful GET to /objects/{pid}/datastreams would
return a 300 multiple-choices and enumerate the dsids in some format.
I agree it would be nice to not have to parse xml on every response
from the API.
Thanks for the time and effort you are putting into this proposal!
Best,
Elliot
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
