GLEEN Downloads
Current Release:
- Version 0.6.0 posted here briefly had a few issues that have been addressed. Please download this new version. The fixed issues were:
- Problems with concatenation
- Pre-built jar was not included in zip file
- Source tree included SVN folders
- Download GLEEN V0.6.1 beta, for ARQ 2.2
- Pre-built GLEEN library and source code included in archive
- Apache 2.0 open source license
- GLEEN requires additional libraries which are most likely already present in any Jena/ARQ application. However, if you need them, they can be downloaded from the following sites:
- ARQ and its associated libraries which are included in the ARQ distribution (tested with ARQ version 2.2)
Old Versions:
- GLEEN
V0.5.1 beta
- Download GLEEN V0.5.1 beta, for ARQ 2.1 (zip file includes gleen.jar as well as the ANTLR runtime library 3.0.1)
- GLEEN requires additional libraries (jena.jar, arq.jar, and commons-logging-1.1.jar) which are most likely already present in any Jena/ARQ application. However, if you need them, they can be downloaded from the following sites:
- Notes regarding this version:
- Uses ANTLR runtime (grammar parser was generated using ANTLR parser generator)
- In ARQ version 2.0 and 2.1, the query prefixes were not accessible from a property function. The OnPath property function requires these prefix mappings to expand the prefixes in the path expression. GLEEN V0.5.1 included a work-around, but requires users of the function to add a line of code, within their project, at the point were the QueryExecution is created.
The following utility function puts the query prefix mapping into the Context object.
- edu.washington.sig.gleen.util.ContextUtil.setQueryPrefs(queryExecution, query);
- Add the above line immediately after the creation of the QueryExecution.
- This allows the OnPath property function to expand the prefixes in the path expression.
- If you do not add the above line, you must either use prefixes defined in the data source (and in the query or it won't execute) or you must use full URIs in your path expressio
- There are limits to the complexity of expressions allowed by the grammar. You are basically allowed two "levels" of nesting. In a "level one" expression you can apply the *, +, or ? operator to individual properties or alternations of properties and then concatenate these. In a "level two" expression you can apply the *, +, or ? operator to a level one expression or alternation of level one expressions. You cannot, for example, apply a + operator to a level two expression. This is a deliberate limitation of the complexity of allowed expression.