incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "ClerezzaProposal" by BertrandDelacretaz
Date Fri, 20 Nov 2009 08:33:21 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "ClerezzaProposal" page has been changed by BertrandDelacretaz.
http://wiki.apache.org/incubator/ClerezzaProposal?action=diff&rev1=4&rev2=5

--------------------------------------------------

  Clerezza is an OSGi-based modular application and set of components (bundles) for building
RESTFul Semantic Web applications and services.
  
  == Proposal ==
- Clerezza can be used as a platform providing all the compile and runtime requirement for
building such applications or used as individual bundles within e.g. Apache Sling, Apache
ServiceMix, or the Eclipse platform.
+ Clerezza can be used as a platform providing all the compile and runtime requirement for
building semantic applications, or used as individual bundles within an OSGi framework, e.g.
Apache Sling, Apache ServiceMix, or the Eclipse platform.
  
  Clerezza provides:
  
-  * An API modeling the W3C RDF standard without any vendor specific addition.
+  * An API modeling the W3C RDF standard without any vendor specific additions.
   * Adapter for various triple stores including Sesame, Jena TDB, and Mulgara.
   * Front-End adaptors, currently to run applications written against the Jena API. Support
for RDF2Go is planned.
   * A JAX-RS implementation designed to work in an OSGi environment and allowing to provide
Root-Resources as OSGi services.
   * Web access to RDF graphs, including a SPARQL-Endpoint.
   * Extensions to JAX-RS allowing to bind Root-Resource classes to specific RDF-Types rather
than to URI-Paths.
   * Templating mechanism (Renderlets) allowing to render RDF resources returned by JAX-RS
resource methods to various formats
-  * Support for Scala for writing modules, ScalaServePages to easily write renderlets, DSL
for accessing graphs.
+  * Support for Scala for writing modules, ScalaServerPages to easily write renderlets, DSL
for accessing graphs.
   * Authentication and authorization based on JAAS and OSGi Conditional Permission Admin
   * Support for user bundles: Users can have a permission to upload their own sandboxed bundles.
The URI space these bundles are allowed to register their JAX-RS resources can be limited
with a prefix.
   * Scripting: Scripting based on javax.script (currently support for JRuby and Scala)
   * Documentation: Bundles can provide their documentation in RDF. These are used for online
documentation as well as for building Maven sites (with a Maven reporting plugin)
  
- The RDF abstraction layer can be used independently of other aspects of Clerezza. It allows
to write applications regardless the used backend. In its purpose, it is similar to RDF2Go,
but provides a significantly more modular interface allowing e.g. to independently switch
the storage, querying, or serialization layer. Furthermore, it doesn't introduce concepts
alien to the RDF model such as blank node labels, but is in its core strictly limited to RDF
semantics.
+ The RDF abstraction layer can be used independently of other aspects of Clerezza. It allows
applications to be written regardless the used backend. In its purpose, it is similar to RDF2Go,
but provides a significantly more modular interface allowing e.g. to independently switch
the storage, querying, or serialization layer. Furthermore, it doesn't introduce concepts
alien to the RDF model such as blank node labels, but is in its core strictly limited to RDF
semantics.
  
- The JAX-RS implementation can also be used independently of any other components. It allows
OSGi services to provide a REST-interface to their methods. By being based on wymiwyg WRHAPI,
it can run both on the default OSGi Web Service as well as on a jetty instance listening on
a different port.
+ The JAX-RS implementation can also be used independently of any other components. It allows
OSGi services to provide a RESTful interface to their methods. By being based on wymiwyg WRHAPI,
it can run both on the default OSGi Web Service as well as on a jetty instance listening on
a different port.
  
  == Background ==
  The current web trends focusing on information sharing, interoperability and collaboration.
