HighlightNeo4j

Neo4j constraints enforce uniqueness, existence, type, and keys

Neo4j Cypher manual listing property uniqueness, existence, type, and key constraints, and preferring graph types for schema.

Neo4j provides property uniqueness, existence (Enterprise), type (Enterprise), and key (Enterprise) constraints on nodes by label or relationships by type. Older CREATE CONSTRAINT syntax still adds constraints to a database’s graph type, but the docs recommend defining schema via graph types for richer constraint kinds and simpler long-term maintenance.

Based on: Constraints - Cypher Manual · Neo4j

HighlightNeo4j

Neo4j MERGE: match-or-create patterns with ON MATCH/ON CREATE

Neo4j Cypher manual for MERGE, which binds existing patterns or creates missing ones, with constraint guidance.

MERGE combines MATCH and CREATE: if the exact pattern exists it binds like MATCH; otherwise it creates like CREATE. ON MATCH and ON CREATE allow different actions for each case. The manual recommends creating constraints before merging for index-backed performance and to prevent unintended divergent data.

Based on: MERGE - Cypher Manual · Neo4j

HighlightGoogle Search Central

Google Search uses on-page structured data as explicit meaning for rich results

Google Search Central intro: structured data markup gives Search explicit page meaning, enables rich results, and cites publisher case studies.

Google Search can use structured data on a page as explicit clues about content—for example recipe ingredients, time, and calories. That markup can enable rich results. Google also uses it to understand page content and gather facts about entities such as people, books, and companies. Case studies cite CTR and engagement lifts for several publishers.

Based on: Intro to How Structured Data Markup Works | Google Search Central | Documentation | Google for Developers · Google Search Central

HighlightAirbyte

Airbyte Protocol standardizes source and destination actors for ELT pipelines

Airbyte docs defining the protocol: actors, catalog/stream/field primitives, and STDIO JSON vs Socket Protobuf data channels.

The Airbyte Protocol specifies standard components and interactions that declare an ELT pipeline. Sources and destinations are actors with standard interfaces; data is described via catalog, configured catalog, stream, configured stream, and field. Two channel modes exist: STDIO with serialized JSON messages, and Socket mode with Protocol Buffers over Unix domain sockets.

Based on: Airbyte Protocol | Airbyte Docs · Airbyte

HighlightW3C Shape Expressions Community Group / shex.io

ShEx 2.1 defines shapes and node constraints for describing RDF graph structure

Final Community Group Report (8 Oct 2019) for Shape Expressions Language 2.1: RDF node and graph structure descriptions for validation and interfaces.

Shape Expressions (ShEx) describe RDF nodes and graph structures: node constraints on IRIs, blank nodes, or literals, and shapes over triples with predicates, cardinalities, and datatypes. Shapes can communicate structures for processes or interfaces, generate or validate data, or drive user interfaces. ShEx 2.1 adds IMPORTS and language tag value sets.

Based on: Shape Expressions Language 2.1 · W3C Shape Expressions Community Group / shex.io

HighlightLinkML / Berkeley Bioinformatics Open Source Projects

LinkML authors YAML schemas that compile and validate across JSON, RDF, and TSV

LinkML documentation: a Linked Data Modeling Language for YAML schemas, multi-format validation, and generators into other frameworks.

LinkML is a flexible modeling language for authoring YAML schemas that describe data structure. It is also a framework for working with and validating data in formats such as JSON, RDF, and TSV, with generators that compile schemas to other frameworks. It is Apache-2.0 licensed and community-driven.

Based on: linkml documentation · LinkML / Berkeley Bioinformatics Open Source Projects

HighlightOracle MySQL

MySQL CHECK constraints encode boolean row rules with optional enforcement

MySQL 8.4 reference for CREATE TABLE CHECK constraints: naming, boolean expr, ENFORCED/NOT ENFORCED, table vs column form.

MySQL 8.4 permits core table and column CHECK constraints for all storage engines. A CHECK (expr) must evaluate to TRUE or UNKNOWN per row; FALSE is a violation. Constraints may be ENFORCED or NOT ENFORCED, named with an optional symbol, and declared as table- or column-level.

Based on: MySQL :: MySQL 8.4 Reference Manual :: 15.1.20.6 CHECK Constraints · Oracle MySQL

HighlightApache Software Foundation

Apache Jena’s jena-shacl runs W3C SHACL Core and SPARQL constraints in practice

Jena documentation for jena-shacl: SHACL Core and SPARQL constraints, compact syntax, CLI validate/parse, and Fuseki endpoint integration.

jena-shacl implements W3C SHACL Core and SHACL SPARQL Constraints, plus compact syntax and SPARQL-based targets. The shacl CLI validates and parses shapes; Fuseki can expose a fuseki:shacl operation that accepts a posted shapes graph and optional graph/target parameters.

Based on: Apache Jena - Apache Jena SHACL · Apache Software Foundation

HighlightMorgan & Claypool (open online edition)

A 2018 handbook on RDF validation covering ShEx, SHACL, and data quality

Open HTML edition of Validating RDF Data (Morgan & Claypool, 2018) by Labra Gayo, Prud’hommeaux, Boneva, and Kontokostas.

Validating RDF Data is a Synthesis Lectures book on Semantic Web theory and technology. The contents move from RDF and data quality through Shape Expressions and SHACL, including shapes, constraints, and related tooling. A free HTML edition is maintained with errata and example source.

Based on: Validating RDF Data · Morgan & Claypool (open online edition)

HighlightSchema.org

Schema.org’s model: multi-inheritance types, multi-domain properties, not a world ontology

Schema.org documentation of its RDF Schema–derived data model: types, properties with multiple domains and ranges, and limits on scope.

Schema.org’s data model is generic and derived from RDF Schema. Types form a multiple-inheritance hierarchy; properties may have multiple domains and ranges for pragmatic reasons. The project is not intended as a universal ontology and expects use alongside other vocabularies that share the same basic model and standards such as JSON-LD, Microdata, and RDFa.

Based on: Data model - Schema.org · Schema.org

HighlightJSON-LD CG / Digital Bazaar community site

JSON-LD turns ordinary JSON into Linked Data that can cross site boundaries

Project site for JSON-LD: a JSON-based Linked Data format, W3C specs, playground, and conforming libraries across many languages.

JSON-LD is a lightweight Linked Data format based on JSON, meant to be readable by humans and usable in programming environments, REST services, and document databases. Linked Data here means standards-based, machine-readable data that can follow links across sites. The site points to W3C recommendations, a playground, and conforming implementations.

Based on: JSON-LD - JSON for Linked Data · JSON-LD CG / Digital Bazaar community site

HighlightPostgreSQL Global Development Group

PostgreSQL COMMENT attaches one replaceable note to almost any database object

Official PostgreSQL docs for the COMMENT command: store, replace, or clear a single comment string on tables, columns, functions, and many other objects.

COMMENT ON stores one comment string per database object and replaces any existing comment when reissued. Specifying NULL or an empty string removes the comment. The synopsis lists object kinds from tables and columns through functions, operators, schemas, and more.

Based on: COMMENT · PostgreSQL Global Development Group