v0.7.0

Features

• Run SPARQL queries over the workspace. A "▶ Run query" code lens above
  each query runs it over the workspace's files as the editor has them
  (unsaved edits included) and opens the results as Markdown, beside the
  query in VS Code, in any LSP editor through window/showDocument. It runs
  on its own thread with query.timeoutSeconds (default 30),
  query.maxRows (default 1000) and query.maxBufferedRows (default
  10 000 000, about 1 GB: a query that keeps more rows in memory to sort,
  group, deduplicate or join them is stopped). Query files of the same name
  get results files of their own (people.md, people-2.md).
  turtle-lsp query (--max-buffered-rows) does the same from the
  command line, with table, JSON, CSV, TSV or Turtle output. The browser editor has a ▶ Run button (Ctrl/Cmd+Enter) with a results pane. The default
  graph is the union of every file's triples; named graphs, updates and
  endpoints are out of scope.
• Reference lenses: "N references" above each subject a file describes
  (Turtle, TriG, N-Triples, N-Quads, JSON-LD); clicking lists them (VS Code's
  references view, Neovim's quickfix list, the browser editor's references
  view). Counted only when shown. Setting
  codeLens.references (default on).
• Workspace diagnostics (diagnostics.workspace, default off): problems
  in files that are not open, computed in the background with the same
  checks as turtle-lsp check, and kept up to date as files change. An edit
  pauses the work, so typing is not slowed.
• imports.unresolved: "ignore" keeps SHACL results at full severity
  while imports are unresolved, instead of softening them to warnings with a
  note ("soften", the default). For projects that validate without their
  imports, as pySHACL does.

Fixes

• VS Code passed shacl.onType to the server only after a settings change,
  not at start.
• A SHACL-SPARQL query stops after 10 s, with a warning on its sh:select or
  sh:ask (shacl-sparql-timeout) that its constraint's results are
  missing. Before, one slow constraint (two patterns with nothing in common)
  could keep validation busy for minutes, and edits could not stop it.

Internals

• The graph and the SPARQL dataset adapter moved from SHACL to a shared
  rdf module; server commands are parsed in their own module.
• spareval is patched (vendor/spareval) so the query time limit and
  cancellation also stop joins that combine rows in memory. Unpatched, a
  cross product or two unconnected property paths ran on past the limit.

What's Changed

• Lsp capability by @abhishekkundu25 in #6

New Contributors

• @abhishekkundu25 made their first contribution in #6

Full Changelog: v0.6.2...v0.7.0

v0.6.2

Features

• Ill-typed literals get a warning (invalid-literal) on the literal,
  naming its datatype: "twelve"^^xsd:integer gives "'twelve' is not a
  valid xsd:integer". Checked are the lexical forms of the numeric types
  (with the ranges of xsd:byte, xsd:unsignedInt and the other bounded
  integers), xsd:boolean, the date and time types (days per month and
  leap years included), the durations, xsd:hexBinary, xsd:base64Binary,
  xsd:language and rdf:JSON, in Turtle, TriG, N-Triples, N-Quads and
  JSON-LD, in the editor and in turtle-lsp check. SPARQL queries are not
  checked. SHACL sh:datatype checks the same lexical forms, so it now also
  rejects ill-formed g* dates, durations, binaries, xsd:language and
  rdf:JSON values.

Fixes

• Fetching owl:imports and JSON-LD contexts over HTTPS uses rustls-webpki
  0.103.16 and webpki-roots 1.0.10, which no longer trust the distrusted
  emSign intermediates (RUSTSEC-2026-0381, RUSTSEC-2026-0382).

Full Changelog: v0.6.1...v0.6.2

v0.6.1

Fixes

• The VS Code Marketplace page described JSON-LD as it was before 0.6.0
  ("completion, rename and formatting ... not there yet"); it now lists what
  0.6.0 does, and the extension's name and description include JSON-LD.
• The browser toolbox names pasted JSON-LD pasted.jsonld instead of
  pasted.trig, and its page descriptions include JSON-LD.

Tests and CI

• CI is green on Windows again. Two SHACL tests removed a folder their
  server was still running in, which Windows refuses; the failure skipped
  stopping the server, and the server held the test run open. A server a
  test forgets to stop now fails its file instead of hanging the run.
• The JSON-LD timing tests compare against Turtle on the same machine
  instead of fixed times, so slower CI runners pass.
• CI runs the build, the Rust tests and the Node tests as separate steps
  with their own time limits (the Node tests 5 minutes).

Full Changelog: v0.6.0...v0.6.1

v0.6.0

Features

• turtle-lsp check: reports from the command line what the editor
  shows (syntax errors, prefixes, vocabulary lints, SHACL validation) at
  file:line:col, for coding agents, CI and pre-commit. Exit codes 0 (clean),
  1 (problems) and 2 (the tool failed). Output formats concise, json,
  github (workflow annotations) and sarif (code scanning). --fix applies
  the safe quick fixes.
