Native
Part of the current operating model or an implemented interface.
Interoperability by design
Global infrastructure cannot depend on one vendor's private language.
A plural data economy needs shared ways to identify, describe, query, govern, discover, contract, and use knowledge. Legra builds on open graph standards and contributes a broader operational route around sovereign Data Products and executable Use Cases.
Standards are connective tissue, not a badge collection.
The point is not to list acronyms. It is to let independently built data, models, policies, services, and business capabilities meet at explicit boundaries without forcing every participant onto one proprietary marketplace or application stack.
Read every claim precisely
Alignment, implementation, and inspiration are different things.
Partial
The semantic substrate fits, while a complete publishing or operational surface is still developing.
Emerging / planned
Standards work or a Legra capability is not yet a completed production surface.
Inspired
An architectural influence—not a compatibility or conformance claim.
Native graph foundation
Standards live in the operating model—not only at import and export.
RDF and Linked Data
IRIs, literals, named graphs, shared vocabularies, RDF-style quads, and standards-based serializations form the semantic core.
Read the Linked Data assessmentSPARQL
Standards-based graph query and update operate alongside Cypher and ISO GQL over the same graph infrastructure.
Explore query languagesRDFS, OWL-RL, and validation
Semantic inference, rules, shapes, and validation make shared meaning executable instead of leaving vocabularies as documentation.
Explore reasoningPROV-O and graph provenance
Agents, delegation, derivation, tasks, events, and version history can remain queryable as connected provenance.
Inspect the standards fitSupply, demand, and policy
The data economy needs standards on both sides of the transaction.
Partial
DCAT
A W3C vocabulary for catalogs, datasets, distributions, and data services. Legra has a native RDF fit and DCAT-oriented groundwork; fuller publishing and federated catalog workflows are developing.
Emerging standard
DPROD
The Data Product Ontology describes governed products, ports, dependencies, and lifecycle. Legra's workspace architecture aligns with its decentralized intent; complete publication, offer, contract, and settlement support is not one finished feature.
Method lineage
EKG Method
The Use Case Tree Method represents demand as outcomes, personas, concepts, Stories, dependencies, and composable capability rather than leaving it in project documents.
Planned
ODRL
The W3C policy model is the direction for fine-grained permissions, duties, prohibitions, constraints, and DPROD contract policy inside workspace authority boundaries.
Architectural influences
Solid and Linked Web Storage
Legra shares the goal of application-independent data control and extends the pod idea with versioned graph work, arbitrary files, execution, evidence, and economic exchange. Alignment is a direction, not a claim of complete Solid protocol compatibility.
Compare Linked Data and pod serversIPFS-inspired content logistics
Content addressing, encrypted blocks, distributed custody, and peer-to-peer delivery draw on similar ideas. Legra adds workspace authority, graph semantics, governed change, task evidence, contracts, and economic management around them.
Compare peer-to-peer data systemsStandards lineage and source material
Built from participation in the standards work.
Legra's direction grows from work initiated through the Enterprise Knowledge Graph community, the DPROD workgroup, and the EKG Method. It goes beyond vocabulary publication toward the operational infrastructure for discovery, agreement, delivery, execution, evidence, and value exchange.