We are pleased to announce new releases of Jena and ARQ:



Jena: http://prdownloads.sourceforge.net/jena/jena-2.5.7.zip



ARQ: http://prdownloads.sourceforge.net/jena/arq-2.6.0.zip



The version of ARQ in the Jena download and version of Jena in the ARQ download

are sync'ed to these releases. You only need download one of them to get all

the jar files.



The difference is that the Jena download has the documentation and source for

Jena, and the ARQ download has the documentation and source for ARQ.



         Andy





Changes (see downloads for details):



==== Jena 2.5.7



Ontology API:

    o Make OntModel.read(string) respect content negotiation



Database layer:

    o Compatibility fixes for PostgreSQL 8.3 (no schema changes)

    o Compatibility fixes for MS SQL Server 2008 (no schema changes)



ReasonerFactoryAssembler

     o Now takes note of ja:schema properties & binds such a schema

       to the reasoners that the factory produces.



Reasoners:

     o Modified @include processing and Rule.rulesFromURL to support

       FileManager redirects.

     o Fixed problem withLPTopGoalIterator which caused one extra level

       of lookahead in some circumstances.





==== ARQ 2.6.0

(changes since the version shipped with Jena 2.5.6)



+ Added .close() to Dataset and GraphStore for those implementations that

   need to make changes permanent or release system resources.



+ Fix bug in SPARQL grammar (!) : expressions like "1+2*3" did not parse.

   This is a fix to the grammar as published by the working group.

    It does not invalidate or change any query that works - it makes some

    illegal syntax work that should work.



+ Redesign of quad support.

   AlgebraGeneratorQuad retired

   Use Algebra.toQuadForm(Op) to turn an algebra expression into quads.



+ fn:string-join was misnamed - was actually renamed as fn:concat

   And now takes arbitrary number of arguments



+ Bug fix: path parsing when "a" (for rdf:type)

            is used in a property list (using ;)



+ Bug fix: LET expressions did not eliminate solutions when

     assigned a new, different value.



+ Signal start/end of updates using the graph-level events mechanism.



+ Change to interface for query compilation : Algebra.compile and

Algebra.optimize



+ Property paths added.  See documentation.

http://jena.sourceforge.net/ARQ/property_paths.html



== Maven



Jena and ARQ are available as artifacts for Maven and Apache Ivy.



The Jena repository is http://jena.hpl.hp.com/repo.

This is mirrored to repo1.maven.org (mirroring may take 24 hours to happen).













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

   Hewlett-Packard Limited

   Registered Office: Cain Road, Bracknell, Berks RG12 1HN

   Registered No: 690597 England

The way SF downloads work has changed a bit and this time we seem to have ended

up with non-lowercase named for files:



http://prdownloads.sourceforge.net/jena/Jena-2.5.7.zip

http://prdownloads.sourceforge.net/jena/ARQ-2.6.0.zip



         Andy



> -----Original Message-----

> From: jena-dev@yahoogroups.com [mailto:jena-dev@yahoogroups.com] On

> Behalf Of Seaborne, Andy

> Sent: 8 December 2008 14:10

> To: jena-dev@yahoogroups.com

> Subject: [jena-dev] ANN: Jena 2.5.7 and ARQ 2.6.0

>

> We are pleased to announce new releases of Jena and ARQ:

>

> Jena: http://prdownloads.sourceforge.net/jena/jena-2.5.7.zip

>

> ARQ: http://prdownloads.sourceforge.net/jena/arq-2.6.0.zip

>

> The version of ARQ in the Jena download and version of Jena in the ARQ

> download

> are sync'ed to these releases. You only need download one of them to get

> all

> the jar files.

>

> The difference is that the Jena download has the documentation and

> source for

> Jena, and the ARQ download has the documentation and source for ARQ.

>

>         Andy

>

>

> Changes (see downloads for details):

>

> ==== Jena 2.5.7

>

> Ontology API:

>    o Make OntModel.read(string) respect content negotiation

>

> Database layer:

>    o Compatibility fixes for PostgreSQL 8.3 (no schema changes)

>    o Compatibility fixes for MS SQL Server 2008 (no schema changes)

>

> ReasonerFactoryAssembler

>     o Now takes note of ja:schema properties & binds such a schema

>       to the reasoners that the factory produces.

>

> Reasoners:

>     o Modified @include processing and Rule.rulesFromURL to support

>       FileManager redirects.

>     o Fixed problem withLPTopGoalIterator which caused one extra level

>       of lookahead in some circumstances.

>

>

> ==== ARQ 2.6.0