• turtle-lsp format: formats files in place; --check and --diff
  change nothing and exit 1 if a file would change.
• turtle-lsp.json: optional settings file at the workspace root, with
  the keys of the editor settings. The command line and the server both read
  it; the editor's settings override it.
• .pre-commit-hooks.yaml with the hooks turtle-lsp-check and
  turtle-lsp-format.
• JSON-LD (.jsonld, language id jsonld; JSON-LD 1.1), with an
  engine that keeps the source position of every triple:
  • diagnostics: JSON syntax errors with recovery (json-syntax), context
    errors (jsonld-context), keys the context does not define
    (jsonld-undefined-term), invalid IRIs and language tags
    (invalid-iri, invalid-language-tag), and the vocabulary lints on
    IRIs reached through the context;
  • JSON-LD files join the workspace: their terms count in Turtle and SPARQL
    files and the other way round, SHACL shapes in either format validate
    their data with each result on the key, value or @id, and named graphs
    follow the TriG rules;
  • hover on keys and @type values, go to definition on @vocab keys, and
    an outline of node objects;
  • turtle-lsp check and the browser editor cover them;
  • remote contexts come from workspace files, the import cache or the
    bundled schema.org, ActivityStreams, Verifiable Credentials and DID
    contexts; the network is used only with imports.network or
    --network.
  • W3C JSON-LD 1.1 suites: toRdf 443 pass, expand 365, remote-doc 6; 2
    known failures in the runner's oracle; the rest (JSON-LD 1.0, options
    the engine does not have, document loading) out of scope. On 364 public
    documents, 339 graphs match oxjsonld's; the other 25 are known oxjsonld
    differences from the spec.
  • Not yet: compaction, flattening, framing and .json files.
• Editing inside JSON-LD files:
  • completion in keys and @type values from the context in force at the
    cursor, workspace properties under @vocab and prefix:local names;
    completing a known prefix the context lacks adds it to the @context
    (idea credited to SWLS);
  • go to definition on a term reaches its @context entry, also in a
    context file of the workspace; references and highlights on terms;
  • rename of terms and keyword aliases (the @context entry and every use),
    and of IRIs from any file, each JSON-LD use rewritten in its own form;
    unsafe renames are refused with the reason;
  • formatting in the editor, turtle-lsp format and the browser, keeping
    the same JSON value;
  • semantic tokens for keywords, properties and classes;
  • the outline nests a named graph's nodes under the graph.
• jsonld-undefined-prefix: a warning when rdfs:label and the like
  name a prefix the @context doesn't define, which JSON-LD reads as an IRI
  with the scheme rdfs:; the quick fix (also check --fix) adds the prefix
  to the @context.

Performance

• SHACL-SPARQL constraints run once for all focus nodes of a shape
  instead of once per node. Validating 30 MB of generated TriG with 71
  SPARQL constraints per file went from 26 s to 0.6 s in the editor and the
  command line, with identical results.
• JSON-LD on a 30,000-line file: open to first diagnostics 7.5 ms
  (Turtle of the same length 5.9 ms), a keystroke 7.3 ms (Turtle 5.0 ms),
  hover 0.1 ms, completion 0.4 ms, formatting the whole file 2.1 ms.
  tests/jsonld_budget.rs holds release builds to opening within 3x Turtle
  and a keystroke under 10 ms.

Fixes

• "Did you mean" now counts swapping two neighbouring letters as one edit, so
  foaf:nmae and rdfs:lable get a suggestion.

Full Changelog: v0.5.2...v0.6.0

v0.5.2

Features

• Neovim with lazy.nvim in one step: this repository is a Neovim plugin.
  { "abhishekkundu25/turtle-lsp", version = "*", config = function() vim.lsp.enable("turtle_lsp") end } installs the server (downloaded for
  your machine from the release and checked against its checksums, or built
  with cargo where there is no download), its config for Turtle, TriG,
  N-Triples, N-Quads and SPARQL, the .ttl and .nq file types, and the
  modeline fix. No Rust needed.
• Each release has the server on its own for other editors:
  turtle-lsp-<platform>.tar.gz (.zip on Windows) for macOS, Linux and
  Windows, with checksums and build attestations.

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Features

• Hover's "Described in core.ttl:18" is a link that opens the file at that
  line.
• Try it in the browser: the RDF Editor runs this server,
  compiled to WebAssembly, in a browser tab: a VS Code-like editor with the
  explorer, Problems, SHACL as you type, rename across files, quick fixes,
  Vim mode and a dark or light theme. Nothing is uploaded. A toolbox page
  formats, validates and checks files without the editor. The server's
  behaviour is unchanged.

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Features

• N-Quads (.nq, language id nquads): syntax errors with recovery per
  line, highlighting, hover, label hints, navigation, an outline grouped by
  graph, and formatting (one quad per line). Its facts join the workspace like
  a TriG file's. W3C N-Quads suites (RDF 1.1 and 1.2): 155/155.
