GSOC idea: json api for plone
Johannes Raggam <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
After discussing this topic with other sprinters at the cathedralsprint, I think a JSON API for Plone would make a nice project. Some of us feel a strong need for a generic JSON API. That can help us to build modern user interfaces, decoupled from the backend and for data exchange with other web services. Best would be to implement some standard, like JSON-LD ( http://json-ld.org/ , http://www.w3.org/TR/json-ld/ ), which'd give us semantic data exchange, which is awesome (more and more web services are agnostic about their data-backend and implement real mashup services). Or Hydra: Hypermedia-Driven Web APIs http://www.markus-lanthaler.com/hydra/ I agree with Martin, that designing an API needs much experience. But I don't see here a blocker for a GSOC project: - There are open standards, which can be implemented (as mentioned above), - The mentor can guide, review and optimize the API, - The framework can do this via reviews also. So, what about that? Best, Johannes -- programmatic web development di(fh) johannes raggam / thet python plone zope development plone framework team member mail: office-//[email protected] web: http://programmatic.pro http://bluedynamics.com ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers
signature.asc
(application/pgp-signature, 181 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlL+icsACgkQW4mNMQxDgAeW/ACfYgBOpGpzw5ELmkPz/YTC8581 TUwAni4wjywWNR7dFpPdFf08O0D1/Kzy =6Sb6 -----END PGP SIGNATURE-----