The format is really useful to be able to do "on-the-fly" SPARQL duration and date calculations but
has a funky notation, e.g. "P12M" for 12 months, hence I wonder whether this is causing a problem or its something I haven't defined correctly.
Currently when I try to import an instance of a class that is using the data property "has XSD duration" (time ontology) with range "xsd.duration", the result is a parser error
"ValueError: Cannot read literal of datatype 749!".
I've just added xsd:duration support in Owlready development version. Durations are translated into Python timedelta objets (and suffer all associated limitations, e.g. 1 month is considered as 30 days).
In addition, I've added DATETIME_ADD, DATETIME_SUB, DATE_ADD, DATE_SUB SPARQL function for computing on dates, e.g. :
Thank you very much for the incredibly fast turn-around!
I was going to suggest the Isodate Package for some of the datetime and duration parsing to help ease the burden.
I have two questions:
1. With the functional implementation currently employed, will the functions have to be called in the select statement or can they be called anywhere within the SPARQL query? e.g. within a BIND statement.
2. Apologies for the beginner question, how would I install the development build?