commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSSITE-80) Start RDF Commons
Date Wed, 17 Dec 2014 21:39:13 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250608#comment-14250608
] 

Andy Seaborne commented on COMMONSSITE-80:
------------------------------------------

I presume we mean a Java API here.  These are not the only RDF APIs.   Apache Jena has an
RDF API that is widely used. Outside Apache, Sesame is another.

commons-rdf is an effort with both Apache committers (>1 projects) and others to find common
ground for a portability layer.

An important question is "why?" -- what does a combined/single/new API provide?  For commons-rdf,
the goal is portable algorithms and processing with a choice of storage. 

This discussion is useful:
https://github.com/commons-rdf/commons-rdf/issues/35

Disclosure: I contribute to Jena and commons-rdf.


> Start RDF Commons
> -----------------
>
>                 Key: COMMONSSITE-80
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-80
>             Project: Commons All
>          Issue Type: New Feature
>            Reporter: Reto Gmür
>
> The Apache Clerezza project has the goal to provide"[a]n API modeling the W3C RDF standard
without any vendor specific additions". It would be beneficial of such an API to be part of
Apache Commons. 
> With this issue the core API work at clerezza should be harmonized with other efforts
like https://github.com/commons-rdf/commons-rdf in which apache committers are involved too.
As a new commons-rdf project. the project should focus on a minimal API that is thus likely
to be broadly accepted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message