[
https://issues.apache.org/jira/browse/JENA-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114588#comment-13114588
]
Paolo Castagna commented on JENA-62:
------------------------------------
> documentation
Will be on-line on the Jena website + README file.
> examples
Are here:
https://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/src/test/java/org/apache/jena/larq/examples/
Documentation can point/link/transclude(*) those.
> how LARQ is going to distributed, e.g. separate zip down, in ARQ zip? other?
LARQ is an optional extension of ARQ.
LARQ depends on ARQ and it does not work without ARQ.
I think it is unnecessary to have a separate zip download for LARQ. Unless all
the other modules have a separate zip down, in that case I'll do the same for
LARQ.
We (@ Talis) use LARQ together with TDB and/or Fuseki. I imagine other users
(as we saw from questions on jena-users and jena-dev) want to do the same.
There is an open issue to add LARQ to Fuseki: JENA-63.
LARQ can be an "optional" dependency added to Fuseki, or TDB.
>From an end-user point of view we need to consider: developer as well as
>end-users who might not want to develop (i.e. they download and run Fuseki).
For developers, LARQ Maven artifacts are perfectly fine. No need for a separate
zip download.
For end-users who do not want to develop but want to perform free text
searches, it would be better to have LARQ included in the Fuseki distribution.
So, to conclude, I propose to:
- not have a separate zip download for LARQ (if possible and if aligned to
what other modules will do, for example IRI).
- include LARQ in the Fuseki distribution (see JENA-63)
But, I am open to better suggestions.
(*) http://en.wikipedia.org/wiki/Transclusion
> Remove LARQ from ARQ
> --------------------
>
> Key: JENA-62
> URL: https://issues.apache.org/jira/browse/JENA-62
> Project: Jena
> Issue Type: Sub-task
> Components: ARQ, LARQ
> Reporter: Paolo Castagna
> Assignee: Andy Seaborne
>
> LARQ (as well as the Lucene dependency) needs to be removed from ARQ.
> ARQ will use the separate LARQ module.
> Since LARQ depends on Lucene and ARQ and we cannot have cycles in our
> dependency graph, ARQ cannot depend on LARQ.
> LARQ is a sort of plug-in for ARQ and we could load it and wire it in into
> ARQ if present in the classpath, in a similar way as showed here:
> http://markmail.org/thread/r5phyiuqkqsyi2xc
> Should we change the namespace for the property function?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
