Package Exports
- @sib-swiss/sparql-editor
- @sib-swiss/sparql-editor/dist/sparql-editor.js
- @sib-swiss/sparql-editor/dist/sparql-editor.min.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@sib-swiss/sparql-editor) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
A standard web component to easily deploy a user-friendly SPARQL query editor for a specific SPARQL endpoint, based on the popular YASGUI editor with advanced autocomplete for predicates based on classes.
The editor retrieves metadata about the endpoint by directly querying the SPARQL endpoint, so all you need to do is to properly document your endpoint. Reducing the need for complex infrastructure, while making your SPARQL endpoints easier to query for users and machines.
Prefixes are automatically pulled from the endpoint using their definition defined with the SHACL ontology (
sh:prefix
/sh:namespace
).The prefixes/namespaces are retrieved with this query:
PREFIX sh: <http://www.w3.org/ns/shacl#> SELECT DISTINCT ?prefix ?namespace WHERE { [] sh:namespace ?namespace ; sh:prefix ?prefix } ORDER BY ?prefix
Example SPARQL queries defined using the SHACL ontology are automatically pulled from the endpoint (queries are defined with
sh:select|sh:ask|sh:construct|sh:describe
, and their human readable description withrdfs:comment
). Checkout thesparql-examples
project for more details.The example queries are retrieved with this SPARQL query:
PREFIX sh: <http://www.w3.org/ns/shacl#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT ?sq ?comment ?query WHERE { ?sq a sh:SPARQLExecutable ; rdfs:comment ?comment ; sh:select|sh:ask|sh:construct|sh:describe ?query . } ORDER BY ?sq
Autocomplete possibilities for properties and classes are automatically pulled from the endpoint based on VoID description present in the triplestore (
void:linkPredicate|void:property
andvoid:class
). The proposed properties are filtered based on the predicates available for the class of the subject related to where your cursor is 🤯. Checkout thevoid-generator
project to automatically generate VoID description for your endpoint.VoID description is retrieved using this SPARQL query:
PREFIX up: <http://purl.uniprot.org/core/> PREFIX void: <http://rdfs.org/ns/void#> PREFIX void-ext: <http://ldf.fi/void-ext#> SELECT DISTINCT ?subjectClass ?prop ?objectClass ?objectDatatype WHERE { { ?cp void:class ?subjectClass ; void:propertyPartition ?pp . ?pp void:property ?prop . OPTIONAL { { ?pp void:classPartition [ void:class ?objectClass ] . } UNION { ?pp void-ext:datatypePartition [ void-ext:datatype ?objectDatatype ] . } } } UNION { ?linkset void:subjectsTarget ?subjectClass ; void:linkPredicate ?prop ; void:objectsTarget ?objectClass . } }
👆️ You can try it for a few SPARQL endpoints of the SIB, such as UniProt and Bgee, here: sib-swiss.github.io/sparql-editor
🚀 Use
Import from a CDN:
<script type="module" src="https://unpkg.com/@sib-swiss/sparql-editor"></script>
Or install with a package manager in your project:
npm install --save @sib-swiss/sparql-editor # or pnpm add @sib-swiss/sparql-editor
Use the custom element in your HTML/JSX/TSX code:
<sparql-editor endpoint="https://sparql.uniprot.org/sparql/"></sparql-editor>
[!WARNING]
Metadata are retrieved by a few lightweight queries sent from client-side JavaScript when the editor is initialized, so your SPARQL endpoint should accept CORS (either from *, which is recommended, or just from the URL where the editor is deployed)
⚙️ Available attributes
You can customize a few optional attributes when calling the custom element:
examples-repo-add-url
: the URL to directly add the query to the git repository where the query examples for this endpoint are stored through the GitHub web UI,examples-repository
: the URL to the git repository where the query examples for this endpoint are stored (automatically generated fromexamples-repo-add-url
if you provide it),examples-namespace
: the namespace used when saving a query as example (defaults to the endpoint URL + /.well-known/sparql-examples/ when not specified),examples-on-main-page
: the number of examples displayed on the main page (defaults to 10),style="--btn-color / --btn-bg-color"
: buttons color.
You can also provide other HTML elements to be included under the SPARQL examples (e.g. about information and links to relevant resources):
<sparql-editor
endpoint="https://www.bgee.org/sparql/"
examples-repo-add-url="https://github.com/sib-swiss/sparql-examples/new/master/examples/Bgee"
examples-repository="https://github.com/sib-swiss/sparql-examples"
examples-namespace="https://sparql.uniprot.org/sparql/.well-known/sparql-examples/"
examples-on-main-page="10"
style="--btn-color: white; --btn-bg-color: #00709b;"
>
<h1>About</h1>
<p>This SPARQL endpoint contains things</p>
</sparql-editor>
📝 Basic example
No need for a complex project you can integrate SPARQL editor in any HTML page by importing from a CDN!
Create a index.html
file with:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>SPARQL editor dev</title>
<meta name="description" content="SPARQL editor demo page" />
<link rel="icon" type="image/png" href="https://upload.wikimedia.org/wikipedia/commons/f/f3/Rdf_logo.svg" />
<!-- Import the module from a CDN -->
<script type="module" src="https://unpkg.com/@sib-swiss/sparql-editor"></script>
</head>
<body>
<div>
<sparql-editor
endpoint="https://www.bgee.org/sparql/"
examples-repo-add-url="https://github.com/sib-swiss/sparql-examples/new/master/examples/Bgee"
examples-on-main-page="10"
style="--btn-color: white; --btn-bg-color: #00709b;"
>
<h1>About</h1>
<p>This SPARQL endpoint contains...</p>
</sparql-editor>
</div>
</body>
</html>
Then just open this HTML page in your favorite browser.
You can also start a basic web server with NodeJS or Python (recommended):
npx http-server
# or
python -m http.server
🛠️ Development
Requirement: NodeJS installed.
Clone the repository obviously, and get into the repository root folder.
Install:
npm install
Run in development:
npm run dev
Auto format code with prettier:
npm run fmt
Lint with eslint (we recommend to install the ESLint
extension on VSCode):
npm run lint
Build for production in the dist
folder:
npm run build
Run the demo pages locally:
npm run demo
Update dependencies to the latest available versions:
npx npm-check-updates -u
🏷️ Release
To create a new release:
Login with
npm adduser
if not already doneUpgrade version in
package.json
Run release script:
npm run release
Create release on GitHub
🤝 Credits
Thanks to: