Published

Data Pipeline

vr.wm-dat-005 · wm-dat-005-data-pipeline

Represent one governed reusable data pipeline definition whose topology, interfaces, logic references, policies and controls can be understood and projected without absorbing runtime, dataset or lineage-event masters.

World Models Information and virtual systems INF.DAT.PIP

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Pipeline identity, scope, ownership and definition Groups governed pipeline context for pipeline identity, scope, ownership and definition.

Pipeline root, version, state and namespace

Groups governed pipeline context for pipeline root, version, state and namespace.

Pipeline identity, type, version, current head and revision

Records pipeline identity, type, version, current head and revision as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish pipeline identity, type, version, current head and revision? identity
Who declared, owns, approves, operates, observes or may rely on pipeline identity, type, version, current head and revision, under which authority and limits? event
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify pipeline identity, type, version, current head and revision? process

Namespace, domain, data product, purpose, criticality and classification

Records namespace, domain, data product, purpose, criticality and classification as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish namespace, domain, data product, purpose, criticality and classification? classification
Who declared, owns, approves, operates, observes or may rely on namespace, domain, data product, purpose, criticality and classification, under which authority and limits? temporal
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify namespace, domain, data product, purpose, criticality and classification? validation

Ownership, stakeholders and definition boundaries

Groups governed pipeline context for ownership, stakeholders and definition boundaries.

Owner, steward, author, operator, approver, consumer and contact

Records owner, steward, author, operator, approver, consumer and contact as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish owner, steward, author, operator, approver, consumer and contact? ownership
Who declared, owns, approves, operates, observes or may rely on owner, steward, author, operator, approver, consumer and contact, under which authority and limits? composition
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify owner, steward, author, operator, approver, consumer and contact? privacy

Workflow, release, deployment, scheduler, run and task boundary

Records workflow, release, deployment, scheduler, run and task boundary as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish workflow, release, deployment, scheduler, run and task boundary? relationship
Who declared, owns, approves, operates, observes or may rely on workflow, release, deployment, scheduler, run and task boundary, under which authority and limits? evidence
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify workflow, release, deployment, scheduler, run and task boundary? lifecycle

Topology, components, ports and data contracts Groups governed pipeline context for topology, components, ports and data contracts.

Nodes, edges, dependencies and control flow

Groups governed pipeline context for nodes, edges, dependencies and control flow.

Source, transform, sink, gateway, subpipeline and component node

Records source, transform, sink, gateway, subpipeline and component node as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish source, transform, sink, gateway, subpipeline and component node? composition
Who declared, owns, approves, operates, observes or may rely on source, transform, sink, gateway, subpipeline and component node, under which authority and limits? ownership
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify source, transform, sink, gateway, subpipeline and component node? quality

Data, control, dependency, condition, order, cycle, fan-in and fan-out edge

Records data, control, dependency, condition, order, cycle, fan-in and fan-out edge as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish data, control, dependency, condition, order, cycle, fan-in and fan-out edge? relationship
Who declared, owns, approves, operates, observes or may rely on data, control, dependency, condition, order, cycle, fan-in and fan-out edge, under which authority and limits? measurement
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify data, control, dependency, condition, order, cycle, fan-in and fan-out edge? security

Ports, datasets, streams, schemas and contracts

Groups governed pipeline context for ports, datasets, streams, schemas and contracts.

Input or output port, dataset, stream, table, topic, object and format

Records input or output port, dataset, stream, table, topic, object and format as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish input or output port, dataset, stream, table, topic, object and format? interoperability
Who declared, owns, approves, operates, observes or may rely on input or output port, dataset, stream, table, topic, object and format, under which authority and limits? exception
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify input or output port, dataset, stream, table, topic, object and format? retention

Data contract, key, type, nullability, partition, order, compatibility and SLA

Records data contract, key, type, nullability, partition, order, compatibility and sla as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish data contract, key, type, nullability, partition, order, compatibility and sla? constraint
Who declared, owns, approves, operates, observes or may rely on data contract, key, type, nullability, partition, order, compatibility and sla, under which authority and limits? provenance
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify data contract, key, type, nullability, partition, order, compatibility and sla? interoperability

