Published

Data Catalog Entry / Data Product

vr.wm-dat-008 · wm-dat-008-data-catalog-entry-data-product

Represent one governed catalog record and the distinct data-product offering it describes so agents can discover, evaluate and request consumption without confusing metadata publication with resource availability, authorization, delivery, fitness or use.

World Models Information and virtual systems INF.DAT.CAT

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

Catalog record and product identity, scope and value Groups governed catalog context for catalog record and product identity, scope and value.

Catalog record identity, version and status

Groups source-qualified catalog context for catalog record identity, version and status.

Catalog record ID, catalog, entry version, head and record status

Records catalog record id, catalog, entry version, head and record status as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish catalog record id, catalog, entry version, head and record status? identity
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on catalog record id, catalog, entry version, head and record status, for which purpose and under what authority? temporal
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify catalog record id, catalog, entry version, head and record status? privacy

Record creator, publisher, created, modified, language and contact

Records record creator, publisher, created, modified, language and contact as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish record creator, publisher, created, modified, language and contact? ownership
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on record creator, publisher, created, modified, language and contact, for which purpose and under what authority? composition
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify record creator, publisher, created, modified, language and contact? lifecycle

Data product identity, purpose and market scope

Groups source-qualified catalog context for data product identity, purpose and market scope.

Product ID, name, version, type, domain, themes, tags and aliases

Records product id, name, version, type, domain, themes, tags and aliases as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish product id, name, version, type, domain, themes, tags and aliases? classification
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on product id, name, version, type, domain, themes, tags and aliases, for which purpose and under what authority? evidence
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify product id, name, version, type, domain, themes, tags and aliases? quality

Purpose, value proposition, intended use, non-use, audience and outcome

Records purpose, value proposition, intended use, non-use, audience and outcome as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish purpose, value proposition, intended use, non-use, audience and outcome? requirement
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on purpose, value proposition, intended use, non-use, audience and outcome, for which purpose and under what authority? ownership
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify purpose, value proposition, intended use, non-use, audience and outcome? security

Ownership, stewardship, resources and composition Groups governed catalog context for ownership, stewardship, resources and composition.

Ownership, accountability and support

Groups source-qualified catalog context for ownership, accountability and support.

Owner, holder, publisher, steward, product manager and accountable authority

Records owner, holder, publisher, steward, product manager and accountable authority as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish owner, holder, publisher, steward, product manager and accountable authority? authority
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on owner, holder, publisher, steward, product manager and accountable authority, for which purpose and under what authority? measurement
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify owner, holder, publisher, steward, product manager and accountable authority? retention

Producer, custodian, contact, support, consumer and role delegation

Records producer, custodian, contact, support, consumer and role delegation as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish producer, custodian, contact, support, consumer and role delegation? ownership
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on producer, custodian, contact, support, consumer and role delegation, for which purpose and under what authority? exception
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify producer, custodian, contact, support, consumer and role delegation? interoperability

Dataset, service, distribution and related resource bindings

Groups source-qualified catalog context for dataset, service, distribution and related resource bindings.

Dataset, version, series, role and authoritative source binding

Records dataset, version, series, role and authoritative source binding as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish dataset, version, series, role and authoritative source binding? relationship
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on dataset, version, series, role and authoritative source binding, for which purpose and under what authority? provenance
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify dataset, version, series, role and authoritative source binding? decision

Service, distribution, schema, contract, lineage, quality and related resource binding

Records service, distribution, schema, contract, lineage, quality and related resource binding as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish service, distribution, schema, contract, lineage, quality and related resource binding? composition
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on service, distribution, schema, contract, lineage, quality and related resource binding, for which purpose and under what authority? process
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify service, distribution, schema, contract, lineage, quality and related resource binding? state

Discovery, semantics, coverage, version and provenance Groups governed catalog context for discovery, semantics, coverage, version and provenance.

Discovery language, taxonomy and semantic description

Groups source-qualified catalog context for discovery language, taxonomy and semantic description.

Title, description, keyword, category, glossary, concept and language

Records title, description, keyword, category, glossary, concept and language as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish title, description, keyword, category, glossary, concept and language? classification
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on title, description, keyword, category, glossary, concept and language, for which purpose and under what authority? validation
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify title, description, keyword, category, glossary, concept and language? identity

Search index, ranking, curation, audience and discovery evidence

Records search index, ranking, curation, audience and discovery evidence as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish search index, ranking, curation, audience and discovery evidence? evidence
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on search index, ranking, curation, audience and discovery evidence, for which purpose and under what authority? privacy
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify search index, ranking, curation, audience and discovery evidence? classification

Coverage, cadence, provenance, version and deprecation

Groups source-qualified catalog context for coverage, cadence, provenance, version and deprecation.

