On Fri, Aug 9, 2013 at 2:38 PM, Rob Vesse (JIRA) <j...@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/JENA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735123#comment-13735123]
>
> Rob Vesse commented on JENA-507:
> --------------------------------
>
> Yes, that is why I mentioned the XPath 3 functions since those now include
> many of these functions so that would seem like an appropriate standard
> namespace to use as far as possible
>
> Supporting the Stardog namespace for relevant functions is also another
> option to boost portability (both for ARQ and dotNetRDF)
>

We'd be happy to change from our custom namespace to use the xpath 3
namespace for those functions.  We're actually at a good point for this,
we're finalizing our 2.0 release, so this would be a good time to make that
switch.  Otherwise, we'd wait until at least 2.1.

Cheers,

Mike


>
> > Add support for Leviathan extension functions to ARQ
> > ----------------------------------------------------
> >
> >                 Key: JENA-507
> >                 URL: https://issues.apache.org/jira/browse/JENA-507
> >             Project: Apache Jena
> >          Issue Type: Improvement
> >          Components: ARQ
> >            Reporter: Rob Vesse
> >            Assignee: Rob Vesse
> >              Labels: extension, functions, sparql
> >   Original Estimate: 336h
> >          Time Spent: 4h
> >  Remaining Estimate: 332h
> >
> > The Leviathan Function library is a set of extension functions present
> in dotNetRDF's SPARQL engine.  It contains a useful set of numeric
> functions which would be useful to have available in core ARQ and would
> boost portability of queries between ARQ and dotNetRDF (note that dotNetRDF
> already supports ARQs extension functions).
> > See
> https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/SPARQL/Leviathan%20Functionsfor
>  definition of functions
> > Note that some of these overlap with new XPath 3 functions but for
> portability purposes there is no reason not to support these as well since
> most are relatively trivial to implement.  I will file a separate issue for
> supporting XPath 3 functions.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

Reply via email to