#455: Integrate SPARQL Functions #511

simonstey · 2025-08-15T06:25:27Z

Closes #455

See this document rendered online here

…mically

simonstey · 2025-08-15T06:27:19Z

Do we want to have the SPARQL function sections being populated dynamically (from https://github.com/w3c/sparql-query/blob/main/sparql-ns.ttl ) or just updated on demand?

HolgerKnublauch · 2025-08-15T06:32:30Z

I am afraid the proper process would be:

We create a new TTL file that owl:imports the base file
In that file we add triples that are useful for rendering, e.g.:
a) grouping by category
b) deep links into the SPARQL spec
Then the content can be created dynamically, if we have a TTL parser available.
Maybe the TTL will be accepted by the sparql main document too, but I am not sure about the update cycle.

This is of course a lot of work but will be paying off on the long term because the info will be machine readable, e.g. for syntax-directed editors.

BTW the diff is huge - what happened?

simonstey · 2025-08-15T06:33:14Z

I am afraid the proper process would be:
1. We create a new TTL file that owl:imports the base file

2. In that file we add triples that are useful for rendering, e.g.:
   a) grouping by category
   b) deep links into the SPARQL spec

3. Then the content can be created dynamically, if we have a TTL parser available.

4. Maybe the TTL will be accepted by the sparql main document too, but I am not sure about the update cycle.
This is of course a lot of work but will be paying off on the long term because the info will be machine readable, e.g. for syntax-directed editors.

BTW the diff is huge - what happened?

I messed up the formatting.. will fix that next

afs · 2025-08-15T08:38:23Z

deep links into the SPARQL spec

If contributed back to RDF & SPARQL WG, I'm sure that could get incorporated into sparql-ns.

…ptions, categories, spec links.

….ttl

- Introduced examples for various SPARQL functions to enhance documentation and usability. - Added a new prefix for shnex-sparql to categorize examples. - Updated existing functions with example usage, including arithmetic, logical, string, numeric, and date functions. - Ensured all aggregate functions also include example usage for clarity.

HolgerKnublauch · 2025-08-16T08:25:21Z

shacl12-vocabularies/shnex-sparql.ttl

