Options
All
  • Public
  • Public/Protected
  • All
Menu

Shapes are used to define patterns of data, which can be used to match or validate state and operations.

Declaration of a shape does not provide any runtime function by itself, but they can be used by other extensions and app code.

While this class implements MeldConstraint, shape checking is semantically weaker than constraint checking, as a violation (non-conformance) does not produce an exception but instead resolves a validation result. However, the constraint apply will attempt a correction in response to a non-conformance.

see

ShapeConstrained for using Shapes for schema validation

see

https://www.w3.org/TR/shacl/#constraints-section

Hierarchy

Implements

Index

Methods

Abstract affected

  • Capture precisely the data being affected by the given update which correspond to this shape, either before or after the update is applied to the state.

    In respect of SHACL concepts, correspondence is based on targets and paths (if applicable), but not constraints; so that non-validating state (either before or after the update) is included.

    see

    https://www.w3.org/TR/shacl/#targets

    see

    https://www.w3.org/TR/shacl/#property-paths

    Parameters

    Returns Promise<GraphUpdate>

    filtered updates where the affected subject corresponds to this shape

Abstract apply

Abstract check

Static from

Legend

  • Constructor
  • Property
  • Method
  • Property
  • Method
  • Inherited property
  • Inherited method
  • Static property
  • Static method
  • Protected method

Generated using TypeDoc. Delivered by Vercel. @m-ld/m-ld - v0.10.0 Source code licensed MIT. Privacy policy