Docs/Reference/Modules/rules_schema_org

rules_schema_org

Sha-pinned schema.org vocabulary + grounding tables via rules_rdf / rules_jena

Latest	`0.0.3`
Versions	2
Category	Bazel rules
Maintainers	Matt Marshall
Registry	https://registry.tbzl.dev/modules/rules_schema_org/
Source	github.com/tomato-bazel/rules_schema_org

MODULE.bazelstarlark

bazel_dep(name = "rules_schema_org", version = "0.0.3")

View source & releases on GitHub ↗

The grounding ontology for typed tool-capability matching. Pins schema.org (and, incrementally, SKOS / DC / the module closure) as sha-verified RDF, RDFS-materializes its class/property hierarchy, and emits the grounding tuples that an NL→BGP capability parser is trained to target.

Built on the cluster’s RDF rules:

rules_rdf   — rdf.resource (pin) · rdf_dataset (closure) ·
              rdf_namespace_aspect (harvest/validate) · rdf_reason ·
              sparql_query (producer)
rules_jena  — Apache Jena backends for the four rdf toolchain types

Pipeline

rdf.resource  →  rdf_dataset(deps=…)  →  rdf_reason(rdfs, include_base)  →  sparql_query
  (pin TTL)        (linked closure)        (materialize subClassOf)          (grounding tuples)

Targets

target	what
`@schemaorg_ttl//:dataset`	the pinned schema.org vocabulary
`//schemaorg:schemaorg`	composing `rdf_dataset` (add SKOS/DC via `deps`)
`//schemaorg:schemaorg_manifest`	harvested namespace set + import audit
`//schemaorg:schemaorg_rdfs`	RDFS-materialized closure
`//schemaorg:grounding_classes`	class→superclass tuples (TSV)

Requirements

Apache Jena needs a Java 17+ runtime; .bazelrc pins --java_runtime_version=remotejdk_17.

Replaces

The ad-hoc savvi-studio/tools/schemaorg index generator — superseded by a hermetic, sha-pinned, reasoned, queryable grounding ontology.

Conformance#

3 findings across 1 invariant. 8 contested atoms. See how gating works or the full report.

D3 a repo name CHOSEN on a SHARED extension must be namespaced why this matters ↗

repo	extension
`dcterms_ttl`	`@rules_rdf//rdf:extensions.bzl`
`schemaorg_ttl`	`@rules_rdf//rdf:extensions.bzl`
`skos_rdf`	`@rules_rdf//rdf:extensions.bzl`

Contested atoms

Third-party modules where this module resolves a different version than others do. Not a violation of anything this module did — it is the actionable form of a registry-level convergence finding, and the sentence a maintainer can act on.

Atom	Resolved here	Elsewhere
`apple_support`	`1.24.2`	`2.2.0` ×1
`bazel_skylib`	`1.8.2`	`1.9.0` ×2
`nlohmann_json`	`3.6.1`	`3.12.0.bcr.1` ×1
`protobuf`	`33.4`	`34.0.bcr.1` ×2
`rules_jvm_external`	`6.7`	`6.8` ×4
`rules_python`	`1.7.0`	`2.0.1` ×1
`rules_swift`	`3.1.2`	`3.6.1` ×1
`upb`	`0.0.0-20220923-a547704`	`0.0.0-20230516-61a97ef` ×1

Dependencies#

rules_schema_org in the registry graph — what it depends on (left) and what depends on it (right).

Depends on

platforms1.0.0bazel_skylib1.8.2rules_rdf0.4.0 rules_jena0.3.2rules_python1.7.0stardoc0.7.2dev

Versions#

2 published versions, newest first. Each resolves to an immutable, integrity-checked archive.

Version	Integrity (sha256)	Source archive
`0.0.3` latest	`xDHCuQi81EEp6ZEH…`	tag archive ↗
`0.0.1`	`AZ/brGExGKo80xJS…`	tag archive ↗

Changelog#

All notable changes to rules_schema_org. The format is loosely Keep a Changelog — version headers mirror the published bazel-registry entries.

0.0.1 — schema.org grounding ontology

Pins the schema.org current vocabulary by sha256 via rules_rdf’s rdf.resource (@schemaorg_ttl).
//schemaorg:schemaorg — the composing rdf_dataset (SKOS / DC / module pins fold in via deps).
//schemaorg:schemaorg_manifest — harvested namespace set (the grounding vocabulary) + owl:imports completeness audit.
//schemaorg:schemaorg_rdfs — RDFS-materialized subclass/subproperty closure (Apache Jena via rules_jena).
//schemaorg:grounding_classes — the class→superclass grounding tuples (5,201 rows) emitted as a build artifact; the type hierarchy the NL→BGP parser’s SFT is generated from.
Requires a Java 17 runtime for the Jena backends (pinned in .bazelrc).

← All modules