Logic, configuration, schedule and execution policy Groups governed pipeline context for logic, configuration, schedule and execution policy.

Logic artifacts, parameters and runtime references

Groups governed pipeline context for logic artifacts, parameters and runtime references.

Code, query, notebook, container, function, artifact, version and digest

Records code, query, notebook, container, function, artifact, version and digest as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish code, query, notebook, container, function, artifact, version and digest? provenance
Who declared, owns, approves, operates, observes or may rely on code, query, notebook, container, function, artifact, version and digest, under which authority and limits? process
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify code, query, notebook, container, function, artifact, version and digest? decision

Parameter, configuration, dependency, environment, secret and credential reference

Records parameter, configuration, dependency, environment, secret and credential reference as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish parameter, configuration, dependency, environment, secret and credential reference? security
Who declared, owns, approves, operates, observes or may rely on parameter, configuration, dependency, environment, secret and credential reference, under which authority and limits? validation
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify parameter, configuration, dependency, environment, secret and credential reference? state

Triggers, schedules and execution semantics

Groups governed pipeline context for triggers, schedules and execution semantics.

Manual, time, event or dependency trigger, schedule, timezone and data interval

Records manual, time, event or dependency trigger, schedule, timezone and data interval as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish manual, time, event or dependency trigger, schedule, timezone and data interval? temporal
Who declared, owns, approves, operates, observes or may rely on manual, time, event or dependency trigger, schedule, timezone and data interval, under which authority and limits? privacy
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify manual, time, event or dependency trigger, schedule, timezone and data interval? identity

Retry, timeout, concurrency, idempotency, checkpoint, backfill, replay and catchup

Records retry, timeout, concurrency, idempotency, checkpoint, backfill, replay and catchup as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish retry, timeout, concurrency, idempotency, checkpoint, backfill, replay and catchup? process
Who declared, owns, approves, operates, observes or may rely on retry, timeout, concurrency, idempotency, checkpoint, backfill, replay and catchup, under which authority and limits? lifecycle
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify retry, timeout, concurrency, idempotency, checkpoint, backfill, replay and catchup? classification

Lineage, quality, observability and data products Groups governed pipeline context for lineage, quality, observability and data products.

Intended lineage, provenance and runtime observation

Groups governed pipeline context for intended lineage, provenance and runtime observation.

Expected input, output, field mapping, transform semantics and derivation

Records expected input, output, field mapping, transform semantics and derivation as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish expected input, output, field mapping, transform semantics and derivation? provenance
Who declared, owns, approves, operates, observes or may rely on expected input, output, field mapping, transform semantics and derivation, under which authority and limits? quality
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify expected input, output, field mapping, transform semantics and derivation? relationship

Runtime lineage event, source, version, confidence, gap and current view

Records runtime lineage event, source, version, confidence, gap and current view as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish runtime lineage event, source, version, confidence, gap and current view? evidence
Who declared, owns, approves, operates, observes or may rely on runtime lineage event, source, version, confidence, gap and current view, under which authority and limits? security
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify runtime lineage event, source, version, confidence, gap and current view? authority

Quality rules, SLOs, telemetry and cost

Groups governed pipeline context for quality rules, slos, telemetry and cost.

Validation rule, dimension, threshold, quarantine, acceptance and exception

Records validation rule, dimension, threshold, quarantine, acceptance and exception as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish validation rule, dimension, threshold, quarantine, acceptance and exception? quality
Who declared, owns, approves, operates, observes or may rely on validation rule, dimension, threshold, quarantine, acceptance and exception, under which authority and limits? retention
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify validation rule, dimension, threshold, quarantine, acceptance and exception? requirement

Log, metric, trace, freshness, latency, volume, error, cost and SLO

Records log, metric, trace, freshness, latency, volume, error, cost and slo as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish log, metric, trace, freshness, latency, volume, error, cost and slo? measurement
Who declared, owns, approves, operates, observes or may rely on log, metric, trace, freshness, latency, volume, error, cost and slo, under which authority and limits? interoperability
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify log, metric, trace, freshness, latency, volume, error, cost and slo? constraint

Security, privacy, resilience and compliance Groups governed pipeline context for security, privacy, resilience and compliance.

Identity, access, secrets, zones and protection