Spatial, temporal, subject, population, variable, granularity and update frequency

Records spatial, temporal, subject, population, variable, granularity and update frequency as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish spatial, temporal, subject, population, variable, granularity and update frequency? temporal
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on spatial, temporal, subject, population, variable, granularity and update frequency, for which purpose and under what authority? lifecycle
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify spatial, temporal, subject, population, variable, granularity and update frequency? relationship

Source, generation, citation, attribution, revision, change, deprecation and sunset

Records source, generation, citation, attribution, revision, change, deprecation and sunset as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish source, generation, citation, attribution, revision, change, deprecation and sunset? provenance
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on source, generation, citation, attribution, revision, change, deprecation and sunset, for which purpose and under what authority? quality
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify source, generation, citation, attribution, revision, change, deprecation and sunset? authority

Interfaces, access, rights, terms and consumption Groups governed catalog context for interfaces, access, rights, terms and consumption.

Interfaces, formats, endpoints and delivery routes

Groups source-qualified catalog context for interfaces, formats, endpoints and delivery routes.

Landing, access, download, API endpoint, protocol, operation and response

Records landing, access, download, api endpoint, protocol, operation and response as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish landing, access, download, api endpoint, protocol, operation and response? interoperability
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on landing, access, download, api endpoint, protocol, operation and response, for which purpose and under what authority? security
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify landing, access, download, api endpoint, protocol, operation and response? requirement

Format, media, package, compression, checksum, partition and delivery mode

Records format, media, package, compression, checksum, partition and delivery mode as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish format, media, package, compression, checksum, partition and delivery mode? validation
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on format, media, package, compression, checksum, partition and delivery mode, for which purpose and under what authority? retention
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify format, media, package, compression, checksum, partition and delivery mode? constraint

Eligibility, rights, privacy, commercial and service terms

Groups source-qualified catalog context for eligibility, rights, privacy, commercial and service terms.

Authentication, authorization, access request, eligibility, approval and workspace

Records authentication, authorization, access request, eligibility, approval and workspace as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish authentication, authorization, access request, eligibility, approval and workspace? security
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on authentication, authorization, access request, eligibility, approval and workspace, for which purpose and under what authority? interoperability
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify authentication, authorization, access request, eligibility, approval and workspace? event

Licence, rights, purpose, residency, retention, pricing, contract, subscription, SLA and support

Records licence, rights, purpose, residency, retention, pricing, contract, subscription, sla and support as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish licence, rights, purpose, residency, retention, pricing, contract, subscription, sla and support? privacy
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on licence, rights, purpose, residency, retention, pricing, contract, subscription, sla and support, for which purpose and under what authority? decision
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify licence, rights, purpose, residency, retention, pricing, contract, subscription, sla and support? temporal

Quality, SLO, observability, feedback and value Groups governed catalog context for quality, slo, observability, feedback and value.

Contract, quality, SLO and observed service levels

Groups source-qualified catalog context for contract, quality, slo and observed service levels.

Contract, schema, quality assessment, certificate, conformance and limitation

Records contract, schema, quality assessment, certificate, conformance and limitation as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish contract, schema, quality assessment, certificate, conformance and limitation? quality
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on contract, schema, quality assessment, certificate, conformance and limitation, for which purpose and under what authority? state
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify contract, schema, quality assessment, certificate, conformance and limitation? composition

Freshness, availability, latency, completeness, reliability, SLO target and observation

Records freshness, availability, latency, completeness, reliability, slo target and observation as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish freshness, availability, latency, completeness, reliability, slo target and observation? measurement
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on freshness, availability, latency, completeness, reliability, slo target and observation, for which purpose and under what authority? identity
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify freshness, availability, latency, completeness, reliability, slo target and observation? evidence

Usage, feedback, issues, outcomes and fitness evidence

Groups source-qualified catalog context for usage, feedback, issues, outcomes and fitness evidence.

Consumer, usage, adoption, feedback, annotation, rating, issue and support case

Records consumer, usage, adoption, feedback, annotation, rating, issue and support case as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish consumer, usage, adoption, feedback, annotation, rating, issue and support case? evidence
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on consumer, usage, adoption, feedback, annotation, rating, issue and support case, for which purpose and under what authority? classification
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify consumer, usage, adoption, feedback, annotation, rating, issue and support case? ownership

Outcome, benefit, cost, risk, fitness claim, confidence and uncertainty

Records outcome, benefit, cost, risk, fitness claim, confidence and uncertainty as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish outcome, benefit, cost, risk, fitness claim, confidence and uncertainty? decision
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on outcome, benefit, cost, risk, fitness claim, confidence and uncertainty, for which purpose and under what authority? relationship
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify outcome, benefit, cost, risk, fitness claim, confidence and uncertainty? measurement

