SSTIM Workbench mark

Non-normative reference software

SSTIM Workbench

Build sensory-stimulation patches and examine the knowledge behind them. SSTIM Workbench brings Patch Studio and Graph Navigator together with SSTIM, the open formalized knowledge standard for techniques, parameters, exposure, safety metadata, and evidence.

Non-clinical scope. SSTIM Workbench supports exploration and authoring. It does not diagnose, treat, cure, or prevent any condition, and makes no claim of clinical efficacy. Read the scope.

Where the Workbench fits

The SSTIM ecosystem centers on SSTIM, the open formalized knowledge standard. It also includes its reference tooling and community, and sensory-stimulation applications and initiatives whether or not they currently adopt or support SSTIM. BioSynCare is a separate commercial application in that ecosystem and the center of its own overlapping application ecosystem.

Open formalized knowledge standard

SSTIM

The specification, RDF vocabulary, semantic infrastructure, documentation, interoperability work, and shared identifiers at the center of the SSTIM ecosystem.

Non-normative reference software
SSTIM Workbench isotype

SSTIM Workbench

The executable environment you are using now. Graph Navigator, Patch Studio, the SPARQL workbench, presets, and supporting engines exercise SSTIM without making Workbench behavior normative.

Open community

W3C Sensory Stimulation Vocabulary Community Group

The independent open forum in which SSTIM is developed. It is part of the SSTIM ecosystem; Community Group work is not a W3C Recommendation or W3C-endorsed technology.

Separate commercial application
BioSynCare isotype

BioSynCare

A separate application with its own private code, catalog, and data. BioSynCare adopts and contributes to SSTIM, participates in the SSTIM ecosystem, and has an application-centered ecosystem that overlaps with it.

Ecosystem inclusion records a relationship; it does not imply ownership, affiliation, endorsement, or application-wide conformance.

Explore the complete architecture and directory

Preserved provenance: BSC and BSC Lab still appear where they identify historical frameworks, implementation records, protocols, citations, or stable IRIs. They are not peer brands in the current public architecture and are not mechanically renamed.

What you can do here

Every screen below is reachable from the dock at the bottom of the window. This is a working application, not a landing page β€” jump straight in from any card.

Graph Navigator Semantic exploration

Browse SSTIM as a connected knowledge graph: ontology terms, controlled vocabulary, public reference records, and the relationships between them.

How to useChoose a scope, search with /, and select a node for its definition, stable IRI, source, and connections. Focus its neighbourhood when the whole graph is too dense. Public and private annotations remain separate from authoritative SSTIM terms.

Explore the graph
Patch Studio Real-time authoring

Build and preview layered audio-visual patches, including first-class stereoscopic scenes, modulation, a resizable Mix view, and photosensitivity safeguards.

How to useStart empty or use a Field starter, then add ordinary audio and visual tracks. Preview, save, import, and export the patch from one workspace. Haptic tracks are authoring metadata for now; this browser build does not provide a haptic delivery engine.

Open Patch Studio
Presets Reference catalog

A public reference catalog read from SSTIM RDF, with frequency targets, groups, provenance, and evidence assessments kept visible rather than flattened into a score.

How to useSearch and filter the catalog, inspect how each record is described, then follow its source and evidence links. These are SSTIM Workbench reference records published under preserved BSC Lab identifiersβ€”not the private BioSynCare catalog and not treatment recommendations.

Browse public presets
SPARQL Query workbench

A SPARQL 1.1 workbench that runs entirely in your browser (Comunica over an N3 store), querying the ontology and the public instance data together.

How to useBegin with a documented example or write your own query. The workbench explains which named graphs are loaded, shows execution status and result counts, and lets you copy tabular results without sending the query to a remote endpoint.

Open the workbench
Logbook Personal record

A private, long-term record of your sensory-stimulation work β€” sessions, observations, ideas, activities, initiatives, notes, and achievements, across multiple named logbooks.

How to useAdd entries, tag them, and filter by tag. Entries are stored locally in your browser. When sign-in is configured, the current account selects a separate local scope; that does not by itself sync logbooks to a server. Your data is never committed to the repository.

Open your logbook
Settings Appearance, engine, safety

Where you choose the visual skin, the audio engine, and the photosensitivity safety behaviour.

How to usePreview a skin, choose the Patch Studio audio engine, and review visual-safety and storage behaviour. Capability checks explain unavailable choices and safe fallbacks.

Review settings

Two more reference surfaces open from the + menu in the top bar: your optional account Profile (private, sign-in based), and the generated Ontology docs and Vocabulary docs.

SSTIM and its data boundaries

SSTIM's current formalized knowledge is published as a modular ontology suite rather than one opaque data file. Its manifest defines dependency closures and adoption profiles; SHACL, OWL reasoning, link checks, snapshots, and release rehearsal are automated repository gates.

  • Foundations β€” stimulation, stimulus specifications, shared quantities, techniques, and configurations.
  • Sessions & exposure β€” plans, executions, overrides, delivery, perception, devices, placement, and limits.
  • Evidence β€” immutable assessment claims with an explicit proposition, qualified basis, direction, tier, agent, and date.
  • Controlled vocabulary β€” multilingual SKOS values for bands, modalities, mechanisms, techniques, evidence, and cautions.
  • Application mappings & stakeholder relationships β€” Patch Studio mappings plus neutral, consent-aware records about people and organizations.
  • Validation & alignment β€” reusable SHACL contracts and conservative external links.

Controlled values are dual-typed as OWL individuals and SKOS concepts. Stable namespace documents live under https://w3id.org/sstim. Automated conformance is useful evidence about the files; it is not a substitute for independent scientific or human review.

Community coordination happens in the Sensory Stimulation Vocabulary Community Group at the W3C β€” an open group, proposed and chaired by Renato Fabbri, for aligning sensory-stimulation vocabulary and interoperability work across projects. Anyone can join and participate.

Read every source in context

The Graph's Data sources panel lists what is loaded and where it comes from. The four words mean different things:

Versioned

Ontology & vocabulary

OWL terms, axioms, and multilingual SKOS values. Cite an immutable release; the running site can contain later development work.

Versioned

Public catalog

Reference frameworks, implementations, presets, and evidence records. Pin a release for reuse; public data is not a clinical recommendation.

Live & retractable

Live stakeholders

Reviewed relationships among people and organizations, fetched at runtime and deliberately excluded from citable archives. This is one data layer, not the complete SSTIM ecosystem.

Personal

Notes & logbooks

Local to this browser by default. Sign-in separates local logbook scopes; shared annotations and account-backed patch storage are separate deployment choices.

Outside this repository: real participant session data, clinical material, and the private BioSynCare catalog. Annotations use separate named graphs; private notes and logbooks remain owned by their author.