Re: GSOC idea: json api for plone

"Jens W. Klein" <jens-/[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Organization Klein & Partner KG
Message-ID <[email protected]>
Hi,

I agree to have a json api for plone. This is essential these days.

Ad json.ld:

json.ld is - as the name says - a linked data format, thus it predicts 
semantic links between the content - in order to make it semantic 
searchable. So the main purpose of json-ld is (more comprehensive, but 
like RDF) to provide triples (subject, predicate, object) about the 
content, probably including all its information prepared in this way.

I fear in most cases this is difficult. To link data in a sematic 
approach we need to inspect this data (manually or automatic) in order 
to enrich the links between the data. The Apache Stanbol Project helps 
here to make this automatic, but I fear this is a  bit heavyweight for 
the average Plone "user".

So imo json-ld is not the right format for the purpose of a simple json 
api. IMO a simple TTW crud API is what we want in 95% of cases.

I really would like to see Plone supporting json-ld anyway. But its out 
of scope of a generic json-api which solves the major daily use-cases of 
the Plone integrators there out in the wild.

just my 0.02 Euro

Jens

On 2014-02-14 22:25, Johannes Raggam wrote:
> 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

-- 
Klein & Partner KG, member of BlueDynamics Alliance


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.