incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Vesse (Updated) (JIRA)" <>
Subject [jira] [Updated] (JENA-127) Add RDF/JSON Parsing Support to RIOT
Date Fri, 30 Sep 2011 14:51:45 GMT


Rob Vesse updated JENA-127:


Attached the Java files for the completely new code this patch adds to make it easier to review

Note that the full patch does include some additional changes beyond these files to things
like, etc in order to fully register the RDF/JSON parser with RIOT
> Add RDF/JSON Parsing Support to RIOT
> ------------------------------------
>                 Key: JENA-127
>                 URL:
>             Project: Jena
>          Issue Type: New Feature
>          Components: Jena, RIOT
>         Environment: All
>            Reporter: Rob Vesse
>            Priority: Minor
>              Labels: patch, rdf/json, riot
>         Attachments:,, RdfJsonRiotPatch.patch,
> The attached patch provides a RDF/JSON (Talis Specification) parser for RIOT, the patch
is against ARQ trunk from the Jena SourceForge SVN repository
> It plugins in as an implementation of LangRIOT (named LangRDFJSON) and uses the existing
TokenizerJSON from the atlas package to do the tokenisation.  There is also a JenaReaderRdfJson
added as part of this patch which does what the name suggests.
> I have also included in this patch a set of unit tests which verify the parsers behaviour
with a variety of valid and invalid inputs.
> There are still some things to be addressed:
> - The patch includes registration of the Jena reader when SysRiot.writeIntoJena() is
called but does not unregister itself when resetJenaReaders() is called, should this be done?
> - Add a RDF/JSON writer - a separate patch will be submitted at a later date (likely
next week) for this
> Otherwise the patch is fairly comprehensive and I hope can be reviewed and included in
future releases

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message