Groups governed pipeline context for identity, access, secrets, zones and protection.

Service identity, permission, data zone, encryption, network and least privilege

Records service identity, permission, data zone, encryption, network and least privilege as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish service identity, permission, data zone, encryption, network and least privilege? security
Who declared, owns, approves, operates, observes or may rely on service identity, permission, data zone, encryption, network and least privilege, under which authority and limits? decision
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify service identity, permission, data zone, encryption, network and least privilege? event

Secret, credential, key reference, rotation, separation and exception

Records secret, credential, key reference, rotation, separation and exception as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish secret, credential, key reference, rotation, separation and exception? security
Who declared, owns, approves, operates, observes or may rely on secret, credential, key reference, rotation, separation and exception, under which authority and limits? state
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify secret, credential, key reference, rotation, separation and exception? temporal

Failure, recovery, rights, retention and obligations

Groups governed pipeline context for failure, recovery, rights, retention and obligations.

Failure mode, detection, rollback, recovery, continuity, disaster and residual risk

Records failure mode, detection, rollback, recovery, continuity, disaster and residual risk as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish failure mode, detection, rollback, recovery, continuity, disaster and residual risk? requirement
Who declared, owns, approves, operates, observes or may rely on failure mode, detection, rollback, recovery, continuity, disaster and residual risk, under which authority and limits? identity
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify failure mode, detection, rollback, recovery, continuity, disaster and residual risk? composition

Purpose, rights, minimization, residency, retention, deletion, consent and legal hold

Records purpose, rights, minimization, residency, retention, deletion, consent and legal hold as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish purpose, rights, minimization, residency, retention, deletion, consent and legal hold? privacy
Who declared, owns, approves, operates, observes or may rely on purpose, rights, minimization, residency, retention, deletion, consent and legal hold, under which authority and limits? classification
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify purpose, rights, minimization, residency, retention, deletion, consent and legal hold? evidence

Lifecycle, governance, runs and projections Groups governed pipeline context for lifecycle, governance, runs and projections.

Release, change, deployment and run linkages

Groups governed pipeline context for release, change, deployment and run linkages.

Draft, reviewed, approved, published, deployed, active, paused, deprecated and retired

Records draft, reviewed, approved, published, deployed, active, paused, deprecated and retired as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish draft, reviewed, approved, published, deployed, active, paused, deprecated and retired? lifecycle
Who declared, owns, approves, operates, observes or may rely on draft, reviewed, approved, published, deployed, active, paused, deprecated and retired, under which authority and limits? relationship
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify draft, reviewed, approved, published, deployed, active, paused, deprecated and retired? ownership

Change impact, compatibility, migration, rollback, deployment, run, incident and remediation

Records change impact, compatibility, migration, rollback, deployment, run, incident and remediation as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish change impact, compatibility, migration, rollback, deployment, run, incident and remediation? lifecycle
Who declared, owns, approves, operates, observes or may rely on change impact, compatibility, migration, rollback, deployment, run, incident and remediation, under which authority and limits? authority
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify change impact, compatibility, migration, rollback, deployment, run, incident and remediation? measurement

Catalog, projection, audit and records

Groups governed pipeline context for catalog, projection, audit and records.

Catalog, dataset, data product, owner, status and discoverability

Records catalog, dataset, data product, owner, status and discoverability as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish catalog, dataset, data product, owner, status and discoverability? classification
Who declared, owns, approves, operates, observes or may rely on catalog, dataset, data product, owner, status and discoverability, under which authority and limits? requirement
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify catalog, dataset, data product, owner, status and discoverability? exception

BPMN, CWL, Airflow, OpenLineage, PROV, DCAT, DQV, SHACL, CloudEvents and OTel projection

Records bpmn, cwl, airflow, openlineage, prov, dcat, dqv, shacl, cloudevents and otel projection as governed pipeline-definition context while deployment, scheduler, run, dataset, lineage-event, secret, telemetry and records masters remain external.

