ISSUE-45: Should SPARQL be a built-in extension language

SPARQL-extension

Should SPARQL be a built-in extension language

State:

CLOSED

Product:

SHACL Spec

Raised by:

Holger Knublauch

Opened on:

2015-04-17

Description:

I think there is enough agreement that SHACL should have an "extension" language to cover cases not addressed by the core vocabulary, and to define new high-level terms (templates). I believe we should get the question clarified whether SPARQL is such an extension language. This question is independent of whether other languages such as JavaScript could also be supported - that would be another ISSUE.

PROPOSAL: SHACL should include SPARQL as an extension language.

Related Actions Items:

No related actions

Related emails:

1. Re: ISSUE-131: Proposal to close (from kcoyle@kcoyle.net on 2016-10-13)
2. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from holger@topquadrant.com on 2015-04-20)
3. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from holger@topquadrant.com on 2015-04-20)
4. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from kcoyle@kcoyle.net on 2015-04-17)
5. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from simon.steyskal@wu.ac.at on 2015-04-17)
6. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from holger@topquadrant.com on 2015-04-17)
7. shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from sysbot+tracker@w3.org on 2015-04-17)
8. Re: shapes-ISSUE-45 (SPARQL-extension): Should SPARQL be a built-in extension language [SHACL Spec] (from kcoyle@kcoyle.net on 2015-04-16)

Related notes:

Display change log