Re: GSOC idea: json api for plone

On Sat, 2014-02-22 at 16:49 -0800, Laurence Rowe wrote:
> I think the complexities you mention apply more to the task of
> extracting semantic likes from unstructured content (e.g. from within
> a Plone rich text field.) JSON-LD is about semantically annotating
> structured json, where everything is already split into fields. You
> just need to say what those fields mean and which are links to other
> resources (reference fields in Plone). Basic support should be trivial
> to implement as you could just generate a json-ld context from an
> existing dexterity schema definition.

exactly as i see it. i'm thinking of extending zope.schema with some
optional attributes for semantics. for example, to add a list of URIs to
online schema vocabularies, like schema.org for each field in a schema
and the schema class itself.

however, i agree that we need a R/W JSON API in the first place.


> You need to expend a significant amount of effort if you want to fully
> connect your metadata into the semantic web as you need to use terms
> and predicates that are also used by others. Plone already has partial
> support for dublin core metadata through the default templates
> rendering html link elements. You'd want a way to specify the
> predicate url on a dexterity schema field.
> 
> 
> It's a read-only standard, so it's not going to help with writes,
> JSON-Shema seems to be the relevant standard there. But even basic
> support gives your users the ability to pull down your metadata and
> load it into a SPARQL store for arbitrary querying, without writing
> custom code to parse and load your json.
> 
> 
> Laurence
> 
> 
> On 22 February 2014 16:01, Jens W. Klein <jens-/[email protected]>
> wrote:
>         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
>         _______________________________________________
>         Plone-developers mailing list
>         Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>         https://lists.sourceforge.net/lists/listinfo/plone-developers
>         
> 
> 
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers

-- 
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

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlMLH3MACgkQW4mNMQxDgAcECQCguCYnLZasUKTwiO9Icg+i+Qrj
DQkAn0r/zujDqUdwb6vLjkLmf3P5t5mc
=KWwe
-----END PGP SIGNATURE-----