Governance, lifecycle, federation, records and projections Groups governed catalog context for governance, lifecycle, federation, records and projections.

Publication, availability, access, delivery and governance events

Groups source-qualified catalog context for publication, availability, access, delivery and governance events.

Draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired

Records draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired? lifecycle
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired, for which purpose and under what authority? authority
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired? exception

Change, approval, violation, incident, exception, remediation, correction and audit event

Records change, approval, violation, incident, exception, remediation, correction and audit event as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish change, approval, violation, incident, exception, remediation, correction and audit event? event
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on change, approval, violation, incident, exception, remediation, correction and audit event, for which purpose and under what authority? requirement
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify change, approval, violation, incident, exception, remediation, correction and audit event? provenance

Federation, access, records and interoperability projections

Groups source-qualified catalog context for federation, access, records and interoperability projections.

Federated source, harvest, sync, conflict, search view, access, retention and tombstone

Records federated source, harvest, sync, conflict, search view, access, retention and tombstone as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish federated source, harvest, sync, conflict, search view, access, retention and tombstone? retention
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on federated source, harvest, sync, conflict, search view, access, retention and tombstone, for which purpose and under what authority? constraint
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify federated source, harvest, sync, conflict, search view, access, retention and tombstone? process

DCAT, DCAT-AP, DPROD, ODPS, Schema.org, DataCite, FAIR, PROV, DQV, ODRL, DPV, OpenAPI and time projection

Records dcat, dcat-ap, dprod, odps, schema.org, datacite, fair, prov, dqv, odrl, dpv, openapi and time projection as source-qualified catalog context while dataset, service, distribution, policy, agreement, subscription, order, delivery, usage, issue, audit and records masters remain external.

What stable identity, version, typed value, scope and explicit unknown establish dcat, dcat-ap, dprod, odps, schema.org, datacite, fair, prov, dqv, odrl, dpv, openapi and time projection? interoperability
Who created, owns, asserts, reviews, approves, supplies, consumes or may rely on dcat, dcat-ap, dprod, odps, schema.org, datacite, fair, prov, dqv, odrl, dpv, openapi and time projection, for which purpose and under what authority? event
Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify dcat, dcat-ap, dprod, odps, schema.org, datacite, fair, prov, dqv, odrl, dpv, openapi and time projection? validation

Classifiers Filled

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

What it is Filled

Owns catalog-record identity, version and lifecycle; separate offering identity and product semantics; discovery and classification; purpose, value and intended use; roles; dataset, service, distribution, contract, schema, lineage and quality references; interface and access-route descriptions; rights, privacy, commercial and service-term references; quality and SLO summaries; feedback, usage indicators, provenance, lifecycle, federation, correction, access, retention, audit and projections. Dataset bytes, services, distributions, policies, agreements, subscriptions, orders, deliveries, usage events, issues, audits and records masters remain external where authoritative.

In scope

Catalog record and distinct data-product offering identity, ownership, purpose, discovery, classifications, coverage, versions and provenance
Non-owning resource composition, interfaces, access routes, rights and terms, quality and SLO summaries, feedback, lifecycle, federation, records and projections

Out of scope

Owning Dataset, Data Service, Distribution, Contract, Schema, Lineage, Quality Assessment, Policy, Agreement, Subscription, Order, Delivery, Usage, Issue, Audit or Records masters
Treating listing or publication as proof of discoverability, availability, authorization, delivery, acceptance, fitness or usage
Autonomous resource publication, access approval, licence or contract change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or physical records disposition

Why it exists Filled

Distinguishing features Filled

Separates the catalogue record from the data product offering it describes.
Listing is independent of availability, authorization, delivery and fitness.
References datasets, services and distributions rather than holding the data.
Differs from a data contract, which governs exchange terms, and from a quality assessment.

What robots and AI may and may not do Filled

Must not

Publish resources or approve access requests.
Change licences, contracts or terms.
Create subscriptions or payments.
Describe a product as available or fit when evidence says otherwise.
Expose metadata that reveals personal data.

Only with a human decision

Publishing, withdrawing or retiring an entry.
Approving access to restricted products.
Changing licence or terms of use.

May

Register and describe a catalogue record and offering.
Enrich discovery metadata such as keywords, coverage and classifications.
Answer search queries and federate with other catalogues.
Record feedback and usage signals.

Moral aspects Filled

Catalogue metadata can itself reveal sensitive facts about people or places.
Honest description of limits prevents misuse of data.
Open discovery supports fair access to public data.

Who is affected

Data consumers
Data subjects
Data product owners

Owners Filled

Steward

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

Roles

