the NDN project's compact language for writing trust schemas - declarative rules relating data-name patterns to key-name patterns, compiled and enforced by verifiers.
A trust rule shipped as data - and V1's honestly-scoped single rule beside it.
Etymology and backstory
VerSec was an earlier NDN trust-schema language; Light VerSec (LVS) is its streamlined successor from Lixia Zhang's group at UCLA, designed so applications can ship schemas as data. The lineage matters to the paper: it shows a decade of running code behind the idea that name-based authorization can be declared rather than programmed.
Ecosystem
NDN tooling (python-ndn ships an LVS implementation); the conceptual cousin of policy languages like Rego and Cedar, but specialized to hierarchical names and signing.
In codexproof
cited as the generalization target. V1 hard-codes one nesting rule in Rust; the paper names LVS-style declarative rules as what a schema case would grow into (the "schema case" gloss Eric ordered is exactly about this). Interview-safe framing: implemented the fixed rule, named the general language, drew the line honestly.