interesting suggestion...
-------- Original Message -------- Subject: Fwd: Re: [ANNOUNCE] Jena 2.10.0 released From: Andy Seaborne <[email protected]> To: [email protected] CC: Forwarded with permission (good suggestion) Andy -------- Original Message -------- Subject: Re: [ANNOUNCE] Jena 2.10.0 released Date: Tue, 26 Feb 2013 14:14:49 -0500 From: Mike Kienenberger <[email protected]> To: Andy Seaborne <[email protected]> Suggestion: When you send out a release announcement, include a short description of what your project does as this will get people interested in what you're releasing rather than deleting the message out of hand. Don't assume people will take the extra time to open your project link in a web browser if they have no idea what you are releasing. For example, ============ The Apache Jena team are pleased to announce the release of Apache Jena 2.10.0 together with Jena Fuseki 0.2.6. Apache Jena™ is a Java framework for building Semantic Web applications. Jena Fuseki is a SPARQL server which provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP. http://jena.apache.org/ [rest of the release blah blah blah.] ============ Regards, Mike Kienenberger On Tue, Feb 26, 2013 at 1:49 PM, Andy Seaborne <[email protected]> wrote: > The Apache Jena team are pleased to announce the release of Apache Jena > 2.10.0 together with Jena Fuseki 0.2.6. > > http://jena.apache.org/ > > Key features and changes in this release are: > > * A single maven artifact to include Jena in your maven project > > * New RDF 1.1 Turtle parser tracking the developing standard > > * Portuguese translations of tutorials > > * Changes to the way storage subsystems provide SPARQL Update > > > == apache-jena-libs > > There is a new maven artifact to help applications by providing a single > maven artifact that include the main Jena modules. > > <dependency> > <groupId>org.apache.jena</groupId> > <artifactId>apache-jena-libs</artifactId> > <type>pom</type> > <version>2.10.0</version> > </dependency> > > Note the use of <type>pom</type> > > By using this artifact, applications will not be affected by any future > changes to the internal development module structure of Jena. > > See > http://jena.apache.org/download/maven.html > > == RIOT Reader > > There is a new RDF parser subsystem, which includes > > * improved content negotiation > * alignment to RDF 1.1 Turtle > * the ability to register new parsers into Jena > * features apply when applications use model.read() > > http://jena.apache.org/documentation/io/index.html > > The package name org.openjena.riot becomes org.apache.jena.riot. > > There is some compatibility code in org.openjena.riot. Operations are > deprecated and will be removed after this release. > > Test: > > model.read("data.ttl") > > will read a local Turtle file. > > == Streaming Update > > The SPARQL Update engine has been re-architected to make the fundamental > execution of SPARQL Updates streamable. > > There is no change to applications using SPARQL Update. > > There are changes to the interface for storage systems that make special > provision for SPARQL Update. If you are migrating such a storage system, > do talk to the developers on [email protected] if you have any > questions or suggestions for improvements. > > == Portuguese Translations of the tutorial > > Guilherme Cavalcanti has provided a Portuguese translation of the tutorials. > > http://jena.apache.org/tutorials/ > > == Reification > > As part of simplifying Jena, the reification styles Convenient and > Minimal are being removed. These need a significant amount of internal > state management and impede scaling beyond storage in memory. > > The only support style is "standard", which as always been the default > style in Jena. Only style "standard" has even been supported by TDB and > SDB. > > Use of the constants for these styles is deprecated and will be treated > as "standard". > > == Internal simplification > > Other simplifications in this release include the removal of the graph > query handler subsystem. This is unrelated to SPARQL and existed in > support of RDQL. > > The graph level bulk query handler has been removed - compatibility for > the Model API for all bulk update is maintained. >
