1. Introduction

The HDIP© Product Descriptor (HPD) is a platform-level artifact that enriches canonical Data Product specifications (DPROD) with classification, lineage, governance, and usage intelligence required for Holistic Data & Information Platform (HDIP) operation.

HPD enables:

Intelligent orchestration (DPFI)
Product discovery & experience (CEP)
DPFI (Data Product Factory Intelligence)
CEP (Consumer Experience Plane)
COVP (Consumer Observability & Value Plane)
Graph-based querying, reasoning, and analysis capabilities

2. Positioning in HDIP

HPD is not a replacement for DPROD or DPDS.

It exists as a separate, additive layer:

DPROD → Semantic Truth (WHAT)
DPDS  → Deployment Blueprint (HOW)
HPD   → Intelligence Layer (CONTEXT + USAGE + CLASSIFICATION)

3. Design Principles

3.1 Non-invasive

HPD does not modify or extend DPROD or DPDS.

3.2 Referential

All relationships are expressed via URI-based references.

3.3 Ontology-driven

HPD aligns with RDF/OWL and JSON-LD.

3.4 Computable

Machine-readable for:

Intelligent orchestration (DPFI)
Product discovery & experience (CEP)
DPFI (Data Product Factory Intelligence)
CEP (Consumer Experience Plane)
COVP (Consumer Observability & Value Plane)
Graph-based querying, reasoning, and analysis capabilities

3.5 Projection-ready

Supports multiple views (UI, APIs, Graphs).

4. Referencing Contract Alignment

HPD follows the HDIP Referencing Contract:

All entities are resources (IRIs)
No string-based classification
External ontologies are allowed (domain, org, etc.)
Relationships are explicit (object properties)

5. Core Structure

Conceptually:

HPD =
identity +
references +
classification +
lineage +
context +
governance +
usage +
observability +
lifecycle

6. Ontology Alignment (TTL)

Below is the minimal ontology alignment for HPD.

@prefix dp: <https://kivanura.org/spec/dp#> .
@prefix hpd: <https://kivanura.org/spec/hdip/hpd#> .
@prefix dprod: <https://example.org/ikgf/dprod#> .
@prefix org: <https://kivanura.org/spec/org#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

##################################################
# Core Classes
##################################################

dp:DataProduct a owl:Class .

##################################################
# HPD Properties
##################################################

hpd:hasProductType a owl:ObjectProperty ;
    rdfs:domain dp:DataProduct ;
    rdfs:range dp:ProductType .

hpd:ownedBy a owl:ObjectProperty ;
    rdfs:domain dp:DataProduct ;
    rdfs:range rdfs:Resource .

hpd:providedBy a owl:ObjectProperty ;
    rdfs:domain dp:DataProduct ;
    rdfs:range rdfs:Resource .

hpd:basedOn a owl:ObjectProperty ;
    rdfs:domain dp:DataProduct ;
    rdfs:range dp:DataProduct .

hpd:hasSyntheticContext a owl:ObjectProperty ;
    rdfs:domain dp:DataProduct ;
    rdfs:range rdfs:Resource .

7. JSON-LD Context

Canonical context:

{
  "@context": {
    "dp": "https://kivanura.org/spec/dp#",
    "hpd": "https://kivanura.org/spec/hdip/hpd#",
    "synctx": "https://kivanura.org/spec/hdip/synctx#",
    "dprod": "https://example.org/ikgf/dprod#",
    "org": "https://kivanura.org/spec/org#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",

    "id": "@id",
    "type": "@type",

    "label": "rdfs:label",

    "productType": {
      "@id": "hpd:hasProductType",
      "@type": "@id"
    },

    "domain": {
      "@id": "dprod:domain",
      "@type": "@id"
    },

    "ownedBy": {
      "@id": "hpd:ownedBy",
      "@type": "@id"
    },

    "providedBy": {
      "@id": "hpd:providedBy",
      "@type": "@id"
    },

    "basedOn": {
      "@id": "hpd:basedOn",
      "@type": "@id"
    },

    "syntheticContext": {
      "@id": "hpd:hasSyntheticContext",
      "@type": "@id"
    }
  }
}

8. Example HPD (JSON-LD Instance)

{
  "@context": "https://kivanura.org/context/hdip.jsonld",

  "id": "https://kivanura.org/data/hpd/SynthPaymentProduct",
  "type": "dp:DataProduct",

  "label": "Synthetic Payment Data Product",

  "domain": "https://example.org/domain/Payments",

  "productType": "dp:SyntheticDataProduct",

  "ownedBy": "https://example.org/org/PaymentsUBR",

  "providedBy": "https://example.org/org/AIEngineering",

  "basedOn": [
    "https://kivanura.org/data/dp/PaymentDataProduct",
    "https://kivanura.org/data/dp/PartyDataProduct"
  ],

  "syntheticContext": "https://kivanura.org/data/synctx/SYNCTX-AI-TRAINING-001"
}

9. PDEP Lifecycle Integration

9.1 Creation Stage

HPD is NOT authored by DPRO.

It is generated by the platform at:

👉 Stage 8 — Platform Compilation Pack

Intent → Semantics → Governance → Usage → Validation
                ↓
      Stage 8: Compilation Pack
                ↓
           HPD generated

9.2 Inputs to HPD Generation

HPD is derived from:

Intent Record
Semantic Descriptor (DPROD)
Governance Policies
Usage Contract
SYNCTX (if applicable)

9.3 Output Role

HPD becomes:

Control-plane artifact for DPFI
Discovery layer for CEP
Queryable graph node for:
- product discovery
- dependency analysis
- impact assessment
- governance and policy evaluation

10. Relationship to Other Artifacts

Artifact	Role
DPROD	Semantic contract
DPDS	Deployment
SYNCTX	Relational boundary
DPP	Trust
HPD	Intelligence layer

11. Key Rules

Rule 1 — Separation of Concerns

HPD MUST NOT redefine DPROD or DPDS.

Rule 2 — Referential Integrity

All references MUST be URIs.

Rule 3 — Product Type

Each HPD MUST have exactly one productType.

Rule 4 — Synthetic Dependency

If productType = Synthetic → syntheticContext MUST exist.

Rule 5 — Domain Flexibility

HPD uses dprod:domain without constraining its ontology.

12. Storage & Runtime

HPD SHOULD be stored in:

Graph DB (preferred)
JSON store (acceptable)
Git (for versioning)

13. Summary

DPROD → defines meaning
DPDS → defines execution
SYNCTX → defines relational boundary
HPD → defines intelligence, classification, and usage

14. Final Insight

HPD is the HDIP Control Plane Representation of a Data Product. It is first-class node in the HDIP Product Knowledge Graph

It enables HDIP to move from:

static metadata

to:

computable, queryable product intelligence

2. Positioning in HDIP

3. Design Principles

3.1 Non-invasive​

3.2 Referential​

3.3 Ontology-driven​

3.4 Computable​

3.5 Projection-ready​