What stable identity, pipeline version, typed value and explicit unknown establish bpmn, cwl, airflow, openlineage, prov, dcat, dqv, shacl, cloudevents and otel projection? interoperability
Who declared, owns, approves, operates, observes or may rely on bpmn, cwl, airflow, openlineage, prov, dcat, dqv, shacl, cloudevents and otel projection, under which authority and limits? constraint
Which effective, release, deployment, scheduled, event, recorded, ingested and knowledge times, evidence and uncertainty qualify bpmn, cwl, airflow, openlineage, prov, dcat, dqv, shacl, cloudevents and otel projection? provenance

Classifiers Filled

Family: World Models
Category: Information and virtual systems
Entry kind: aggregate
Navigation path: NAV.INF.DAT.PIP
Domain: INF.DAT.PIP
Industry: Cross-industry
Tags: datapipelineinf.dat.pip

What it is Filled

Owns pipeline identity, version and lifecycle; purpose, domain and ownership; component graph, ports and dependency semantics; dataset and data-contract bindings; logic, artifact, configuration, environment and secret references; trigger, schedule and execution policies; intended lineage, validation, quality, observability, security, privacy, resilience and interoperability projections. Workflow, run, task attempt, dataset, data product, lineage event, deployment, scheduler, software, secret, telemetry, incident, evidence, audit and records masters remain external.

In scope

Pipeline identity, version, ownership, purpose, topology, components, ports, edges, dependencies, contracts, logic references, parameters, configuration and execution policies
Intended lineage, quality, observability, security, privacy, resilience, lifecycle, releases, runtime bindings, run references, catalog views, audit and projections

Out of scope

Owning workflow, run, task attempt, dataset, data product, lineage event, deployment, scheduler, software, credential, telemetry, incident, evidence, audit or records masters
Treating intended topology, a completed run or an emitted lineage event as proof of quality, freshness, publication, consumption, compliance or exactly-once behavior
Autonomous deployment, execution, scheduling, backfill, replay, credential rotation, access widening, data publication, output deletion, incident closure or records disposition

Why it exists Filled

Distinguishing features Filled

A reusable versioned definition of data processing steps, not an individual execution.
Declares ports, data contracts and intended lineage before any run happens.
Differs from a general business process or workflow by binding datasets and data contracts.
Static lineage in the definition is intent, while runtime lineage comes from runs.

What robots and AI may and may not do Filled

Must not

Deploy, schedule, execute, backfill or replay the pipeline without delegation.
Rotate credentials or widen data access.
Change a released version in place.
Publish or delete outputs.
Claim exactly-once or deterministic behaviour without scoped evidence.

Only with a human decision

Releasing or retiring a pipeline version.
Approving schedule or trigger changes for production.
Approving new access to personal or restricted data.

May

Register a pipeline definition with topology and version.
Validate the graph, contracts and controls before release.
Describe the pipeline and its dependencies for impact analysis.
Propose changes as new versions for review.

Moral aspects Filled

Pipelines move personal data between systems, so purpose and access controls must travel with the definition.
Hidden transformations can introduce bias or errors into decisions about people.
Wasteful schedules consume compute and energy without value.

Who is affected

Data subjects
Downstream consumers of outputs
Data platform operators

Owners Filled

Steward

Dimension owner, namespace authority, data governance mandate and accountable data product owner

Roles

Data product owner: Own purpose, outcome, criticality, consumers, acceptance and accountable use of the pipeline.
Data steward: Own dataset meaning, contracts, quality, lineage, classification, rights and retention profiles.
Pipeline author and data engineer: Maintain topology, transform logic references, parameters, dependencies, tests and versioned change evidence.
Platform operator and SRE: Maintain deployment, scheduler, runtime, observability, capacity, recovery and incident linkages outside the definition.
Security and privacy reviewer: Review identity, secrets, access, zones, encryption, purpose, minimization, residency and deletion controls.
Independent reviewer and release authority: Review topology, contracts, change impact, validation, exceptions, compatibility and release decisions within mandate.
Records and interoperability steward: Own audit, retention, disposition, source pins, mappings and declared projection loss.

Links to other meta-models Filled

references

WM-ACT-003 Process / Workflow - Represent the unfrozen parent boundary without inheritance, mutation, execution or cascade authority.
WM-ACT-053 Data Processing Job / Pipeline Run - Resolve time-bounded executions while preserving separate definition, deployment, run and task identities.
WM-DAT-006 Data Lineage - Resolve authoritative runtime provenance without absorbing the lineage master.
Dataset, Data Product, Data Contract, Deployment, Scheduler, Software, Secret, Telemetry, Incident, Evidence, Audit and Records models - Resolve authoritative semantics, state, artifacts, controls and evidence without changing their ownership.