+	rdfs:label "W3C SHACL SPARQL Functions Vocabulary"@en ;
+	rdfs:comment "This vocabulary defines SPARQL functions for use with SHACL."@en ;
+	sh:declare [
+		sh:prefix "shnex" ;


Should declare sparql instead

addressed in 530b33d

shacl12-vocabularies/shnex-sparql.ttl

…ttl; fix isdefinedby URIs

…nd infix operator symbols. Add infix operators to selected functions

afs · 2025-08-17T11:21:31Z

SPARQL functions work on arguments that are single RDF terms. In [ sparql:agg-count ( ?values ) ] there isn't a term for ?values. (The pain of lists not being first class in RDF.)

SPARQL Aggregates tied into the way GROUP BY works (e.g. SUM(?X+1)) to produce sets - the design means the lists are solely within aggregates a don't leak out to general evaluation. SPARQL Aggregates are not directly usable as node expressions.

shnex has it's own aggregates and that's probably the way to go - I think that defining an adaption layer to get SPARQL aggregates to work is not that different from shnex's aggregates so there is no advantage to SPARQL aggregates.

shnex aggregates working on lists which integrates with the way shnex is e.g. sh:values.

[ sparql:coalesce ( ?optionalValue "default" ) ] is n-ary including a "no result" error.
It is also special because of it's error handling - ditto logical-and, and logical-or.

I don't see that node expressions can have variables other than the environment : #498 (comment)

afs · 2025-09-03T17:17:32Z

shacl12-vocabularies/shnex-sparql.ttl

+shnex-sparql:infixOperator
+	a rdf:Property ;
+	rdfs:label "infix operator"@en ;
+	rdfs:comment "Indicates the infix operator symbol used in SPARQL syntax for this function, enabling conversion from functional form to infix notation."@en ;


Where is infix used in node expressions?

It is not but the information is useful to capture IMHO, to produce human-readable syntax.

That would also need infix precedence.

That would also need infix precedence.

which means? 🤔

afs · 2025-09-03T17:21:59Z

shacl12-vocabularies/shnex-sparql.ttl

+	shnex-sparql:example """[ sparql:plus ( 38 4 ) ]""" ;
+	.
+
+sparql:subtract


This has the same URI as the entry in /ns/sparql.ttl.

But both graphs have triples with subject sparql:subtract and properties rdfs:comment and rdfs:isDefinedBy with different object.

It would be better to only include the SHACL Node Expression additions.

Yes, if necessary create a fresh property to avoid clashes.

@afs

This has the same URI as the entry in /ns/sparql.ttl.

what has the same URI? shnex-sparql:example ?

shacl12-node-expr/index.html

shacl12-vocabularies/shnex-sparql.ttl

TallTed · 2025-09-08T20:22:39Z

shacl12-vocabularies/shnex-sparql.ttl

+	rdfs:comment "This function tests whether a string matches a regular expression pattern, optionally with a specified flag (e.g., i for case-insensitive)."@en ;
+	shnex-sparql:category "string" ;
+	rdfs:isDefinedBy <http://www.w3.org/TR/sparql12-query/#func-regex> ;
+	shnex-sparql:example """[ sparql:regex ( "hello123" "[0-9]+" ) ]""" ;


Where does the "specified flag" go? It seems this should have either multiple examples, or one that includes the optional "specified flag".

Suggested change

shnex-sparql:example """[ sparql:regex ( "hello123" "[0-9]+" ) ]""" ;

shnex-sparql:example """[ sparql:regex ( "HeLLo123" "^hello" "i" ) ]""" ;

TallTed · 2025-09-08T20:26:31Z

shacl12-vocabularies/shnex-sparql.ttl

+sparql:day
+	a sparql:Function ;
+	rdfs:label "day"@en ;
+	rdfs:comment "This function returns the day component of an xsd:dateTime or xsd:date."@en ;


Suggested change

rdfs:comment "This function returns the day component of an xsd:dateTime or xsd:date."@en ;

rdfs:comment "This function returns the day (0–31) component of an xsd:dateTime or xsd:date."@en ;

Suggested change

rdfs:comment "This function returns the day component of an xsd:dateTime or xsd:date."@en ;

rdfs:comment "This function returns the day (1-31) component of an xsd:dateTime or xsd:date."@en ;

shouldn't it be 1-31 then?

TallTed · 2025-09-08T20:26:57Z

shacl12-vocabularies/shnex-sparql.ttl

+sparql:month
+	a sparql:Function ;
+	rdfs:label "month"@en ;
+	rdfs:comment "This function returns the month component of an xsd:dateTime or xsd:date."@en ;


Suggested change

rdfs:comment "This function returns the month component of an xsd:dateTime or xsd:date."@en ;

rdfs:comment "This function returns the month component (0–12) of an xsd:dateTime or xsd:date."@en ;

Suggested change

rdfs:comment "This function returns the month component of an xsd:dateTime or xsd:date."@en ;

rdfs:comment "This function returns the month component (1-12) of an xsd:dateTime or xsd:date."@en ;

shouldn't it be 1-12 then?

TallTed · 2025-09-08T20:28:58Z

shacl12-vocabularies/shnex-sparql.ttl

+sparql:seconds
+	a sparql:Function ;
+	rdfs:label "seconds"@en ;
+	rdfs:comment "This function returns the second component (0–60, including leap seconds) of an xsd:dateTime value."@en ;


If this is "including leap seconds", the range must reach 61 (possibly higher; I do not know the maximum number of leap seconds that might be applied in any given year).

Suggested change

rdfs:comment "This function returns the second component (0–60, including leap seconds) of an xsd:dateTime value."@en ;

rdfs:comment "This function returns the second component (0–61, including leap seconds) of an xsd:dateTime value."@en ;

This counting from zero.
60 would be the leap second.

But xsd:dateTime does not support leap seconds.
"a decimal number greater than or equal to 0 and less than 60."
Discussion: https://www.w3.org/TR/xmlschema11-2/#d-t-values

in which case it should actually be:

Suggested change

rdfs:comment "This function returns the second component (0–60, including leap seconds) of an xsd:dateTime value."@en ;

rdfs:comment "This function returns the second (0–59) component of an xsd:dateTime value."@en ;

59.5 is legal.

so [0,60) then?

what about removing the value range altogether?

Suggested change

rdfs:comment "This function returns the second component (0–60, including leap seconds) of an xsd:dateTime value."@en ;

rdfs:comment "This function returns the seconds component of an xsd:dateTime value."@en ;

what about removing the value range altogether?

+1

afs · 2025-09-18T09:28:54Z

s/second/seconds/ to reduce the ambiguity of "the second component of".

…gnore entries

feat: ✨ automatically fetch sparql functions and create sections dyna…

efb154b

…mically

simonstey self-assigned this Aug 15, 2025

simonstey linked an issue Aug 15, 2025 that may be closed by this pull request

Support all SPARQL functions as Node Expressions #455

Open

style: 🎨 restore formatting of sections

350be06

simonstey added 3 commits August 16, 2025 07:29

Import SPARQL function triples into shnex-sparql.ttl — labels, descri…

0cdd709

…ptions, categories, spec links.

Render SPARQL functions table in node-expr UI from local shnex-sparql…

f28f2dd

….ttl

HolgerKnublauch reviewed Aug 16, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Outdated Show resolved Hide resolved

HolgerKnublauch reviewed Aug 16, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Outdated Show resolved Hide resolved

HolgerKnublauch reviewed Aug 16, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Show resolved Hide resolved

HolgerKnublauch reviewed Aug 16, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Show resolved Hide resolved

simonstey added 3 commits August 17, 2025 08:50

chore: Normalize SPARQL function labels to lowercase in shnex-sparql.…

530b33d

…ttl; fix isdefinedby URIs

refactor: 💬 Replace dc:description with rdfs:comment

753311e

feat: add property definitions for function categorization, example a…

fdfad05

…nd infix operator symbols. Add infix operators to selected functions

afs mentioned this pull request Sep 3, 2025

Policy for expression evaluation for call-by-URI. w3c/sparql-query#280

Open

afs reviewed Sep 3, 2025

View reviewed changes

TallTed reviewed Sep 8, 2025

View reviewed changes

shacl12-node-expr/index.html Outdated Show resolved Hide resolved

TallTed reviewed Sep 8, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Outdated Show resolved Hide resolved

TallTed reviewed Sep 8, 2025

View reviewed changes

shacl12-vocabularies/shnex-sparql.ttl Outdated Show resolved Hide resolved

TallTed reviewed Sep 8, 2025

View reviewed changes

fix: update comments for clarity in SPARQL functions and update .giti…

5479885

…gnore entries

	shnex-sparql:example """[ sparql:regex ( "hello123" "[0-9]+" ) ]""" ;
	shnex-sparql:example """[ sparql:regex ( "HeLLo123" "^hello" "i" ) ]""" ;

	rdfs:comment "This function returns the day component of an xsd:dateTime or xsd:date."@en ;
	rdfs:comment "This function returns the day (0–31) component of an xsd:dateTime or xsd:date."@en ;

#455: Integrate SPARQL Functions #511

Are you sure you want to change the base?

#455: Integrate SPARQL Functions #511

Uh oh!

Conversation

simonstey commented Aug 15, 2025

Uh oh!

simonstey commented Aug 15, 2025

Uh oh!

HolgerKnublauch commented Aug 15, 2025

Uh oh!

simonstey commented Aug 15, 2025

Uh oh!

afs commented Aug 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

afs commented Aug 17, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

afs Sep 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

afs commented Sep 18, 2025

Uh oh!

Uh oh!

afs commented Aug 15, 2025 •

edited

Loading

afs Sep 18, 2025 •

edited

Loading