<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml_AI_Highlight.xsl"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Name>Data Provenance Standards for Trustworthy AI and Data Ecosystems</Name>
  <Description>The OASIS Data Provenance Standards Technical Committee advances cross-industry standards for data provenance, lineage, pedigree, and metadata tagging to ensure transparency, accountability, and trust in AI-driven and data-dependent applications.</Description>
  <OtherInformation>This plan was derived and rendered in StratML format by Claude.ai based upon the public charter, homepage, and founding statements of the OASIS Data Provenance Standards Technical Committee (DPS TC), whose founding sponsors include Cisco, IBM, Intel, Microsoft, and Red Hat. The TC was formally launched on April 8, 2025, building on the Data &amp; Trust Alliance&apos;s Data Provenance Standards v1.0.0. 
^^ Submitter&apos;s Note: It has been lightly edited in the form at https://stratml.us/forms/Claude/Part1.html</OtherInformation>
  <StrategicPlanCore>
    <Organization>
      <Name>OASIS Data Provenance Standards Technical Committee</Name>
      <Acronym>DPSTC</Acronym>
      <Identifier>2e0ab93c-3743-4840-9c70-b019f2e23bf8</Identifier>
      <Description>An OASIS Technical Committee co-chaired by Cisco and IBM, with founding sponsors including Intel, Microsoft, and Red Hat, building on the Data &amp; Trust Alliance&apos;s Data Provenance Standards v1.0.0 to create de jure cross-industry standards for data transparency, accountability, and trust.</Description>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Cisco</Name>
        <Description>Co-Chair</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>IBM</Name>
        <Description>Co-Chair</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Intel</Name>
        <Description>Founding Sponsor</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Microsoft</Name>
        <Description>Founding Sponsor</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Red Hat</Name>
        <Description>Founding Sponsor</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Person">
        <Name>Lisa Bobbitt</Name>
        <Description>TC Co-Chair (Cisco)</Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Person">
        <Name>Bryan Bortnick</Name>
        <Description>TC Co-Chair (IBM)</Description>
      </Stakeholder>
    </Organization>
    <Vision>
      <Description>A world in which every data asset — across all industries — carries standardized, machine-readable provenance metadata that makes its origin, lineage, rights, and restrictions transparent to all who rely on it, enabling trustworthy AI and data-dependent systems at global scale.</Description>
      <Identifier>6200585a-7006-4f32-a4e7-28a8a13c6afa</Identifier>
    </Vision>
    <Mission>
      <Description>To develop and advance actionable cross-industry standards for data provenance — covering tagging and metadata frameworks at the database, table, column, graph, NoSQL, and API levels — that deliver measurable business value, enhance data lifecycle management, and reinforce trust in AI-driven applications.</Description>
      <Identifier>071dfd52-fefe-43ff-b602-1dedd331175c</Identifier>
    </Mission>
    <Value>
      <Name>Transparency</Name>
      <Description>Full visibility into where data comes from, how it is created, and whether it can be used legally is the foundation of trustworthy AI and data-dependent systems.</Description>
    </Value>
    <Value>
      <Name>Accountability</Name>
      <Description>Data provenance standards create auditable records that hold data suppliers, acquirers, and consumers accountable for data quality, rights, and restrictions throughout the data lifecycle.</Description>
    </Value>
    <Value>
      <Name>Openness</Name>
      <Description>Standards developed through an open, consensus-based process — available to all industries and stakeholders — are more durable, equitable, and widely adopted than proprietary or siloed approaches.</Description>
    </Value>
    <Value>
      <Name>Interoperability</Name>
      <Description>Common provenance vocabularies and metadata schemas enable seamless data exchange across organizations, industries, and jurisdictions without proprietary lock-in.</Description>
    </Value>
    <Goal>
      <Name>Provenance</Name>
      <Description>Develop and publish cross-industry technical standards for data provenance, lineage, pedigree, and metadata tagging that establish a universal data governance norm applicable across all industries and data structures.</Description>
      <Identifier>da44ca7d-771d-47d5-8753-da1cd219e7c8</Identifier>
      <SequenceIndicator>1</SequenceIndicator>
      <Objective>
        <Name>Tagging</Name>
        <Description>Specify consistent metadata tagging frameworks covering database, table, column, graph database, NoSQL database, and API data structures to enable comprehensive data lineage tracking at every level of the data ecosystem.</Description>
        <Identifier>8e43a0b1-d589-4ad2-a03a-b9cce59a052e</Identifier>
        <SequenceIndicator>1.1</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Rights &amp; Restrictions</Name>
        <Description>Define standardized descriptors for data rights, restrictions, sourcing, and permissible use that allow data suppliers to communicate and data acquirers to enforce compliance with privacy, intellectual property, and regulatory obligations.</Description>
        <Identifier>cf4bc245-ff35-430e-9ed9-e2dfe997d1d7</Identifier>
        <SequenceIndicator>1.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Vocabulary</Name>
        <Description>Establish a shared provenance vocabulary — encompassing provenance, lineage, pedigree, trust, rights, and restrictions — that bridges existing complementary efforts such as C2PA (image provenance) and OpenSSF AIBOM (software supply chain security) without duplicating them.</Description>
        <Identifier>836862b3-36f4-49d7-a13e-db72161744cc</Identifier>
        <SequenceIndicator>1.3</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>AI Trust</Name>
      <Description>Reinforce trust in AI-driven systems by ensuring that the data used to train and operate AI models carries transparent, auditable provenance metadata that supports responsible AI development and deployment.</Description>
      <Identifier>e27c3ffb-dd3e-4217-b804-356ddd21e339</Identifier>
      <SequenceIndicator>2</SequenceIndicator>
      <Objective>
        <Name>Governance</Name>
        <Description>Enable AI ethics specialists, data governance professionals, and compliance officers to integrate DPS standards into AI model development pipelines, ensuring data used in AI systems is traceable to its origin with documented rights and restrictions.</Description>
        <Identifier>8e085518-ddac-4714-846f-6a6bc07bba69</Identifier>
        <SequenceIndicator>2.1</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Validation</Name>
        <Description>Explore and specify opportunities for automated tools to generate and validate provenance metadata at scale, ensuring standards are adoptable without prohibitive manual overhead and are compatible with modern data pipeline tooling.</Description>
        <Identifier>448aed78-7426-4747-9a1d-0a8e51527362</Identifier>
        <SequenceIndicator>2.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Reasoning</Name>
        <Description>Extend provenance concepts from data infrastructure into the AI reasoning layer, addressing questions of what authorized an agent action, what data was accessed under what grants, and whether agent decision chains are traceable after the fact.</Description>
        <Identifier>e1fb94a6-5102-4545-a943-8eb630e0b743</Identifier>
        <SequenceIndicator>2.3</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>Adoption &amp; Value</Name>
      <Description>Drive industry-wide adoption of data provenance standards by demonstrating clear return on investment for data providers and consumers, reducing the costs of low-quality data, regulatory non-compliance, and trust deficits in AI-driven applications.</Description>
      <Identifier>041edfba-ddf0-41d6-aee6-a4ad6d7b6814</Identifier>
      <SequenceIndicator>3</SequenceIndicator>
      <Objective>
        <Name>Business Case</Name>
        <Description>Document and communicate the measurable business value of provenance standards, including reductions in data cleanup costs, overpayment for low-quality data, regulatory risk exposure, and audit remediation effort.</Description>
        <Identifier>825f926a-4739-4203-8b1e-fb81934871ce</Identifier>
        <SequenceIndicator>3.1</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Engagement</Name>
        <Description>Expand TC membership and participation across diverse industries and geographies, ensuring that standards reflect the full range of data ecosystems and earn legitimacy as de jure global norms through OASIS&apos;s open consensus process.</Description>
        <Identifier>bb3bf73c-f814-422c-ac7d-b4c0a45a0908</Identifier>
        <SequenceIndicator>3.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Guidance</Name>
        <Description>Bridge the gap between standards specification and practical implementation by developing reference implementations, conformance tests, and implementation guides that reduce the barrier to adoption for organizations of all sizes.</Description>
        <Identifier>d890f032-94ed-48da-8179-ae129d4a8787</Identifier>
        <SequenceIndicator>3.3</SequenceIndicator>
      </Objective>
    </Goal>
  </StrategicPlanCore>
  <AdministrativeInformation>
    <StartDate>2025-04-08</StartDate>
    <PublicationDate>2026-06-08</PublicationDate>
    <Source>https://www.oasis-open.org/tc-dps/</Source>
    <Submitter>
      <GivenName>Owen</GivenName>
      <Surname>Ambur</Surname>
      <EmailAddress>Owen.Ambur@verizon.net</EmailAddress>
    </Submitter>
  </AdministrativeInformation>
</StrategicPlan>