Re: [RESULTS] [VOTE] Accept Apache Clerezza into the incubator

[David Crossley]

I did the first step for you ... added to the ReportingSchedule
with December, January, February being your first three
reporting months. Please adjust that if you want to.

This gets your project into Clutch immediately, which helps
to manage the incubation process.
http://incubator.apache.org/clutch.html#steps

-David


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULTS] [VOTE] Accept Apache Clerezza into the incubator

[Bertrand Delacretaz]

On Mon, Nov 23, 2009 at 7:32 PM, Reto Bachmann-Gmür
 wrote:
> Please vote on accepting Apache Clerezza for incubation at the Apache
> Incubator. The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal...

The vote passes with more than 3 +1s from Incubator PMC members.

+1 votes received, (*) means Incubator PMC member [1]. No other votes.

Adam Wojtuniak
Alan D. Cabrera (*)
Ant Elder (*)
Bertrand Delacretaz (*)
Craig L Russell (*)
Davanum Srinivas (*)
Gianugo Rabellino (*)
Jean-Baptiste Onofré
Karl Pauls
Marcel Offermans
Mohammad Nour El-Din
Niclas Hedhman (*)
Reinhard Pötz (*)
Ross Gardler (*)
Sylvain Wallez (*)
Tommaso Teofili

Thanks everybody for your support, I'll request creation of the
infrastructure services and user accounts in the next few days.

Clerezza podling committers, please send in your iCLA
(http://www.apache.org/licenses/icla.txt) if you haven't done it yet.

Reto, you can now send the software grant
(http://www.apache.org/licenses/software-grant.txt) for the initial
code donation.

Looking forward to Clerezza!

Stay tuned to http://incubator.apache.org/clerezza (once that comes to
life) for the story of the name ;-)

-Bertrand

[1] If you're an Incubator member and don't get a (*) above that means
https://svn.apache.org/repos/private/committers/board/committee-info.txt
is not up to date.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Niclas Hedhman]

On Tue, Nov 24, 2009 at 2:32 AM, Reto Bachmann-Gmür
 wrote:

[ x ] +1, bring Clerezza into Incubator


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Jean-Baptiste Onofré]

+1
-Original Message-
From: Mohammad Nour El-Din 
Date: Tue, 24 Nov 2009 13:19:25 
To: ; 
Subject: Re: [VOTE] Accept Apache Clerezza into the incubator

+1

On Tue, Nov 24, 2009 at 1:15 PM, ant elder  wrote:
> +1
>
>   ...ant
>
> On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür
>  wrote:
>> Please vote on accepting Apache Clerezza for incubation at the Apache
>> Incubator. The full proposal is available at the end of this message and
>> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
>> <http://wiki.apache.org/incubator/AceProposal>. We ask the Incubator PMC
>> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
>> Karl and Reinhard volunteering to be Mentors.
>>
>> Please cast your votes:
>>
>> [ ] +1, bring Clerezza into Incubator
>> [ ] +0, I don't care either way,
>> [ ] -1, do not bring Clerezza into Incubator, because...
>>
>> The vote is open for the next 72 hours and only votes from the Incubator
>> PMC are binding.
>>
>> - - - - - - - - - -
>>
>> Abstract
>>
>> 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 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
>> 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, 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 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 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.
>>
>> The REST paradigm and Semantic Web technologies support th

Re: [VOTE] Accept Apache Clerezza into the incubator

[Mohammad Nour El-Din]

+1

