sstim

Validate sensory-stimulation descriptions against a published SSTIM profile.

SSTIM is an open standard for describing what a stimulus actually is: signals, channels, renderings, techniques, protocols, sessions, exposure and evidence. This package is a client for it. The ontology, its SHACL shapes and its profiles are published independently, and this code only reads them.

pip install sstim
sstim validate my-stimulus.ttl --profile core

my-stimulus.ttl
  profile core at https://w3id.org/sstim/0.17.0
  ok     SHACL conformance
  ok     every SSTIM term is defined in the core closure
  ok     nothing minted under https://w3id.org/sstim

Three checks, not one

SHACL conformance on its own does not tell you your file is right, for a reason that catches everyone once: SHACL is silent about a term it has never heard of. Misspell a property, or reach for one from a module your profile does not contain, and the shapes have nothing to say. Your file validates. A consumer loading that profile then meets a predicate it cannot interpret, and your mistake surfaces in their pipeline instead of yours.

So this runs three checks:

1. Conformance against the shapes of the profile you named, not against the largest one available.
2. Containment: every SSTIM term you used is defined inside that profile's closure.
3. Namespace discipline: you have not minted anything under https://w3id.org/sstim. Reuse their terms; mint your records in your own namespace. It is the first rule an adopter can break and the most expensive to undo.

Profiles

Take the smallest one that carries what you actually assert. Moving up later is additive, so starting small costs nothing.

sstim profiles                      # what a release offers
sstim modules --profile full        # what that profile pulls in, and from where

Versions are resolved, not guessed

With no --version, the newest frozen release is resolved by reading owl:versionIRI from the stable IRI. This matters more than it looks: the manifest served at https://w3id.org/sstim/manifest is the development line, so code that fetches it and believes it pinned something has pinned nothing.

sstim validate my.ttl --profile core --version 0.17.0   # pin explicitly

Every module listed in a manifest carries a sha256, and the bytes served are checked against it before anything is parsed. A truncated download or a substituted file stops the run rather than quietly validating your data against a graph that is not SSTIM. Verified modules are cached by checksum, so repeated runs are offline and a cache entry can never be stale.

sstim validate my.ttl --offline     # fail rather than fetch
sstim cache                         # where the cache lives

As a library

import sstim

report = sstim.validate("my-stimulus.ttl", profile="core")
if not report:
    print(report)

# Resolve once, validate many
closure = sstim.resolve_profile("full", version="0.17.0")
closure.version_iri          # 'https://w3id.org/sstim/0.17.0'
[m.id for m in closure.semantic_modules]
reports = [sstim.validate(p, closure=closure) for p in paths]

manifest= resolves from a local checkout or a frozen release directory instead, which needs no network at all.

What this does not do

It does not tell you a stimulation is safe, effective, or ethically approved. Conformance means a file is well formed against the model. Those are different reviews, and SSTIM does not perform them.

More

• Adopting SSTIM, the half-hour on-ramp
• Starter examples
• The ontology and its term index

Apache-2.0. SSTIM itself is CC BY 4.0.