Catalog authority: Own catalog scope, registration rules, publication policy, federation and record lifecycle.
Data product owner: Own offering purpose, value, resource composition, consumer outcomes and accountable use.
Data steward: Own dataset semantics, taxonomy, quality, provenance and authoritative metadata bindings.
Service and distribution owner: Own endpoints, formats, operations, delivery routes, SLOs and support evidence.
Rights, privacy and access authority: Own licence, policy, purpose, eligibility, privacy, agreement and access-decision references.
Catalog curator and reviewer: Review descriptions, classifications, versions, evidence, conflicts, limitations and lifecycle proposals.
Records and federation steward: Own harvesting, conflict, correction, retention, tombstone, audit and projection policy.

Links to other meta-models Filled

references

WM-DAT-001 Dataset - Represent the candidate governed data-resource boundary without ownership, mutation or cascade authority.
WM-DAT-004 Data Schema / Data Contract - Resolve authoritative structural and contractual expectations without absorbing their lifecycle.
WM-DAT-006 Data Lineage - Resolve source and transformation provenance without owning lineage events.
WM-DAT-007 Data Quality Assessment - Resolve purpose-qualified quality evidence without certifying fitness.
Data Service, Distribution, Policy, Agreement, Subscription, Delivery, Usage, Issue, Audit and Records models - Resolve authoritative operational, legal, commercial and evidentiary masters without changing their ownership.

aligned

DCAT 3, DCAT-AP 3.0.1, DPROD 1.0 Beta 1, ODPS 4.1, Schema.org Dataset, DataCite 4.6, FAIR, PROV-O, DQV, ODRL 2.2, DPV 2.0, OpenAPI 3.1.1, OWL-Time and RFC 3339 - Project version-pinned discovery, product, citation, provenance, quality, rights, privacy, interface and time views with declared loss.

neighbor

WM-DAT-001 Dataset - The candidate relation identifies governed data resources and versions. The catalog record and offering own discovery and product context but not dataset identity, bytes or lifecycle.
CatalogRecord, DataProduct, DatasetSeries, Distribution and DataService - These identities remain separate. One record describes one resource head; an offering composes resources by role without collapsing them.
WM-DAT-004 Data Schema / Data Contract, WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Assessment - The catalog stores versioned references and qualified summaries but not authoritative contract, schema, lineage or assessment lifecycles.
Policy, agreement, subscription, order, delivery, usage, issue, audit and records - These masters retain independent parties, authority, state, evidence and time. The catalog describes routes and references but executes none of them.
DCAT, DCAT-AP, DPROD, ODPS, Schema.org, DataCite, FAIR, PROV, DQV, ODRL, DPV, OpenAPI and time - Each source has a distinct scope and normative force. Every mapping is version-pinned, profile-qualified and loss-declaring.

parent

WM-DAT-001

What else AI and robots need to interact with it Filled

Sources Filled

Data Catalog Vocabulary DCAT Version 3 - World Wide Web Consortium
DCAT Application Profile for data portals in Europe - European Commission SEMIC
Data on the Web Best Practices - World Wide Web Consortium
PROV-O The PROV Ontology - World Wide Web Consortium
Data on the Web Best Practices Data Quality Vocabulary - World Wide Web Consortium
ODRL Information Model 2.2 - World Wide Web Consortium
Data Privacy Vocabulary - World Wide Web Consortium Data Privacy Vocabularies and Controls Community Group
Data Product Ontology - Object Management Group
Open Data Product Specification - Linux Foundation
Dataset - Schema.org
DataCite Metadata Schema Documentation for the Publication and Citation of Research Data and Other Research Outputs - DataCite
NIST Research Data Framework Version 2.0 - National Institute of Standards and Technology
FAIR Guiding Principles for scientific data management and stewardship - Scientific Data
Time Ontology in OWL - World Wide Web Consortium
Date and Time on the Internet Timestamps - Internet Engineering Task Force
OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

Approve or reject the WM-DAT-001 relation and register dedicated Data Service, Distribution, Policy, Agreement, Subscription, Delivery, Usage, Issue, Audit and Records edges.
Create domain, taxonomy, commercial, legal, privacy, access-workflow, service-level, quality-method and organizational profiles.
Conformance-test resource composition, access routes, rights expressions, SLO calculations and lifecycle transitions against concrete catalog engines.
Validate organization-specific publication, federation, consumer disclosure, legal hold, retention, withdrawal and disposition policies.
Revisit DPROD after finalization and re-check all current-at-access profiles before canonical promotion.
Obtain independent external review before promoting beyond reviewable-draft assurance.
Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
The WM-DAT-001 relation remains candidate and grants no approved ownership or cascade behavior.
DPROD 1.0 Beta 1 and current-at-access profiles require future version review and conformance testing.
Domain taxonomies, commercial terms, legal rules, access workflows, quality methods and service-level calculations require separate 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-008-data-catalog-entry-data-product/spec.yaml, ver-cy/world-models/card-supplements/wm-dat-008-data-catalog-entry-data-product.json