W3C PROV-O: The PROV Ontology
The registry entry for PROV-O, with the body’s development process, the clause map, the crosswalk, adoption, participation channels, tools and updates. Artefacts that apply it carry a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-3, NS-3b, NS-11.
- Open standards: PROV-O: The PROV Ontology; in-toto Attestation Framework; Verifiable Credentials Data Model v2.0; RFC 9162 Certificate Transparency Version 2.0 (log structure); C2PA Technical Specification.
- Data and feeds: Software Heritage archive API; Rekor public transparency log.
- Couples with: Verified intelligence and transparency; Data and datasets; Decision records and accountability.
Summary
- VersionW3C Recommendation 30 April 2013
- Year2013
- Accessopen
- Relationadopt
- Verifiedyes: name, body, version and year confirmed at the source
- DomainProvenance and evidence
- Updateslisted for reference
The relation is shown as recorded in the registry.
- Operations
- 8
- in the W3C track
- Clause map
- 5
- parts, numbers and titles
- Siblings
- 5
- entries in provenance and evidence
- Data sources
- 3
- listed for reference
How W3C develops a standard such as PROV-O
The stages of the body’s own process document, step by step: the actor, the decision rule and the record each operation leaves. W3C Process Document (2025)
Process explorer · NXS · Process
W3C Recommendation track
8 steps·3 stages·2 gates
NXS · Process
W3C Recommendation track
Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.
A reviewed charter leads to working drafts, a Candidate Recommendation with implementation experience, Advisory Committee review, and a maintained Recommendation.
01 Advisory Committee
- 01CharterDecision · the Advisory Committee, on a W3C proposalMembers review the charter; the group is chartered with its deliverables and the patent policy terms.
- 06AC reviewGate · the Advisory CommitteeMembers review the Proposed Recommendation and may formally object.
02 Working group
- 02FPWDRecord · working groupThe first public draft on the technical-report page; wide review begins.
- 03Working DraftsStep · working group editorsDrafts iterate in the open; the group records issues and their resolution.
- 04Candidate RecommendationGate · working group, with the Director’s or Team’s decisionCandidate Recommendation gathers implementation experience; test suites and reports are published.
03 W3C decision
- 05Proposed RecommendationStep · W3CThe document is sent to the Advisory Committee with the implementation report.
- 07RecommendationOutcome · W3CA W3C Recommendation; patent commitments apply under the Patent Policy.
- 08MaintenanceRecord · working group or maintenance groupRecommendations are maintained; errata and amendments are recorded on the technical-report page.
W3C Process Document · W3C Patent PolicyAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Advisory Committee | Charter (decision). Members review the charter; the group is chartered with its deliverables and the patent policy terms. | the Advisory Committee, on a W3C proposal | Advisory Committee review of scope, deliverables and patent policy | a chartered working group |
| 02 | Werkgroep | FPWD (record). The first public draft on the technical-report page; wide review begins. | working group | publication starts the patent exclusion period | First Public Working Draft |
| 03 | Werkgroep | Working Drafts (step). Drafts iterate in the open; the group records issues and their resolution. | working group editors | consensus of the group; horizontal review (accessibility, internationalisation, privacy, security) | successive drafts with change logs |
| 04 | Werkgroep | Candidate Recommendation (gate). Candidate Recommendation gathers implementation experience; test suites and reports are published. | working group, with the Director’s or Team’s decision | implementation experience and wide review before advancing | a CR snapshot and an implementation report |
| 05 | W3C decision | Proposed Recommendation (step). The document is sent to the Advisory Committee with the implementation report. | W3C | the group shows it met the CR exit criteria | a PR for Advisory Committee review |
| 06 | Advisory Committee | AC review (gate). Members review the Proposed Recommendation and may formally object. | the Advisory Committee | formal objections handled under the Process | review responses |
| 07 | W3C decision | Recommendation (end). A W3C Recommendation; patent commitments apply under the Patent Policy. | W3C | a W3C decision after Advisory Committee review | the Recommendation |
| 08 | W3C decision | Maintenance (record). Recommendations are maintained; errata and amendments are recorded on the technical-report page. | working group or maintenance group | candidate amendments and errata under the Process | errata, amendments, new editions |
Table.The Advisory Committee reviews a charter; the working group publishes a First Public Working Draft and further drafts; Candidate Recommendation gathers implementation experience; Proposed Recommendation goes to Advisory Committee review; the W3C decision publishes the Recommendation, which is then maintained. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: W3C Process Document · W3C Patent Policy.
Public structure of the document
Part numbers and titles, linked to the body’s own document; the machine-readable artefact published by the body is linked at the source.
- Parts5
- Named sub-parts6
- Machine artefactPROV-O ontology (OWL)
- Text reproducednone
Numbers and titles only; every part opens the body’s own document.
Obligations that a Nexus Standard adopts or profiles are written as Nexus clauses (NS-10) citing the source by identifier and clause number (NS-14).
PROV-O among the standards of provenance and evidence
The registry relation is adopt: The Nexus Standards use the external standard as it is for a function. Evidence: Validation of values against the external scheme.
The crosswalk as a table: 29 external standards by domain
| Domain | External standard | Issuing body | Relation |
|---|---|---|---|
| Data and datasets | CARE Principles for Indigenous Data Governance | Global Indigenous Data Alliance | adopt |
| Data and datasets | Croissant: A Metadata Format for ML-Ready Datasets | MLCommons Croissant Working Group | crosswalk |
| Data and datasets | Datasheets for Datasets | Gebru et al. (arXiv 2018; Communications of the ACM 2021) | profile |
| Data and datasets | ESCO European Skills, Competences, Qualifications and… | European Commission | crosswalk |
| Data and datasets | FAIR Guiding Principles for scientific data management and… | Wilkinson et al. 2016; GO FAIR | adopt |
| Data and datasets | Global indicator framework for the Sustainable Development… | UN Statistical Commission | crosswalk |
| Data and datasets | Handbook on Constructing Composite Indicators (OECD and… | OECD and European Commission JRC | adopt |
| Data and datasets | IEEE 1451 Smart transducer interface standards | IEEE | cite |
| Data and datasets | ISO 22739 Blockchain and distributed ledger technologies… | ISO/TC 307 | cite |
| Data and datasets | ISO 23247 Automation systems and integration – Digital… | ISO/TC 184 | cite |
| Data and datasets | ISO 8601-1:2019 Date and time – Representations for… | ISO/TC 154 | adopt |
| Data and datasets | ISO/IEC 22123 Information technology – Cloud computing | ISO/IEC JTC 1/SC 38 | cite |
| Data and datasets | ISO/IEC 30173:2023 Digital twin – Concepts and terminology | ISO/IEC JTC 1/SC 41 | crosswalk |
| Data and datasets | JSON-LD 1.1 | W3C | adopt |
| Data and datasets | OWL 2 Web Ontology Language | W3C | adopt |
| Data and datasets | Schema.org vocabulary | Schema.org Community Group (W3C) | adopt |
| Data and datasets | Semantic Sensor Network Ontology (SOSA/SSN) | W3C and OGC | adopt |
| Data and datasets | Shapes Constraint Language (SHACL) | W3C | adopt |
| Data and datasets | SKOS Simple Knowledge Organization System Reference | W3C | adopt |
| Data and datasets | SPARQL 1.1 Query Language | W3C | adopt |
| Data and datasets | Statistical Data and Metadata eXchange (SDMX); ISO… | SDMX sponsors (BIS, ECB, Eurostat, IMF, OECD, UN, World Bank); ISO/TC 154 | crosswalk |
| Data and datasets | Time Ontology in OWL | W3C and OGC | adopt |
| Data and datasets | W3C Data Catalog Vocabulary (DCAT) – Version 3 | W3C Dataset Exchange Working Group | adopt |
| Provenance and evidence | C2PA Content Credentials specification | Coalition for Content Provenance and Authenticity (Joint Development Foundation) | adopt |
| Provenance and evidence | IETF SCITT architecture (Supply Chain Integrity… | IETF SCITT working group | profile |
| Provenance and evidence | in-toto Attestation Framework | in-toto project (CNCF) | adopt |
| Provenance and evidence | Sigstore (Cosign, Fulcio, Rekor) | OpenSSF (Linux Foundation); graduated project March 2024 | adopt |
| Provenance and evidence | W3C PROV-O: The PROV Ontology | W3C Provenance Working Group | adopt |
| Provenance and evidence | W3C Verifiable Credentials Data Model v2.0 | W3C Verifiable Credentials Working Group | crosswalk |
Nexus Standards in the graph: NS-3b, NS-11. A relation is a register entry, never a compliance claim.
2 Nexus Standards · 2 domains · 29 external standards · 24 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.
Crosswalk graph57 nodes and 62 links: this standard, the entries in the area’s principal domains, their bodies, the Nexus Standards the area lists and their implementers. Relations are shown as recorded in the registry.
Implementations, listed as submitted
Implementations and validators in alphabetical order; the implementers of the area’s Nexus Standards with their implementation status; and the entries of the open-standards stack that name this standard. Listings are not a ranking.
| Implementering | By | Wat dit is |
|---|---|---|
| prov (Python) | Trung Dong Huynh and contributors | PROV data model library with PROV-O serialisation |
| PROV implementation report | W3C Provenance Working Group | implementations reported at the time the Recommendation was published |
| ProvToolbox | Luc Moreau and contributors | Java toolbox for PROV, including PROV-O |
| Test suite or validator | What it checks |
|---|---|
| PROV-CONSTRAINTS validators listed in the implementation report | validators recorded by the working group |
| Stack entry | Rol | Export |
|---|---|---|
| W3C PROV-O | provenance graph (derivations, corrections) | prov Bundle (NS-3b section 3; relatedIdentifiers to PROV predicates, record refs to prov:specializationOf and prov:wasRevisionOf) |
NoteThe outline, participation channels, implementations, test suites, schema and data feeds on this page were compiled from the body’s public pages on 16 October 2026; all other information is taken from the registry entry.
Participation in PROV-O
The participation channels of the body and the requirements of each, followed by the general path from a comment at the body to a registry change in the Nexus Standards.
| Channel | Wat dit is | What it requires | Link |
|---|---|---|---|
| Comment list | public-prov-comments archive: comments on the PROV documents | an email address; the archive is public | Open the comment list page |
| Errata | errata of the PROV family of documents | errata are reported through the comment list | Open the errata page |
| Process document | W3C Process Document (registry entry w3c-process-2025) | to be read before participating | Open the process document page |
| Community groups | W3C Community Groups: open to anyone with a W3C account | a W3C account and the community contributor agreement | Open the community groups page |
Process explorer · NXS · Process
Contributing through a standards body
11 steps·3 stages·1 gate
NXS · Process
Contributing through a standards body
A contributor joins a body’s channel under its rules, files issues, reviews, proposes and tests, and Nexus Standards cites the outcome through a change proposal.
01 Contributor
- 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
- 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
- 06Propose textStep · the contributor, in the body’s channelWording goes to the body’s own channel. In Nexus Standards, the obligation becomes a clause (NS-10) citing the source clause.
- 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
02 The standards body
- 03Join a channelStep · the body’s working group or committeeMailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.
- 04File an issueRecord · the contributor, in the body’s trackerAn erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.
- 05Public reviewGate · the body, under its processPublic reviews and last calls are the body’s own stages. The monitoring console shows their dates once the body’s feed exists.
- 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
03 Nexus Standards
- 09Cite the outcomeStep · Nexus Standards editorsThe outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.
- 10Change proposalRecord · any person, with identity recordedA change proposal is a change request to the canonical repository, with a public proposal record. Editors decide with reasons.
- 11Register changeOutcome · editors, with reasons on recordThe register entry is amended and the package page is regenerated from it.
OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claimsAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Contributor | Identify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document. | the contributor | the register names the body and links to its own page | the body’s page, linked from the package |
| 02 | Contributor | Read IPR and participation rules (step). Participation rules differ: an IETF working group requires no membership; an OASIS technical committee requires membership; W3C groups have community and member forms. | the contributor | membership, patent policy and contributor agreements are set by the body and read at the source | the requirements of the channel |
| 03 | The standards body | Join a channel (step). Mailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires. | the body’s working group or committee | the channel belongs to the body and follows its process document | a list subscription, an issue account, a membership |
| 04 | The standards body | File an issue (record). An erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link. | the contributor, in the body’s tracker | an issue is the body’s record, cited by URL | an issue with a stable link |
| 05 | The standards body | Public review (gate). Public reviews and last calls are the body’s own stages. The monitoring console shows their opening and closing dates once the body’s feed is available. | the body, under its process | the body decides under its own rules; the Nexus Standards record the public outcome | comment dispositions by the body |
| 06 | Contributor | Propose text (step). Wording is submitted to the body’s own channel. In the Nexus Standards, the same obligation is expressed as a clause (NS-10) that cites the source by clause number. | the contributor, in the body’s channel | text is proposed through the body’s own channel; the body’s text remains with the body | a change request, an Internet-Draft or a comment with wording |
| 07 | Contributor | Implement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one. | the contributor | a passing run is evidence of implementation | a test run with the suite version and time |
| 08 | The standards body | Implementation report (record). Implementations are listed as submitted, in alphabetical order. | the body or the working group | listed as the body publishes it, without ranking | the report, linked |
| 09 | Nexus Standards | Cite the outcome (step). The outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source. | Nexus Standards editors | cited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalence | a crosswalk entry or a clause citing the source |
| 10 | Nexus Standards | Change proposal (record). A change proposal is a change request to the canonical repository, with a proposal record in the public change record. Editors decide with written reasons. | any person, with identity recorded | every change is submitted as a change proposal under NS-13 | a change proposal with a UNI |
| 11 | Nexus Standards | Register change (end). The register entry is amended and the package page is regenerated from it. | editors, with reasons on record | accepted, rejected or withdrawn in writing; the history is retained | the amended register entry and its history |
Table.A contributor identifies the standards body, reads its participation and intellectual property rules, joins a channel, files an issue, takes part in the public review, proposes text, and implements and tests; the body publishes the implementation report. The Nexus Standards cite the outcome through a change proposal that becomes a register correction, a crosswalk entry or a clause. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claims.
Tools and their availability
Run the test suite in the browser
A browser-based test run on worked examples is in progress. In the meantime, PROV-CONSTRAINTS validators listed in the implementation report, published by the body, can be run at the source.
AvailableOpen the schema
PROV-O ontology (OWL), at the body’s own address.
Available · composed in the browserDownload the profile
The composer opens with this standard and the area’s Nexus Standards selected, and produces YAML or JSON with citations and the licence line.
PlannedOpen in an integrated application
An integration point on this page is reserved for compatible applications and is not yet active.
A passing test run constitutes implementation evidence.
Latest releases from the body
Data sources are listed for reference; live data is displayed once licence review is complete. The latest version of the standard recorded in the registry is W3C Recommendation 30 April 2013 (2013). Latest at W3C Provenance Working Group.
After licence review, data are delivered, in order of preference, through the governed data service, the site integration, a direct browser read of an open endpoint, or a build-time snapshot with its timestamp; the age of the data is always shown. Monitoring console: worked example.
| Data source | Registry | Format | Browser read | Delivery | Cadence |
|---|---|---|---|---|---|
w3c.tr.feed | data-sources | rdf | unknown | governed data service, build-time snapshot | daily |
w3c.news.feed | data-sources | rss | unknown | governed data service, build-time snapshot | daily |
w3c.prov.comments.archive | data-sources | html | unknown | build-time snapshot | weekly |
3 data sources listed.
Questions and answers.
Do the standards reproduce PROV-O?
Where do the updates come from?
Is the relation a conformance statement?
Around provenance and evidence.
Building on PROV-O
Relations to this standard are recorded in the registry. Changes are submitted as proposals under NS-13 and may be prepared through the working groups and the National Working Groups of participating countries.
Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.
Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.