{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-dat-008","code":"wm-dat-008-data-catalog-entry-data-product","url":"https://ver.cy/models/wm-dat-008-data-catalog-entry-data-product/","name":"Data Catalog Entry / Data Product","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"aggregate","plane":"","domain":["INF.DAT.CAT"],"industry":["Cross-industry"],"navPath":"NAV.INF.DAT.CAT","tags":["data","catalog","entry","product","inf.dat.cat"],"facets":{}},"whatItIs":"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.","purpose":"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.","scope":{"in":["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":["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"],"boundaries":[{"neighbor":"WM-DAT-001 Dataset","distinction":"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."},{"neighbor":"CatalogRecord, DataProduct, DatasetSeries, Distribution and DataService","distinction":"These identities remain separate. One record describes one resource head; an offering composes resources by role without collapsing them."},{"neighbor":"WM-DAT-004 Data Schema / Data Contract, WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Assessment","distinction":"The catalog stores versioned references and qualified summaries but not authoritative contract, schema, lineage or assessment lifecycles."},{"neighbor":"Policy, agreement, subscription, order, delivery, usage, issue, audit and records","distinction":"These masters retain independent parties, authority, state, evidence and time. The catalog describes routes and references but executes none of them."},{"neighbor":"DCAT, DCAT-AP, DPROD, ODPS, Schema.org, DataCite, FAIR, PROV, DQV, ODRL, DPV, OpenAPI and time","distinction":"Each source has a distinct scope and normative force. Every mapping is version-pinned, profile-qualified and loss-declaring."}]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"record-product-identity-scope-and-value","name":"Catalog record and product identity, scope and value","description":"Groups governed catalog context for catalog record and product identity, scope and value.","layers":[{"id":"catalog-record-identity-version-and-status","name":"Catalog record identity, version and status","description":"Groups source-qualified catalog context for catalog record identity, version and status.","findings":[{"id":"catalog-record-id-catalog-entry-version-head-and-record-status","name":"Catalog record ID, catalog, entry version, head and record status","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish catalog record id, catalog, entry version, head and record status?","id":"catalog-record-id-catalog-entry-version-head-and-record-status-q01","kind":"identity"},{"text":"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?","id":"catalog-record-id-catalog-entry-version-head-and-record-status-q02","kind":"temporal"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify catalog record id, catalog, entry version, head and record status?","id":"catalog-record-id-catalog-entry-version-head-and-record-status-q03","kind":"privacy"}]},{"id":"record-creator-publisher-created-modified-language-and-contact","name":"Record creator, publisher, created, modified, language and contact","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish record creator, publisher, created, modified, language and contact?","id":"record-creator-publisher-created-modified-language-and-contact-q01","kind":"ownership"},{"text":"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?","id":"record-creator-publisher-created-modified-language-and-contact-q02","kind":"composition"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify record creator, publisher, created, modified, language and contact?","id":"record-creator-publisher-created-modified-language-and-contact-q03","kind":"lifecycle"}]}]},{"id":"data-product-identity-purpose-and-market-scope","name":"Data product identity, purpose and market scope","description":"Groups source-qualified catalog context for data product identity, purpose and market scope.","findings":[{"id":"product-id-name-version-type-domain-themes-tags-and-aliases","name":"Product ID, name, version, type, domain, themes, tags and aliases","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish product id, name, version, type, domain, themes, tags and aliases?","id":"product-id-name-version-type-domain-themes-tags-and-aliases-q01","kind":"classification"},{"text":"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?","id":"product-id-name-version-type-domain-themes-tags-and-aliases-q02","kind":"evidence"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify product id, name, version, type, domain, themes, tags and aliases?","id":"product-id-name-version-type-domain-themes-tags-and-aliases-q03","kind":"quality"}]},{"id":"purpose-value-proposition-intended-use-non-use-audience-and-outcome","name":"Purpose, value proposition, intended use, non-use, audience and outcome","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish purpose, value proposition, intended use, non-use, audience and outcome?","id":"purpose-value-proposition-intended-use-non-use-audience-and-outcome-q01","kind":"requirement"},{"text":"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?","id":"purpose-value-proposition-intended-use-non-use-audience-and-outcome-q02","kind":"ownership"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify purpose, value proposition, intended use, non-use, audience and outcome?","id":"purpose-value-proposition-intended-use-non-use-audience-and-outcome-q03","kind":"security"}]}]}]},{"id":"ownership-stewardship-resources-and-composition","name":"Ownership, stewardship, resources and composition","description":"Groups governed catalog context for ownership, stewardship, resources and composition.","layers":[{"id":"ownership-accountability-and-support","name":"Ownership, accountability and support","description":"Groups source-qualified catalog context for ownership, accountability and support.","findings":[{"id":"owner-holder-publisher-steward-product-manager-and-accountable-authority","name":"Owner, holder, publisher, steward, product manager and accountable authority","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish owner, holder, publisher, steward, product manager and accountable authority?","id":"owner-holder-publisher-steward-product-manager-and-accountable-authority-q01","kind":"authority"},{"text":"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?","id":"owner-holder-publisher-steward-product-manager-and-accountable-authority-q02","kind":"measurement"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify owner, holder, publisher, steward, product manager and accountable authority?","id":"owner-holder-publisher-steward-product-manager-and-accountable-authority-q03","kind":"retention"}]},{"id":"producer-custodian-contact-support-consumer-and-role-delegation","name":"Producer, custodian, contact, support, consumer and role delegation","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish producer, custodian, contact, support, consumer and role delegation?","id":"producer-custodian-contact-support-consumer-and-role-delegation-q01","kind":"ownership"},{"text":"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?","id":"producer-custodian-contact-support-consumer-and-role-delegation-q02","kind":"exception"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify producer, custodian, contact, support, consumer and role delegation?","id":"producer-custodian-contact-support-consumer-and-role-delegation-q03","kind":"interoperability"}]}]},{"id":"dataset-service-distribution-and-related-resource-bindings","name":"Dataset, service, distribution and related resource bindings","description":"Groups source-qualified catalog context for dataset, service, distribution and related resource bindings.","findings":[{"id":"dataset-version-series-role-and-authoritative-source-binding","name":"Dataset, version, series, role and authoritative source binding","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish dataset, version, series, role and authoritative source binding?","id":"dataset-version-series-role-and-authoritative-source-binding-q01","kind":"relationship"},{"text":"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?","id":"dataset-version-series-role-and-authoritative-source-binding-q02","kind":"provenance"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify dataset, version, series, role and authoritative source binding?","id":"dataset-version-series-role-and-authoritative-source-binding-q03","kind":"decision"}]},{"id":"service-distribution-schema-contract-lineage-quality-and-related-resource-binding","name":"Service, distribution, schema, contract, lineage, quality and related resource binding","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish service, distribution, schema, contract, lineage, quality and related resource binding?","id":"service-distribution-schema-contract-lineage-quality-and-related-resource-binding-q01","kind":"composition"},{"text":"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?","id":"service-distribution-schema-contract-lineage-quality-and-related-resource-binding-q02","kind":"process"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify service, distribution, schema, contract, lineage, quality and related resource binding?","id":"service-distribution-schema-contract-lineage-quality-and-related-resource-binding-q03","kind":"state"}]}]}]},{"id":"discovery-semantics-coverage-version-and-provenance","name":"Discovery, semantics, coverage, version and provenance","description":"Groups governed catalog context for discovery, semantics, coverage, version and provenance.","layers":[{"id":"discovery-language-taxonomy-and-semantic-description","name":"Discovery language, taxonomy and semantic description","description":"Groups source-qualified catalog context for discovery language, taxonomy and semantic description.","findings":[{"id":"title-description-keyword-category-glossary-concept-and-language","name":"Title, description, keyword, category, glossary, concept and language","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish title, description, keyword, category, glossary, concept and language?","id":"title-description-keyword-category-glossary-concept-and-language-q01","kind":"classification"},{"text":"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?","id":"title-description-keyword-category-glossary-concept-and-language-q02","kind":"validation"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify title, description, keyword, category, glossary, concept and language?","id":"title-description-keyword-category-glossary-concept-and-language-q03","kind":"identity"}]},{"id":"search-index-ranking-curation-audience-and-discovery-evidence","name":"Search index, ranking, curation, audience and discovery evidence","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish search index, ranking, curation, audience and discovery evidence?","id":"search-index-ranking-curation-audience-and-discovery-evidence-q01","kind":"evidence"},{"text":"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?","id":"search-index-ranking-curation-audience-and-discovery-evidence-q02","kind":"privacy"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify search index, ranking, curation, audience and discovery evidence?","id":"search-index-ranking-curation-audience-and-discovery-evidence-q03","kind":"classification"}]}]},{"id":"coverage-cadence-provenance-version-and-deprecation","name":"Coverage, cadence, provenance, version and deprecation","description":"Groups source-qualified catalog context for coverage, cadence, provenance, version and deprecation.","findings":[{"id":"spatial-temporal-subject-population-variable-granularity-and-update-frequency","name":"Spatial, temporal, subject, population, variable, granularity and update frequency","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish spatial, temporal, subject, population, variable, granularity and update frequency?","id":"spatial-temporal-subject-population-variable-granularity-and-update-frequency-q01","kind":"temporal"},{"text":"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?","id":"spatial-temporal-subject-population-variable-granularity-and-update-frequency-q02","kind":"lifecycle"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify spatial, temporal, subject, population, variable, granularity and update frequency?","id":"spatial-temporal-subject-population-variable-granularity-and-update-frequency-q03","kind":"relationship"}]},{"id":"source-generation-citation-attribution-revision-change-deprecation-and-sunset","name":"Source, generation, citation, attribution, revision, change, deprecation and sunset","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish source, generation, citation, attribution, revision, change, deprecation and sunset?","id":"source-generation-citation-attribution-revision-change-deprecation-and-sunset-q01","kind":"provenance"},{"text":"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?","id":"source-generation-citation-attribution-revision-change-deprecation-and-sunset-q02","kind":"quality"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify source, generation, citation, attribution, revision, change, deprecation and sunset?","id":"source-generation-citation-attribution-revision-change-deprecation-and-sunset-q03","kind":"authority"}]}]}]},{"id":"interfaces-access-rights-terms-and-consumption","name":"Interfaces, access, rights, terms and consumption","description":"Groups governed catalog context for interfaces, access, rights, terms and consumption.","layers":[{"id":"interfaces-formats-endpoints-and-delivery-routes","name":"Interfaces, formats, endpoints and delivery routes","description":"Groups source-qualified catalog context for interfaces, formats, endpoints and delivery routes.","findings":[{"id":"landing-access-download-api-endpoint-protocol-operation-and-response","name":"Landing, access, download, API endpoint, protocol, operation and response","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish landing, access, download, api endpoint, protocol, operation and response?","id":"landing-access-download-api-endpoint-protocol-operation-and-response-q01","kind":"interoperability"},{"text":"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?","id":"landing-access-download-api-endpoint-protocol-operation-and-response-q02","kind":"security"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify landing, access, download, api endpoint, protocol, operation and response?","id":"landing-access-download-api-endpoint-protocol-operation-and-response-q03","kind":"requirement"}]},{"id":"format-media-package-compression-checksum-partition-and-delivery-mode","name":"Format, media, package, compression, checksum, partition and delivery mode","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish format, media, package, compression, checksum, partition and delivery mode?","id":"format-media-package-compression-checksum-partition-and-delivery-mode-q01","kind":"validation"},{"text":"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?","id":"format-media-package-compression-checksum-partition-and-delivery-mode-q02","kind":"retention"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify format, media, package, compression, checksum, partition and delivery mode?","id":"format-media-package-compression-checksum-partition-and-delivery-mode-q03","kind":"constraint"}]}]},{"id":"eligibility-rights-privacy-commercial-and-service-terms","name":"Eligibility, rights, privacy, commercial and service terms","description":"Groups source-qualified catalog context for eligibility, rights, privacy, commercial and service terms.","findings":[{"id":"authentication-authorization-access-request-eligibility-approval-and-workspace","name":"Authentication, authorization, access request, eligibility, approval and workspace","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish authentication, authorization, access request, eligibility, approval and workspace?","id":"authentication-authorization-access-request-eligibility-approval-and-workspace-q01","kind":"security"},{"text":"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?","id":"authentication-authorization-access-request-eligibility-approval-and-workspace-q02","kind":"interoperability"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify authentication, authorization, access request, eligibility, approval and workspace?","id":"authentication-authorization-access-request-eligibility-approval-and-workspace-q03","kind":"event"}]},{"id":"licence-rights-purpose-residency-retention-pricing-contract-subscription-sla-and-support","name":"Licence, rights, purpose, residency, retention, pricing, contract, subscription, SLA and support","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish licence, rights, purpose, residency, retention, pricing, contract, subscription, sla and support?","id":"licence-rights-purpose-residency-retention-pricing-contract-subscription-sla-and-support-q01","kind":"privacy"},{"text":"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?","id":"licence-rights-purpose-residency-retention-pricing-contract-subscription-sla-and-support-q02","kind":"decision"},{"text":"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?","id":"licence-rights-purpose-residency-retention-pricing-contract-subscription-sla-and-support-q03","kind":"temporal"}]}]}]},{"id":"quality-slo-observability-feedback-and-value","name":"Quality, SLO, observability, feedback and value","description":"Groups governed catalog context for quality, slo, observability, feedback and value.","layers":[{"id":"contract-quality-slo-and-observed-service-levels","name":"Contract, quality, SLO and observed service levels","description":"Groups source-qualified catalog context for contract, quality, slo and observed service levels.","findings":[{"id":"contract-schema-quality-assessment-certificate-conformance-and-limitation","name":"Contract, schema, quality assessment, certificate, conformance and limitation","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish contract, schema, quality assessment, certificate, conformance and limitation?","id":"contract-schema-quality-assessment-certificate-conformance-and-limitation-q01","kind":"quality"},{"text":"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?","id":"contract-schema-quality-assessment-certificate-conformance-and-limitation-q02","kind":"state"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify contract, schema, quality assessment, certificate, conformance and limitation?","id":"contract-schema-quality-assessment-certificate-conformance-and-limitation-q03","kind":"composition"}]},{"id":"freshness-availability-latency-completeness-reliability-slo-target-and-observation","name":"Freshness, availability, latency, completeness, reliability, SLO target and observation","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish freshness, availability, latency, completeness, reliability, slo target and observation?","id":"freshness-availability-latency-completeness-reliability-slo-target-and-observation-q01","kind":"measurement"},{"text":"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?","id":"freshness-availability-latency-completeness-reliability-slo-target-and-observation-q02","kind":"identity"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify freshness, availability, latency, completeness, reliability, slo target and observation?","id":"freshness-availability-latency-completeness-reliability-slo-target-and-observation-q03","kind":"evidence"}]}]},{"id":"usage-feedback-issues-outcomes-and-fitness-evidence","name":"Usage, feedback, issues, outcomes and fitness evidence","description":"Groups source-qualified catalog context for usage, feedback, issues, outcomes and fitness evidence.","findings":[{"id":"consumer-usage-adoption-feedback-annotation-rating-issue-and-support-case","name":"Consumer, usage, adoption, feedback, annotation, rating, issue and support case","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish consumer, usage, adoption, feedback, annotation, rating, issue and support case?","id":"consumer-usage-adoption-feedback-annotation-rating-issue-and-support-case-q01","kind":"evidence"},{"text":"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?","id":"consumer-usage-adoption-feedback-annotation-rating-issue-and-support-case-q02","kind":"classification"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify consumer, usage, adoption, feedback, annotation, rating, issue and support case?","id":"consumer-usage-adoption-feedback-annotation-rating-issue-and-support-case-q03","kind":"ownership"}]},{"id":"outcome-benefit-cost-risk-fitness-claim-confidence-and-uncertainty","name":"Outcome, benefit, cost, risk, fitness claim, confidence and uncertainty","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish outcome, benefit, cost, risk, fitness claim, confidence and uncertainty?","id":"outcome-benefit-cost-risk-fitness-claim-confidence-and-uncertainty-q01","kind":"decision"},{"text":"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?","id":"outcome-benefit-cost-risk-fitness-claim-confidence-and-uncertainty-q02","kind":"relationship"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify outcome, benefit, cost, risk, fitness claim, confidence and uncertainty?","id":"outcome-benefit-cost-risk-fitness-claim-confidence-and-uncertainty-q03","kind":"measurement"}]}]}]},{"id":"governance-lifecycle-federation-records-and-projections","name":"Governance, lifecycle, federation, records and projections","description":"Groups governed catalog context for governance, lifecycle, federation, records and projections.","layers":[{"id":"publication-availability-access-delivery-and-governance-events","name":"Publication, availability, access, delivery and governance events","description":"Groups source-qualified catalog context for publication, availability, access, delivery and governance events.","findings":[{"id":"draft-reviewed-approved-published-discoverable-available-deprecated-withdrawn-and-retired","name":"Draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired?","id":"draft-reviewed-approved-published-discoverable-available-deprecated-withdrawn-and-retired-q01","kind":"lifecycle"},{"text":"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?","id":"draft-reviewed-approved-published-discoverable-available-deprecated-withdrawn-and-retired-q02","kind":"authority"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify draft, reviewed, approved, published, discoverable, available, deprecated, withdrawn and retired?","id":"draft-reviewed-approved-published-discoverable-available-deprecated-withdrawn-and-retired-q03","kind":"exception"}]},{"id":"change-approval-violation-incident-exception-remediation-correction-and-audit-event","name":"Change, approval, violation, incident, exception, remediation, correction and audit event","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish change, approval, violation, incident, exception, remediation, correction and audit event?","id":"change-approval-violation-incident-exception-remediation-correction-and-audit-event-q01","kind":"event"},{"text":"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?","id":"change-approval-violation-incident-exception-remediation-correction-and-audit-event-q02","kind":"requirement"},{"text":"Which event, effective, publication, modification, recorded, ingestion and knowledge times, evidence and uncertainty qualify change, approval, violation, incident, exception, remediation, correction and audit event?","id":"change-approval-violation-incident-exception-remediation-correction-and-audit-event-q03","kind":"provenance"}]}]},{"id":"federation-access-records-and-interoperability-projections","name":"Federation, access, records and interoperability projections","description":"Groups source-qualified catalog context for federation, access, records and interoperability projections.","findings":[{"id":"federated-source-harvest-sync-conflict-search-view-access-retention-and-tombstone","name":"Federated source, harvest, sync, conflict, search view, access, retention and tombstone","description":"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.","questions":[{"text":"What stable identity, version, typed value, scope and explicit unknown establish federated source, harvest, sync, conflict, search view, access, retention and tombstone?","id":"federated-source-harvest-sync-conflict-search-view-access-retention-and-tombstone-q01","kind":"retention"},{"text":"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?","id":"federated-source-harvest-sync-conflict-search-view-access-retention-and-tombstone-q02","kind":"constraint"},{"text":"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?","id":"federated-source-harvest-sync-conflict-search-view-access-retention-and-tombstone-q03","kind":"process"}]},{"id":"dcat-dcat-ap-dprod-odps-schema-org-datacite-fair-prov-dqv-odrl-dpv-openapi-and-time-projection","name":"DCAT, DCAT-AP, DPROD, ODPS, Schema.org, DataCite, FAIR, PROV, DQV, ODRL, DPV, OpenAPI and time projection","description":"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.","questions":[{"text":"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?","id":"dcat-dcat-ap-dprod-odps-schema-org-datacite-fair-prov-dqv-odrl-dpv-openapi-and-time-projection-q01","kind":"interoperability"},{"text":"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?","id":"dcat-dcat-ap-dprod-odps-schema-org-datacite-fair-prov-dqv-odrl-dpv-openapi-and-time-projection-q02","kind":"event"},{"text":"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?","id":"dcat-dcat-ap-dprod-odps-schema-org-datacite-fair-prov-dqv-odrl-dpv-openapi-and-time-projection-q03","kind":"validation"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["Publishing, withdrawing or retiring an entry.","Approving access to restricted products.","Changing licence or terms of use."]},"ethics":{"considerations":["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."],"affectedParties":["Data consumers","Data subjects","Data product owners"]},"owners":{"steward":"Dimension owner, namespace authority, catalog governance mandate and accountable data product owner","roles":[{"name":"Catalog authority","responsibilities":["Own catalog scope, registration rules, publication policy, federation and record lifecycle."]},{"name":"Data product owner","responsibilities":["Own offering purpose, value, resource composition, consumer outcomes and accountable use."]},{"name":"Data steward","responsibilities":["Own dataset semantics, taxonomy, quality, provenance and authoritative metadata bindings."]},{"name":"Service and distribution owner","responsibilities":["Own endpoints, formats, operations, delivery routes, SLOs and support evidence."]},{"name":"Rights, privacy and access authority","responsibilities":["Own licence, policy, purpose, eligibility, privacy, agreement and access-decision references."]},{"name":"Catalog curator and reviewer","responsibilities":["Review descriptions, classifications, versions, evidence, conflicts, limitations and lifecycle proposals."]},{"name":"Records and federation steward","responsibilities":["Own harvesting, conflict, correction, retention, tombstone, audit and projection policy."]}],"masterSystems":[]},"relations":[{"target":"WM-DAT-001 Dataset","type":"references","note":"Represent the candidate governed data-resource boundary without ownership, mutation or cascade authority."},{"target":"WM-DAT-004 Data Schema / Data Contract","type":"references","note":"Resolve authoritative structural and contractual expectations without absorbing their lifecycle."},{"target":"WM-DAT-006 Data Lineage","type":"references","note":"Resolve source and transformation provenance without owning lineage events."},{"target":"WM-DAT-007 Data Quality Assessment","type":"references","note":"Resolve purpose-qualified quality evidence without certifying fitness."},{"target":"Data Service, Distribution, Policy, Agreement, Subscription, Delivery, Usage, Issue, Audit and Records models","type":"references","note":"Resolve authoritative operational, legal, commercial and evidentiary masters without changing their ownership."},{"target":"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","type":"aligned","note":"Project version-pinned discovery, product, citation, provenance, quality, rights, privacy, interface and time views with declared loss."},{"target":"WM-DAT-001 Dataset","type":"neighbor","note":"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."},{"target":"CatalogRecord, DataProduct, DatasetSeries, Distribution and DataService","type":"neighbor","note":"These identities remain separate. One record describes one resource head; an offering composes resources by role without collapsing them."},{"target":"WM-DAT-004 Data Schema / Data Contract, WM-DAT-006 Data Lineage and WM-DAT-007 Data Quality Assessment","type":"neighbor","note":"The catalog stores versioned references and qualified summaries but not authoritative contract, schema, lineage or assessment lifecycles."},{"target":"Policy, agreement, subscription, order, delivery, usage, issue, audit and records","type":"neighbor","note":"These masters retain independent parties, authority, state, evidence and time. The catalog describes routes and references but executes none of them."},{"target":"DCAT, DCAT-AP, DPROD, ODPS, Schema.org, DataCite, FAIR, PROV, DQV, ODRL, DPV, OpenAPI and time","type":"neighbor","note":"Each source has a distinct scope and normative force. Every mapping is version-pinned, profile-qualified and loss-declaring."},{"target":"WM-DAT-001","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier for each catalog record, offering, resource binding, policy reference or artifact, qualified by issuer, namespace and record kind.","Governed globally resolvable catalog-record or offering IRI.","Dimension UUID or ULID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A catalogue entry names a title, a publisher, an owner, distributions or services, a licence and a status.","Often confused with the dataset, a distribution file, an API endpoint or a data contract."]},"capabilities":{"applicability":"required","items":["Register a catalog record and offering: Governed operation to register a catalog record and offering without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Bind authoritative owner, product and purpose: Governed operation to bind authoritative owner, product and purpose without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Compose dataset, service and distribution references: Governed operation to compose dataset, service and distribution references without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Enrich discovery semantics and coverage: Governed operation to enrich discovery semantics and coverage without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Bind contract, schema, quality and lineage references: Governed operation to bind contract, schema, quality and lineage references without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Record interface, access and delivery routes: Governed operation to record interface, access and delivery routes without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Record rights, terms, SLO and support profiles: Governed operation to record rights, terms, slo and support profiles without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Publish, deprecate, withdraw or retire a catalog record: Governed operation to publish, deprecate, withdraw or retire a catalog record without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Record feedback, usage, outcomes and issues: Governed operation to record feedback, usage, outcomes and issues without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition.","Query, federate, project, correct, retain and audit: Governed operation to query, federate, project, correct, retain and audit without autonomous resource publication, access approval, agreement change, subscription, payment, delivery, dataset mutation, quality certification, service retirement or records disposition."]},"hazards":{"applicability":"required","items":["Stale entries pointing to withdrawn or changed data.","Misleading descriptions of coverage or quality.","Metadata leakage of sensitive information."]},"interfaces":{"applicability":"required","items":["W3C DCAT 3 and DCAT-AP.","DataCite Metadata Schema.","Schema.org Dataset.","W3C ODRL and the W3C Data Privacy Vocabulary (DPV).","OpenAPI Specification for data services.","FAIR Guiding Principles."]},"context":{"applicability":"required","items":["Rights, privacy, contracting, pricing, access, retention and publication authority depend on jurisdiction and organization.","DCAT-AP is a European profile; DPROD is beta; ODPS, Schema.org, DataCite, FAIR, DPV and OpenAPI are scoped profiles, not universal operating law."]}},"sources":[{"title":"Data Catalog Vocabulary DCAT Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"World Wide Web Consortium"},{"title":"DCAT Application Profile for data portals in Europe","url":"https://semiceu.github.io/DCAT-AP/releases/3.0.1/","note":"European Commission SEMIC"},{"title":"Data on the Web Best Practices","url":"https://www.w3.org/TR/dwbp/","note":"World Wide Web Consortium"},{"title":"PROV-O The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data on the Web Best Practices Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"Data Privacy Vocabulary","url":"https://www.w3.org/community/reports/dpvcg/CG-FINAL-dpv-20240801/","note":"World Wide Web Consortium Data Privacy Vocabularies and Controls Community Group"},{"title":"Data Product Ontology","url":"https://www.omg.org/spec/DPROD/1.0/Beta1/PDF","note":"Object Management Group"},{"title":"Open Data Product Specification","url":"https://opendataproducts.org/v4.1/","note":"Linux Foundation"},{"title":"Dataset","url":"https://schema.org/Dataset","note":"Schema.org"},{"title":"DataCite Metadata Schema Documentation for the Publication and Citation of Research Data and Other Research Outputs","url":"https://schema.datacite.org/meta/kernel-4.6/","note":"DataCite"},{"title":"NIST Research Data Framework Version 2.0","url":"https://nvlpubs.nist.gov/nistpubs/SpecialPublications/1500-18/NIST.SP.1500-18r2.html","note":"National Institute of Standards and Technology"},{"title":"FAIR Guiding Principles for scientific data management and stewardship","url":"https://doi.org/10.1038/sdata.2016.18","note":"Scientific Data"},{"title":"Time Ontology in OWL","url":"https://www.w3.org/TR/owl-time/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet Timestamps","url":"https://www.rfc-editor.org/info/rfc3339","note":"Internet Engineering Task Force"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-dat-008-data-catalog-entry-data-product/spec.yaml","agents":"/models/wm-dat-008-data-catalog-entry-data-product/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-dat-008-data-catalog-entry-data-product"},"provenance":{"origin":"world-models research","builtFrom":["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"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T13:15:24Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}