Therefore the behaviour of the end-user has changed over the last years: end-users not only
consuming information they also producing content anytime anywhere - in contrast to non-interactive
websites where users are limited to the passive viewing of information that is provided to
them. Since the end-users are sensitized to the possibilities of the web the web application
requirements increases. Examples of such applications are social-networking sites, wikis,
blogs and mashups.
@@ -45, +45 @@

   * Prepare for an initial release that demonstrates the systems core capabilities.
  
  == Current Status ==
- The current codebase is developed and tested using Apache Felix. It has been developed intensively
and reviewed at trialox since August 2008 using Scrum and having a development process emphasizing
individual accountability and reviews. We have internally demonstrated that we can release
codes as scheduled. Platform core functionalities are available, however the need of new features
may arise, performance and robustness could be improved. Incomplete documentation for the
project is available with the individual artifacts, both in the generated maven sites as in
a version available exposed by Clerezza at runtime we also have a wiki at [[http://wiki.trialox.org/|http://wiki.trialox.org]]
with some information mainly on the development process. We also use mailing lists for communication
among developers and users.
+ The current codebase is developed and tested using Apache Felix. It has been developed intensively
and reviewed at trialox since August 2008 using Scrum, with a development process emphasizing
individual accountability and reviews. We have internally demonstrated that we can release
codes as scheduled. Platform core functionalities are available, however the need for new
features may arise, performance and robustness could be improved. Incomplete documentation
for the project is available with the individual artifacts, both in the generated maven sites
as in a version available exposed by Clerezza at runtime. We also have a wiki at [[http://wiki.trialox.org/|http://wiki.trialox.org]]
with some information mainly on the development process. We also use mailing lists for communication
among developers and users.
  
  === Meritocracy ===
  The core developers understand what it means to have a process based on meritocracy. We
will provide continuous efforts to build an environment that supports this, encouraging community
members to contribute.
  
  === Community ===
- Trialox has been developing the current codebase since August 2008. Trialox was founded
in partnership with the University of Zurich and could profit from previous research work
at the Department of Informatics. Part of the team from the beginning was Reto Bachmann Gmür
who has been developing open source Semantic Web applications for many years, including working
with the Jena team at HP Labs.
+ Trialox has been developing the current codebase since August 2008. Trialox was founded
in partnership with the University of Zurich and could benefit from previous research work
at the Department of Informatics. Part of the team from the beginning was Reto Bachmann Gmür
who has been developing open source Semantic Web applications for many years, including working
with the Jena team at HP Labs.
  
  Trialox has contributed to the JAX-RS specification. Some of the code written by trialox
is used by Open Source projects such Paxle and Gradino.
  
@@ -66, +66 @@

   * Reto Bachmann-Gmür, Developer and Architect at Trialox, developing Clerezza since August
2008.
  
  === Alignment ===
- We provide a launcher which runs Clerezza's bundles within Apache Felix. We also provide
feedback about the usage of Apache Felix and its components including the framework security
via the mailing list. For building Clerezza's bundles we use Apache Maven and various plugins.
We also have developed a plugin to help managing projects which contain ontologies, so that
Java classes representing those ontologies can be pre-compiled. Other projects which based
on Web services and/or RDF can benefit from Clerezza or its specific bundles. We are open
to collaborate with other Apache projects which can benefit from functionality provided by
Clerezza. Clerezza has the advantage of being very modular and independent of application
frameworks, thus can be easily integrated with other Apache projects. UIMA and Tika come to
mind, as they would help extract semantic information from various data types and formats.
An alignment to the JAX-RS implementation in Apache CXF could not only help removing the dependencies
to the CDDL files taken from Jersey but also help providing a fully framework independent
implementation with a larger group of developers and thus higher quality.
+ We provide a launcher which runs Clerezza's bundles within Apache Felix. We also provide
feedback about the usage of Apache Felix and its components including the framework security
via the mailing list. For building Clerezza's bundles we use Apache Maven and various plugins.
We also have developed a plugin to help managing projects which contain ontologies, so that
Java classes representing those ontologies can be pre-compiled. Other projects which based
on Web services and/or RDF can benefit from Clerezza or its specific bundles. We are open
to collaborate with other Apache projects which can benefit from functionality provided by
Clerezza. Clerezza has the advantage of being very modular and independent of application
frameworks, thus can be easily integrated with other Apache projects. UIMA and Tika come to
mind, as they would help extract semantic information from various data types and formats.
An alignment to the JAX-RS implementation in Apache CXF could not only help removing the dependencies
to the CDDL-licensed code taken from Jersey but also help providing a fully framework independent
implementation with a larger group of developers and thus higher quality.
  
  == Known Risks ==
- The current size of Clerezza core developers is small, but by innovative project in the
semantic "space", we are confident that new developers will join and commit.
+ The current team of Clerezza core developers is small, but being an innovative project in
the semantic "space", we are confident that Clerezza can attract new developers.
  
-  . Clerezza has been started as an Open Source project providing mercurial repository for
public access to source codes and also a publicly accessible JIRA instance for issues tracking.
Clerezza is licensed since project begin under Apache License version 2.0. Some of the initial
committers already have strong experiences with Open Source software development. Others,
while not being totally inexperience, are willing to learn.
+ Clerezza has been started as an Open Source project providing mercurial repository for public
access to source codes and also a publicly accessible JIRA instance for issues tracking. Clerezza
is licensed since project begin under Apache License version 2.0. Some of the initial committers
already have strong experiences with Open Source software development. Others, while not being
totally inexperience, are willing to learn.
  
  The risk that Clerezza will be an orphaned product is considered small. Three main factors
will avoid this to happen:
  
@@ -83, +83 @@

  == Documentation ==
  A small set of further documentation is available under the following links:
  
-  . [[http://wiki.trialox.org/confluence/pages/createpage.action?spaceKey=INTERNALS&title=1&linkCreation=true&fromPageId=4423905|1]]
http://trialox.org/projects/org.clerezza.rdf.core/documentation/overview.xhtml [[http://wiki.trialox.org/confluence/pages/createpage.action?spaceKey=INTERNALS&title=2&linkCreation=true&fromPageId=4423905|2]]
http://trialox.org/projects/org.clerezza.triaxrs.parent/org.clerezza.triaxrs/documentation/
+  * [[http://wiki.trialox.org/confluence/pages/createpage.action?spaceKey=INTERNALS&title=1&linkCreation=true&fromPageId=4423905|1]]
http://trialox.org/projects/org.clerezza.rdf.core/documentation/overview.xhtml  
+  * [[http://wiki.trialox.org/confluence/pages/createpage.action?spaceKey=INTERNALS&title=2&linkCreation=true&fromPageId=4423905|2]]
http://trialox.org/projects/org.clerezza.triaxrs.parent/org.clerezza.triaxrs/documentation/
  
  == Initial Source ==
  Clerezza has been in development since mid 2008. Public access to the source is provided
through http://scm.trialox.org/.
@@ -92, +93 @@

  The current codebase is owned by trialox, and will be donated together with its documentation.
We will get the paperwork out of the way as soon as possible.
  
  == External Dependencies ==
- There are quite a few open source libraries already used. However, they have Apache compatible
licenses. The libraries, their sources and licenses are listed here:
+ There are quite a few open source libraries already used. They have Apache compatible licenses,
with one issue to solve around Jersey which is CDDL.
+ 
+ The libraries, their sources and licenses are listed here:
  
  Apache Felix, ASL:
  
@@ -146, +149 @@

  
  Jersey (https://jersey.dev.java.net/), CDDL license
  
- The current code bases on code licensed under the CDDL, we understand we have to get rid
of these before making a release. The following files are affected.
+ The current code bases on code licensed under the CDDL, according to http://apache.org/legal/resolved.html
we understand we have to get rid of these before making a release, or redistribute in binary
form only. The following files are affected.
  
   * QualityFactor.java
   * HttpDateFormat.java
@@ -215, +218 @@

  
  Sponsor:
  
- Apache Incubator
+  * Apache Incubator
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message