> (changes since the version shipped with Jena 2.5.6)

>

> + Added .close() to Dataset and GraphStore for those implementations

> that

>   need to make changes permanent or release system resources.

>

> + Fix bug in SPARQL grammar (!) : expressions like "1+2*3" did not

> parse.

>   This is a fix to the grammar as published by the working group.

>    It does not invalidate or change any query that works - it makes some

>    illegal syntax work that should work.

>

> + Redesign of quad support.

>   AlgebraGeneratorQuad retired

>   Use Algebra.toQuadForm(Op) to turn an algebra expression into quads.

>

> + fn:string-join was misnamed - was actually renamed as fn:concat

>   And now takes arbitrary number of arguments

>

> + Bug fix: path parsing when "a" (for rdf:type)

>            is used in a property list (using ;)

>

> + Bug fix: LET expressions did not eliminate solutions when

>     assigned a new, different value.

>

> + Signal start/end of updates using the graph-level events mechanism.

>

> + Change to interface for query compilation : Algebra.compile and

> Algebra.optimize

>

> + Property paths added.  See documentation.

> http://jena.sourceforge.net/ARQ/property_paths.html

>

> == Maven

>

> Jena and ARQ are available as artifacts for Maven and Apache Ivy.

>

> The Jena repository is http://jena.hpl.hp.com/repo.

> This is mirrored to repo1.maven.org (mirroring may take 24 hours to

> happen).

>

>

>

>

>

>

> --------------------------------------------

>   Hewlett-Packard Limited

>   Registered Office: Cain Road, Bracknell, Berks RG12 1HN

>   Registered No: 690597 England

>

>

> ------------------------------------

>

> Yahoo! Groups Links

>

>

>

On Monday 08 December 2008 15:09:42 Seaborne, Andy wrote:

> + Property paths added.  See documentation.

> http://jena.sourceforge.net/ARQ/property_paths.html



Oh, cool! I have not been aware of any other efforts, but I have actually

implemented something very similar in my application. Also, I think there is

something in N3? It seems like something that makes SPARQL easier to write,

so perhaps this is something that should be taken up with DAWGv2?



Kind regards



Kjetil Kjernsmo

--

Senior Knowledge Engineer

Mobile: +47 986 48 234

Email: kjetil.kjernsmo@...

Web: http://www.computas.com/



|  SHARE YOUR KNOWLEDGE  |



Computas AS  PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47 6783

1001

> -----Original Message-----

> From: jena-dev@yahoogroups.com [mailto:jena-dev@yahoogroups.com] On

> Behalf Of Kjetil Kjernsmo

> Sent: 9 December 2008 10:31

> To: jena-dev@yahoogroups.com

> Subject: Property paths (was: Re: [jena-dev] ANN: Jena 2.5.7 and ARQ

> 2.6.0)

>

> On Monday 08 December 2008 15:09:42 Seaborne, Andy wrote:

> > + Property paths added.  See documentation.

> > http://jena.sourceforge.net/ARQ/property_paths.html

>

> Oh, cool! I have not been aware of any other efforts, but I have

> actually

> implemented something very similar in my application. Also, I think

> there is

> something in N3? It seems like something that makes SPARQL easier to

> write,

> so perhaps this is something that should be taken up with DAWGv2?



Well, *I* hope so :-)  Not everything in the extensions in ARQ should be

candidates for standardisation but property paths are one I thing would be

useful.



There are two kinds of property paths: abbreviations for structures you can

already write, fixed length paths and alternatives of fixed length paths, and

those that introduce new expressive power (the unbounded length forms: e.g. "*",

"+", {n,}"  The simpler cases of fixed length paths get compiled internally to

triple patterns in ARQ for efficiency.



N3 has the fixed length forms with "!" and "^" but not the arbitrary length

paths.

ARQ could have used "!" for "/" but (1) other people have uses "/" and (2) uucp

is not a modern routing technology (and BCPL is not a common programming

language).



         Andy





>

> Kind regards

>

> Kjetil Kjernsmo

> --

> Senior Knowledge Engineer

> Mobile: +47 986 48 234

> Email: kjetil.kjernsmo@...

> Web: http://www.computas.com/

>

> |  SHARE YOUR KNOWLEDGE  |

>

> Computas AS  PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47

> 6783

> 1001

>

>

> ------------------------------------

>

> Yahoo! Groups Links

>

>

>

> Well, *I* hope so :-)  Not everything in the extensions in ARQ

> should be candidates for standardisation but property paths are one

> I think would be useful.



Yes absolutely. IMHO by far the most useful aspect here is the *