On Tue, Nov 24, 2009 at 1:15 PM, ant elder  wrote:
> +1
>
>   ...ant
>
> On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür
>  wrote:
>> Please vote on accepting Apache Clerezza for incubation at the Apache
>> Incubator. The full proposal is available at the end of this message and
>> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
>> . We ask the Incubator PMC
>> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
>> Karl and Reinhard volunteering to be Mentors.
>>
>> Please cast your votes:
>>
>> [ ] +1, bring Clerezza into Incubator
>> [ ] +0, I don't care either way,
>> [ ] -1, do not bring Clerezza into Incubator, because...
>>
>> The vote is open for the next 72 hours and only votes from the Incubator
>> PMC are binding.
>>
>> - - - - - - - - - -
>>
>> Abstract
>>
>> 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 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
>> 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, 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 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 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.
>>
>> The REST paradigm and Semantic Web technologies support these trends and
>> form the basis for the upcoming Web of Data (a.k.a. linked data, Web
>> 3.0). They change the paradigms for developing complex Web applications.
>> Clerezza allows to develop applications that integrate perfectly in the
>> Semantic Web providing all accessible resources in machine
>> understandable formats without imposing additional burdens on the
>> developer. Additionally, thanks to the flexibility of the RDF model used
>> as back-end, some tedious database related tasks required for
>> traditional Web application development are no longer needed.
>>
>> Rationale
>>
>> Most Web application framework are not designed to leverage the full
>> power of HTTP but often try to reproduce non Web de

Re: [VOTE] Accept Apache Clerezza into the incubator

[ant elder]

+1

   ...ant

On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür
 wrote:
> Please vote on accepting Apache Clerezza for incubation at the Apache
> Incubator. The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
> . We ask the Incubator PMC
> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
> Karl and Reinhard volunteering to be Mentors.
>
> Please cast your votes:
>
> [ ] +1, bring Clerezza into Incubator
> [ ] +0, I don't care either way,
> [ ] -1, do not bring Clerezza into Incubator, because...
>
> The vote is open for the next 72 hours and only votes from the Incubator
> PMC are binding.
>
> - - - - - - - - - -
>
> Abstract
>
> 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 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
> 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, 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 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 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.
>
> The REST paradigm and Semantic Web technologies support these trends and
> form the basis for the upcoming Web of Data (a.k.a. linked data, Web
> 3.0). They change the paradigms for developing complex Web applications.
> Clerezza allows to develop applications that integrate perfectly in the
> Semantic Web providing all accessible resources in machine
> understandable formats without imposing additional burdens on the
> developer. Additionally, thanks to the flexibility of the RDF model used
> as back-end, some tedious database related tasks required for
> traditional Web application development are no longer needed.
>
> Rationale
>
> Most Web application framework are not designed to leverage the full
> power of HTTP but often try to reproduce non Web design patterns for the
> Web environment. In general, application frameworks are oriented towards
> relational or hierarchical data structures. While attempts to ove

Re: [VOTE] Accept Apache Clerezza into the incubator

[Sylvain Wallez]

Reto Bachmann-Gmür wrote:

Please vote on accepting Apache Clerezza for incubation at the Apache
Incubator. The full proposal is available at the end of this message and
as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
. We ask the Incubator PMC
to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
Karl and Reinhard volunteering to be Mentors.

Please cast your votes:

[x] +1, bring Clerezza into Incubator
  


+1, sounds very interesting.

Sylvain

--
Sylvain Wallez - http://bluxte.net


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Tommaso Teofili]

2009/11/23 Reinhard Pötz 

>
> >
> > [ ] +1, bring Clerezza into Incubator
> > [ ] +0, I don't care either way,
> > [ ] -1, do not bring Clerezza into Incubator, because...
> >
> > The vote is open for the next 72 hours and only votes from the Incubator
> > PMC are binding.
>
>
+1

Tommaso

Re: [VOTE] Accept Apache Clerezza into the incubator

[Reinhard Pötz]

Reto Bachmann-Gmür wrote:
> Please vote on accepting Apache Clerezza for incubation at the Apache
> Incubator. The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
> . We ask the Incubator PMC
> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
> Karl and Reinhard volunteering to be Mentors.
> 
> Please cast your votes:
> 
> [ ] +1, bring Clerezza into Incubator
> [ ] +0, I don't care either way,
> [ ] -1, do not bring Clerezza into Incubator, because...
> 
> The vote is open for the next 72 hours and only votes from the Incubator
> PMC are binding.