aligned

BPMN 2.0.2, CWL 1.2.1, Airflow 3.3.0, OpenLineage 1.53.0, PROV-O, DCAT 3, DQV, SHACL, JSON Schema 2020-12, CloudEvents 1.0.2, OpenTelemetry 1.44.0, Kubernetes and OCI 1.1.1 - Project version-pinned workflow, runtime, lineage, catalog, quality, validation, event, telemetry and packaging views with declared loss.

neighbor

WM-ACT-003 Process / Workflow - The unified parent signal supplies a general workflow boundary but grants no inheritance or ownership. The data pipeline specializes data movement and transformation while preserving its own versioned definition.
WM-ACT-053 Data Processing Job / Pipeline Run - The run master owns a time-bounded execution, attempts, input and output instances, status and runtime events. The pipeline owns reusable intended structure and policy.
WM-DAT-006 Data Lineage - The lineage master owns cross-system provenance observations and their evidence. The pipeline stores expected derivations and non-owning lineage references.
Dataset, data product, contract, deployment, scheduler, software, secret and telemetry - These masters own data semantics, product accountability, interface commitments, runtime state, executable artifacts, credentials and observations. The pipeline binds version-qualified references only.
BPMN, CWL, Airflow, OpenLineage, PROV, DCAT, DQV, SHACL, JSON Schema, CloudEvents, OpenTelemetry, Kubernetes and OCI - These standards and platforms have distinct scopes. Every mapping is version-pinned, profile-qualified and loss-declaring, never presumed universal or lossless.

parent

WM-ACT-003

contains

WM-ACT-053

What else AI and robots need to interact with it Filled

Sources Filled

OpenLineage Object Model - OpenLineage
DAGs - Apache Software Foundation
Common Workflow Language Workflow Description - Common Workflow Language Project
Business Process Model and Notation - Object Management Group
PROV-O The PROV Ontology - World Wide Web Consortium
Data Catalog Vocabulary DCAT Version 3 - World Wide Web Consortium
Data on the Web Best Practices Data Quality Vocabulary - World Wide Web Consortium
Shapes Constraint Language SHACL - World Wide Web Consortium
JSON Schema Draft 2020-12 - JSON Schema Project
CloudEvents Specification - Cloud Native Computing Foundation
OpenTelemetry Semantic Conventions - OpenTelemetry
Jobs - Kubernetes
OCI Image Format Specification - Open Container Initiative
Secure Software Development Framework Version 1.1 - National Institute of Standards and Technology
Time Ontology in OWL - World Wide Web Consortium
Date and Time on the Internet Timestamps - Internet Engineering Task Force

Open questions

Approve or reject the WM-ACT-003, WM-ACT-053 and WM-DAT-006 relationships and register Dataset, Data Product, Data Contract, Deployment, Scheduler, Software, Secret, Telemetry, Incident, Evidence, Audit and Records edges.
Create orchestrator, runtime, data-platform, database, streaming, transaction, schema-evolution, quality, security, privacy and jurisdiction profiles.
Test idempotency, checkpoint, retry, replay, backfill, ordering and exactly-once claims against concrete engine and storage combinations.
Validate organization-specific access, credential, data-zone, residency, minimization, consent, retention, deletion, incident and recovery policies.
Conformance-test version-pinned BPMN, CWL, Airflow, OpenLineage, PROV, DCAT, DQV, SHACL, JSON Schema, CloudEvents, OpenTelemetry, Kubernetes and OCI mappings and obtain independent external review before canonical promotion.
Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
The unified parent WM-ACT-003 and candidate relations to WM-ACT-053 and WM-DAT-006 are not approved frozen composition edges.
Engine-specific task types, expression languages, scheduler semantics, exactly-once guarantees and database transaction behavior require separate profiles.
Jurisdiction, organization, data sensitivity, residency, privacy, retention and rights requirements require adopting-Dimension profiles.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-dat-005-data-pipeline/spec.yaml, ver-cy/world-models/card-supplements/wm-dat-005-data-pipeline.json