operator that allows users to get transitive sub/super classes and

properties at query time, e.g.



	 ?p rdfs:subPropertyOf* rdfs:label .

	 ?ex ?p ?label .



to get all values of rdfs:label (or sub-properties thereof) at ?ex. Or



	 ?type rdfs:subClassOf* ex:Person .

	 ?instance a ?type .



to get all instances of ex:Person (or sub-classes thereof).



This extension basically means that a huge fraction of use cases of

RDFS/OWL inferencing can be covered by SPARQL alone. No need for any

other (potentially slow) inference engines in the stack here!



I hope the working group will consider this.



Holger



PS: Having said this, I also believe that SPARQL 2 should contain LET,

but that's another story.

On Tuesday 09 December 2008 18:26:53 Holger Knublauch wrote:

> Yes absolutely. IMHO by far the most useful aspect here is the *  

> operator that allows users to get transitive sub/super classes and  

> properties at query time, e.g.



Yeah, that's a good point!



Andy, would this be material for another member submission?



Kind regards



Kjetil Kjernsmo

--

Senior Knowledge Engineer

Mobile: +47 986 48 234

Email: kjetil.kjernsmo@...

Web: http://www.computas.com/



|  SHARE YOUR KNOWLEDGE  |



Computas AS  PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47 6783

1001

> -----Original Message-----

> From: jena-dev@yahoogroups.com [mailto:jena-dev@yahoogroups.com] On Behalf

> Of Kjetil Kjernsmo

> Sent: 10 December 2008 15:03

> To: jena-dev@yahoogroups.com

> Subject: Re: Property paths (was: Re: [jena-dev] ANN: Jena 2.5.7 and ARQ

> 2.6.0)

>

> On Tuesday 09 December 2008 18:26:53 Holger Knublauch wrote:

> > Yes absolutely. IMHO by far the most useful aspect here is the *

> > operator that allows users to get transitive sub/super classes and

> > properties at query time, e.g.

>

> Yeah, that's a good point!

>

> Andy, would this be material for another member submission?



The draft charter is currently out for approval by the Advisory Committee of the

W3C so the charter will not be updated to include another submission.



Influence will come in the WG through making a good case for it in the revisions

to "use case and requirements" document.  So (1) membership of the WG and (2)

making a good case, understanding the needs of everyone.



         Andy



>

> Kind regards

>

> Kjetil Kjernsmo

> --

> Senior Knowledge Engineer

> Mobile: +47 986 48 234

> Email: kjetil.kjernsmo@...

> Web: http://www.computas.com/

>

> |  SHARE YOUR KNOWLEDGE  |

>

> Computas AS  PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47 6783

> 1001

>

>

> ------------------------------------

>

> Yahoo! Groups Links

>

>

>

Max,



Thanks for the report.  I just now downloaded ARQ 2.6.0 from SourceForge

and executed the query:



PREFIX apf:     <http://jena.hpl.hp.com/ARQ/property#>

PREFIX :        <http://example/>

SELECT *

{

    ?subject apf:versionARQ ?version



}



and I get:



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

| subject                       | version |

===========================================

| <http://jena.hpl.hp.com/#arq> | "2.6"   |

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



Similarly for Jena 2.5.7, it that the same results,  although the jars

should be identical.



You will get "@version-major@.@version-minor@" if the development system

for ARQ is on the classpath first because the @-tokens are rewritten by

ant during the build process.  Just running from Eclipse-compiled source

code, and you get the @-form.  It is very easy to do that - I had to

check my own setting of classpath because it is quite keen to add the

development classes on the front of the classapth.



	 Andy





Max Gorbunov wrote:

> Hi Andy,

>

> On Mon, Dec 8, 2008 at 5:09 PM, Seaborne, Andy

> <andy_seaborne@... <mailto:andy_seaborne@...>>

> wrote:

>

>     We are pleased to announce new releases of Jena and ARQ:

>

>     Jena: http://prdownloads.sourceforge.net/jena/jena-2.5.7.zip

>

>     ARQ: http://prdownloads.sourceforge.net/jena/arq-2.6.0.zip

>

>

>

> {?subject apf:versionARQ ?version} gives "@version-major@.@version-minor@"

>

> --

> Sincerely yours,

>  Max Gorbunov

>  Senior Software Engineer

>  Grid Dynamics Consulting Services

>  mgorbunov@... <mailto:mgorbunov@...>



--

Hewlett-Packard Limited

Registered Office: Cain Road, Bracknell, Berks RG12 1HN

Registered No: 690597 England