+1

--
Reinhard

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Ross Gardler]

+1

2009/11/23 adam wojtuniak :
>  [X] +1, bring Clerezza into Incubator  (non binding)
>
> Cheers,
> Adam
>
> On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür <
> reto.bachm...@trialox.org> wrote:
>
>> Please vote on accepting Apache Clerezza for incubation at the Apache
>> Incubator. The full proposal is available at the end of this message and
>> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
>> . We ask the Incubator PMC
>> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
>> Karl and Reinhard volunteering to be Mentors.
>>
>> Please cast your votes:
>>
>> [ ] +1, bring Clerezza into Incubator
>> [ ] +0, I don't care either way,
>> [ ] -1, do not bring Clerezza into Incubator, because...
>>
>> The vote is open for the next 72 hours and only votes from the Incubator
>> PMC are binding.
>>
>> - - - - - - - - - -
>>
>> Abstract
>>
>> 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 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
>> 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, 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 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 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.
>>
>> The REST paradigm and Semantic Web technologies support these trends and
>> form the basis for the upcoming Web of Data (a.k.a. linked data, Web
>> 3.0). They change the paradigms for developing complex Web applications.
>> Clerezza allows to develop applications that integrate perfectly in the
>> Semantic Web providing all accessible resources in machine
>> understandable formats without imposing additional burdens on the
>> developer. Additionally, thanks to the flexibility of the RDF model used
>> as back-end, some tedious database related tasks required for
>> traditional Web application development are no longer needed.
>>
>> Rationale
>>
>> Most Web application framework are not designed to leverage

Re: [VOTE] Accept Apache Clerezza into the incubator

[Gianugo Rabellino]

On Mon, Nov 23, 2009 at 7:32 PM, Reto Bachmann-Gmür
 wrote:
> Please vote on accepting Apache Clerezza for incubation at the Apache
> Incubator. The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
> . We ask the Incubator PMC
> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
> Karl and Reinhard volunteering to be Mentors.
>
> Please cast your votes:

+1

-- 
Gianugo

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Karl Pauls]

+1

regards,

Karl

On Mon, Nov 23, 2009 at 9:35 PM, Craig L Russell  wrote:
> +1
>
> Sounds like a very interesting project.
>
> Craig
>
> On Nov 23, 2009, at 10:32 AM, Reto Bachmann-Gmür wrote:
>
>> Please vote on accepting Apache Clerezza for incubation at the Apache
>> Incubator. The full proposal is available at the end of this message and
>> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
>> . We ask the Incubator PMC
>> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
>> Karl and Reinhard volunteering to be Mentors.
>>
>> Please cast your votes:
>>
>> [ ] +1, bring Clerezza into Incubator
>> [ ] +0, I don't care either way,
>> [ ] -1, do not bring Clerezza into Incubator, because...
>>
>> The vote is open for the next 72 hours and only votes from the Incubator
>> PMC are binding.
>>
>> - - - - - - - - - -
>>
>> Abstract
>>
>> 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 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
>> 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, 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 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 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.
>>
>> The REST paradigm and Semantic Web technologies support these trends and
>> form the basis for the upcoming Web of Data (a.k.a. linked data, Web
>> 3.0). They change the paradigms for developing complex Web applications.
>> Clerezza allows to develop applications that integrate perfectly in the
>> Semantic Web providing all accessible resources in machine
>> understandable formats without imposing additional burdens on the
>> developer. Additionally, thanks to the flexibility of the RDF model used
>> as back-end, some tedious database related tasks required for
>> traditional Web application development are no longer needed.
>>
>> Rationale
>>
>> Most Web application framework are not designed to leverage the full
>> power

Re: [VOTE] Accept Apache Clerezza into the incubator

[Craig L Russell]

+1

Sounds like a very interesting project.

Craig

On Nov 23, 2009, at 10:32 AM, Reto Bachmann-Gmür wrote:


Please vote on accepting Apache Clerezza for incubation at the Apache
Incubator. The full proposal is available at the end of this message  
and

as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
. We ask the Incubator  
PMC
to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas,  
Ross,

Karl and Reinhard volunteering to be Mentors.

Please cast your votes:

[ ] +1, bring Clerezza into Incubator
[ ] +0, I don't care either way,
[ ] -1, do not bring Clerezza into Incubator, because...

The vote is open for the next 72 hours and only votes from the  
Incubator

PMC are binding.

- - - - - - - - - -

Abstract

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

The REST paradigm and Semantic Web technologies support these trends  
and

form the basis for the upcoming Web of Data (a.k.a. linked data, Web
3.0). They change the paradigms for developing complex Web  
applications.
Clerezza allows to develop applications that integrate perfectly in  
the

Semantic Web providing all accessible resources in machine
understandable formats without imposing additional burdens on the
developer. Additionally, thanks to the flexibility of the RDF model  
used

as back-end, some tedious database related tasks required for
traditional Web application development are no longer needed.

Rationale

Most Web application framework are not designed to leverage the full
power of HTTP but often try to reproduce non Web design patterns for  
the
Web environment. In general, application frameworks are oriented  
towards

relational or hierarchical data structures. While attempts to overcome
this such as Drupal have become very popular, they do not at their  
core

base on the sta

Re: [VOTE] Accept Apache Clerezza into the incubator

[adam wojtuniak]

 [X] +1, bring Clerezza into Incubator  (non binding)

Cheers,
Adam

On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür <
reto.bachm...@trialox.org> wrote:

> Please vote on accepting Apache Clerezza for incubation at the Apache
> Incubator. The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
> . We ask the Incubator PMC
> to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
> Karl and Reinhard volunteering to be Mentors.
>
> Please cast your votes:
>
> [ ] +1, bring Clerezza into Incubator
> [ ] +0, I don't care either way,
> [ ] -1, do not bring Clerezza into Incubator, because...
>
> The vote is open for the next 72 hours and only votes from the Incubator
> PMC are binding.
>
> - - - - - - - - - -
>
> Abstract
>
> 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 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
> 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, 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 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 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.
>
> The REST paradigm and Semantic Web technologies support these trends and
> form the basis for the upcoming Web of Data (a.k.a. linked data, Web
> 3.0). They change the paradigms for developing complex Web applications.
> Clerezza allows to develop applications that integrate perfectly in the
> Semantic Web providing all accessible resources in machine
> understandable formats without imposing additional burdens on the
> developer. Additionally, thanks to the flexibility of the RDF model used
> as back-end, some tedious database related tasks required for
> traditional Web application development are no longer needed.
>
> Rationale
>
> Most Web application framework are not designed to leverage the full
> power of HTTP but often try to reproduce non Web design patterns for the
> Web environment. In general, application frameworks are o

Re: [VOTE] Accept Apache Clerezza into the incubator

[Alan D. Cabrera]

+1


Regards,
Alan

On Nov 23, 2009, at 10:32 AM, Reto Bachmann-Gmür wrote:


Please vote on accepting Apache Clerezza for incubation at the Apache
Incubator. The full proposal is available at the end of this message  
and

as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
. We ask the Incubator  
PMC
to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas,  
Ross,

Karl and Reinhard volunteering to be Mentors.

Please cast your votes:

[ ] +1, bring Clerezza into Incubator
[ ] +0, I don't care either way,
[ ] -1, do not bring Clerezza into Incubator, because...

The vote is open for the next 72 hours and only votes from the  
Incubator

PMC are binding.

- - - - - - - - - -

Abstract

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

The REST paradigm and Semantic Web technologies support these trends  
and

form the basis for the upcoming Web of Data (a.k.a. linked data, Web
3.0). They change the paradigms for developing complex Web  
applications.
Clerezza allows to develop applications that integrate perfectly in  
the

Semantic Web providing all accessible resources in machine
understandable formats without imposing additional burdens on the
developer. Additionally, thanks to the flexibility of the RDF model  
used