• SPARQL (.rq, .sparql, .ru, language id sparql; queries and
  updates, SPARQL 1.1 and 1.2), built on the same knowledge of the workspace
  and the vocabularies as Turtle:
  • diagnostics as you type: syntax errors at the token where the query stops
    making sense, undeclared, unused, duplicate and redefined prefixes,
    unknown or deprecated vocabulary terms, own terms nothing describes, and
    projected variables the WHERE clause never binds;
  • completion of keywords by context, variables, prefixes (adding the
    PREFIX line), terms ranked by position and by the ontology, and
    built-in functions;
  • hover, label hints, go to definition (terms, prefixes, variables),
    references and highlights (variables scoped by subquery), semantic
    highlighting, folding and an outline;
  • rename of variables, prefixes, and terms across Turtle, N-Quads and SPARQL
    files in both directions;
  • formatting that never changes what the query means (the output must parse
    to the same algebra), and refuses queries with errors;
  • quick fixes and refactorings: add a missing PREFIX, add all, remove an
    unused one, fix a misspelled term, organise prefixes, shorten or expand
    IRIs.
    W3C SPARQL 1.1 and 1.2 syntax suites: 425/426. Prefixes from prefixes.ttl
    and turtle.prefixes count as declared; a query never makes a term look
    described. The server never runs a query.
• The VS Code extension registers N-Quads and SPARQL with their own grammars,
  and is listed as Turtle RDF & SPARQL Language Server (TTL, OWL, SHACL);
  the README shows the Neovim setup for nquads and sparql buffers.

Fixes

• SHACL-SPARQL queries with a local name of two dots or more
  (ec:1.1.1.353) are no longer reported as syntax errors.
• A SHACL-SPARQL query nested deep enough to overflow the parser's recursion
  is reported instead of crashing validation.
• Two crashes in locating a SHACL-SPARQL syntax error next to a multi-byte
  character are fixed.

Testing

• npm run corpus also checks N-Quads against oxttl (a Web Data Commons
  dump) and 1,317 real SPARQL queries (SIB sparql-examples) against
  spargebra and the formatter.

Full Changelog: v0.4.2...v0.5.0

v0.4.2

Fixes

• Renaming a shared prefix back to a name that some other file declares for
  itself is no longer refused when that file does not use the prefix being
  renamed (for example renaming ex: to eg: and then back to ex:).

Extension

• The Marketplace page now lists SHACL validation, owl:imports,
  formatting, refactorings and TriG/N-Triples support.

Full Changelog: v0.4.1...v0.4.2

v0.4.1

Fixes

• Renaming a shared prefix: renaming a prefix that a prefixes.ttl
  declares, from that file or from a file that uses it, now renames it in
  every file that takes it from there (open or not), and not in files that
  declare it themselves. Before, only the current file changed, which left
  the other files with an undeclared prefix. A rename to a name the affected
  files already declare or use is refused, and a prefix from the
  turtle.prefixes setting is refused with a pointer to the setting.

Full Changelog: v0.3.0...v0.4.1

v0.3.0

Features

• SHACL-SPARQL: sh:sparql constraints (sh:SPARQLConstraint with
  sh:select) on node and property shapes, with pre-bound $this, $PATH,
  $currentShape and $shapesGraph, sh:prefixes / sh:declare, message
  templates ({?value}, {$this}) and sh:deactivated; SPARQL-based targets
  and SPARQL-based constraint components. W3C SHACL-SPARQL suite: 23/23.
• SPARQL queries in shapes are checked as you type: syntax errors and
  undeclared prefixes (errors, on the exact spot in the query), and the
  constructs SHACL-SPARQL forbids (MINUS, VALUES, SERVICE, LATERAL, rebinding
  a pre-bound variable) as warnings.
• SHACL validation while typing: the workspace is validated about a
  second after typing stops, on the unsaved text; saving still validates at
  once. Setting turtle.shacl.onType (default on) turns it off.
• Progress for indexing, owl:imports resolution and SHACL runs that
  last more than 200 ms, for clients that support work done progress. A SHACL
  run ends with a summary such as "2 errors, 1 warning in 2 files".
• The undeclared-prefix quick fix can also add the owl:imports of the
  workspace ontology that defines the namespace.

Fixes

• Unknown-term warnings no longer appear on terms the workspace or a resolved
  import describes, and files with thousands of them stay fast (a 2.3 MB file
  went from 2.3 s per edit to about 60 ms).
• SHACL errors that unresolved owl:imports could change are shown as
  warnings that name the missing imports.
• The formatter's safety check keeps the document's base IRI, so documents
  with relative IRIs are not refused.

Testing

• npm run corpus checks the parser against oxttl and the formatter's
  properties on public RDF files (68 cases, 2.17 million triples), and
  measures the server on each.

Full Changelog: v0.2.0...v0.3.0