- From: John Snelson <John.Snelson@marklogic.com>
- Date: Tue, 18 Feb 2020 11:32:05 +0000
- To: Gregory Williams <greg@evilfunhouse.com>
- CC: "public-sparql-12@w3.org" <public-sparql-12@w3.org>
Received on Tuesday, 18 February 2020 11:32:37 UTC
On 17/02/2020 18:19, Gregory Williams wrote: Hi John, Thanks for the feedback. On Feb 10, 2020, at 3:05 AM, John Snelson <John.Snelson@marklogic.com<mailto:John.Snelson@marklogic.com>> wrote: Hi Jerven, Gregory, Thanks for this! Looks like a good start. I can't open github issues that aren't labelled "New Feature", which doesn't seem to fit the situation. Here are my comments: 1) We should document the mapping of SPARQL function names to F&O function names. For instance, I'm assuming YEAR(xs:date) maps to fn:year-from-date(). I’m not opposed to this, but since the SEP does not include the exact language that would be applied to the spec, I didn’t think this was necessary. In a document that is proposing spec text (which this SEP could be updated to become), I would think the sections enumerating the function definitions (like YEAR in https://www.w3.org/TR/sparql11-query/#func-year) would include similar language to existing definitions (which do include reference references where appropriate). Well, the SEP names functions and leaves us to assume what the functions should do. They need some definition, and I figured the easiest thing to do would be to point to existing definitions in F&O. John -- John Snelson, Principal Engineer http://twitter.com/jpcs MarkLogic Corporation http://www.marklogic.com
Received on Tuesday, 18 February 2020 11:32:37 UTC