as back-end, some tedious database related tasks required for
traditional Web application development are no longer needed.

Rationale

Most Web application framework are not designed to leverage the full
power of HTTP but often try to reproduce non Web design patterns for  
the
Web environment. In general, application frameworks are oriented  
towards

relational or hierarchical data structures. While attempts to overcome
this such as Drupal have become very popular, they do not at their  
core

base on the stack of Semantic Web standards. Cl

Re: [VOTE] Accept Apache Clerezza into the incubator

[Bertrand Delacretaz]

On Mon, Nov 23, 2009 at 7:32 PM, Reto Bachmann-Gmür
 wrote:
> ...The full proposal is available at the end of this message and
> as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
> 

The first link is the right one, of course.

> ...Please cast your votes:

[ X] +1, bring Clerezza into Incubator

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Marcel Offermans]

+1 (non binding)


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Clerezza into the incubator

[Davanum Srinivas]

+1, bring Clerezza into Incubator

On 11/23/2009 01:32 PM, Reto Bachmann-Gmür wrote:

Please vote on accepting Apache Clerezza for incubation at the Apache
Incubator. The full proposal is available at the end of this message and
as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
. We ask the Incubator PMC
to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
Karl and Reinhard volunteering to be Mentors.

Please cast your votes:

[ ] +1, bring Clerezza into Incubator
[ ] +0, I don't care either way,
[ ] -1, do not bring Clerezza into Incubator, because...

The vote is open for the next 72 hours and only votes from the Incubator
PMC are binding.

- - - - - - - - - -

Abstract

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

The REST paradigm and Semantic Web technologies support these trends and
form the basis for the upcoming Web of Data (a.k.a. linked data, Web
3.0). They change the paradigms for developing complex Web applications.
Clerezza allows to develop applications that integrate perfectly in the
Semantic Web providing all accessible resources in machine
understandable formats without imposing additional burdens on the
developer. Additionally, thanks to the flexibility of the RDF model used
as back-end, some tedious database related tasks required for
traditional Web application development are no longer needed.

Rationale

Most Web application framework are not designed to leverage the full
power of HTTP but often try to reproduce non Web design patterns for the
Web environment. In general, application frameworks are oriented towards
relational or hierarchical data structures. While attempts to overcome
this such as Drupal have become very popular, they do not at their core
base on the stack of Semantic Web standards. Clerezza will prove that

[VOTE] Accept Apache Clerezza into the incubator

[Reto Bachmann-Gmür]

Please vote on accepting Apache Clerezza for incubation at the Apache
Incubator. The full proposal is available at the end of this message and
as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal
. We ask the Incubator PMC
to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross,
Karl and Reinhard volunteering to be Mentors.

Please cast your votes:

[ ] +1, bring Clerezza into Incubator
[ ] +0, I don't care either way,
[ ] -1, do not bring Clerezza into Incubator, because...

The vote is open for the next 72 hours and only votes from the Incubator
PMC are binding.

- - - - - - - - - -

Abstract

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

The REST paradigm and Semantic Web technologies support these trends and
form the basis for the upcoming Web of Data (a.k.a. linked data, Web
3.0). They change the paradigms for developing complex Web applications.
Clerezza allows to develop applications that integrate perfectly in the
Semantic Web providing all accessible resources in machine
understandable formats without imposing additional burdens on the
developer. Additionally, thanks to the flexibility of the RDF model used
as back-end, some tedious database related tasks required for
traditional Web application development are no longer needed.

Rationale

Most Web application framework are not designed to leverage the full
power of HTTP but often try to reproduce non Web design patterns for the
Web environment. In general, application frameworks are oriented towards
relational or hierarchical data structures. While attempts to overcome
this such as Drupal have become very popular, they do not at their core
base on the stack of Semantic Web standards. Clerezza will prove that
the flexibility of the RDF doesn't result in increased complexity, but
on the contrary allows for fa