Skip to content
StandardsProvenance and evidenceOpen standard package
PROV-O · adopt

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).

Provenance and evidence
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.Source: the Nexus Standards registry: the area record.
  • 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.
01అవలోకనం

Summary

Registry entrythe external standards register · w3c-prov-o
  1. VersionW3C Recommendation 30 April 2013
  2. సంవత్సరం2013
  3. ప్రాప్యతతెరిచి ఉంది
  4. Relationadopt
  5. Verifiedyes: name, body, version and year confirmed at the source
  6. DomainProvenance and evidence
  7. 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
02ప్రక్రియ

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 steps3 stages2 gates

NXS · Process

W3C Recommendation track

ప్రమాణ జీవిత చక్రం · NS-13 ట్రాక్ · సహకార మార్గాలు · IETF ట్రాక్ · W3C ట్రాక్ · OGC ట్రాక్ · OASIS ట్రాక్ · ISO మరియు IEC దశలు · అనుగుణత · రికార్డు జీవిత చక్రం · మళ్లింపు · పర్యవేక్షణ.

A reviewed charter leads to working drafts, a Candidate Recommendation with implementation experience, Advisory Committee review, and a maintained Recommendation.

  1. 01 Advisory Committee

    1. 01CharterDecision · the Advisory Committee, on a W3C proposalMembers review the charter; the group is chartered with its deliverables and the patent policy terms.
    2. 06AC reviewGate · the Advisory CommitteeMembers review the Proposed Recommendation and may formally object.
  2. 02 Working group

    1. 02FPWDRecord · working groupThe first public draft on the technical-report page; wide review begins.
    2. 03Working DraftsStep · working group editorsDrafts iterate in the open; the group records issues and their resolution.
    3. 04Candidate RecommendationGate · working group, with the Director’s or Team’s decisionCandidate Recommendation gathers implementation experience; test suites and reports are published.
  3. 03 W3C decision

    1. 05Proposed RecommendationStep · W3CThe document is sent to the Advisory Committee with the implementation report.
    2. 07RecommendationOutcome · W3CA W3C Recommendation; patent commitments apply under the Patent Policy.
    3. 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
Process · W3C track8 operations
దశPhaseకార్యకలాపంWhoDecision ruleరికార్డు
01Advisory CommitteeCharter (decision). Members review the charter; the group is chartered with its deliverables and the patent policy terms.the Advisory Committee, on a W3C proposalAdvisory Committee review of scope, deliverables and patent policya chartered working group
02కార్యనిర్వాహక బృందంFPWD (record). The first public draft on the technical-report page; wide review begins.working grouppublication starts the patent exclusion periodFirst Public Working Draft
03కార్యనిర్వాహక బృందంWorking Drafts (step). Drafts iterate in the open; the group records issues and their resolution.working group editorsconsensus of the group; horizontal review (accessibility, internationalisation, privacy, security)successive drafts with change logs
04కార్యనిర్వాహక బృందంCandidate Recommendation (gate). Candidate Recommendation gathers implementation experience; test suites and reports are published.working group, with the Director’s or Team’s decisionimplementation experience and wide review before advancinga CR snapshot and an implementation report
05W3C decisionProposed Recommendation (step). The document is sent to the Advisory Committee with the implementation report.W3Cthe group shows it met the CR exit criteriaa PR for Advisory Committee review
06Advisory CommitteeAC review (gate). Members review the Proposed Recommendation and may formally object.the Advisory Committeeformal objections handled under the Processreview responses
07W3C decisionRecommendation (end). A W3C Recommendation; patent commitments apply under the Patent Policy.W3Ca W3C decision after Advisory Committee reviewthe Recommendation
08W3C decisionMaintenance (record). Recommendations are maintained; errata and amendments are recorded on the technical-report page.working group or maintenance groupcandidate amendments and errata under the Processerrata, 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.

Compare with the Nexus track and other standards bodies.

03Clause map

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.

Clause map · the document’s public structure, navigableFrom the registry
Clause map5 parts
  1. Parts5
  2. Named sub-parts6
  3. Machine artefactPROV-O ontology (OWL)
  4. 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).

04క్రాస్‌వాక్

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.

Crosswalk graph · provenance and evidence, around this standardNexus Standards registry
W3C PROV-O: The PROV Ontology: crosswalk57 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 62 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 29 external standards by domain
డొమైన్External standardIssuing bodyRelation
Data and datasetsCARE Principles for Indigenous Data GovernanceGlobal Indigenous Data Allianceadopt
Data and datasetsCroissant: A Metadata Format for ML-Ready DatasetsMLCommons Croissant Working Groupcrosswalk
Data and datasetsDatasheets for DatasetsGebru et al. (arXiv 2018; Communications of the ACM 2021)profile
Data and datasetsESCO European Skills, Competences, Qualifications and…European Commissioncrosswalk
Data and datasetsFAIR Guiding Principles for scientific data management and…Wilkinson et al. 2016; GO FAIRadopt
Data and datasetsGlobal indicator framework for the Sustainable Development…UN Statistical Commissioncrosswalk
Data and datasetsHandbook on Constructing Composite Indicators (OECD and…OECD and European Commission JRCadopt
Data and datasetsIEEE 1451 Smart transducer interface standardsIEEEcite
Data and datasetsISO 22739 Blockchain and distributed ledger technologies…ISO/TC 307cite
Data and datasetsISO 23247 Automation systems and integration – Digital…ISO/TC 184cite
Data and datasetsISO 8601-1:2019 Date and time – Representations for…ISO/TC 154adopt
Data and datasetsISO/IEC 22123 Information technology – Cloud computingISO/IEC JTC 1/SC 38cite
Data and datasetsISO/IEC 30173:2023 Digital twin – Concepts and terminologyISO/IEC JTC 1/SC 41crosswalk
Data and datasetsJSON-LD 1.1W3Cadopt
Data and datasetsOWL 2 Web Ontology LanguageW3Cadopt
Data and datasetsSchema.org vocabularySchema.org Community Group (W3C)adopt
Data and datasetsSemantic Sensor Network Ontology (SOSA/SSN)W3C and OGCadopt
Data and datasetsShapes Constraint Language (SHACL)W3Cadopt
Data and datasetsSKOS Simple Knowledge Organization System ReferenceW3Cadopt
Data and datasetsSPARQL 1.1 Query LanguageW3Cadopt
Data and datasetsStatistical Data and Metadata eXchange (SDMX); ISO…SDMX sponsors (BIS, ECB, Eurostat, IMF, OECD, UN, World Bank); ISO/TC 154crosswalk
Data and datasetsTime Ontology in OWLW3C and OGCadopt
Data and datasetsW3C Data Catalog Vocabulary (DCAT) – Version 3W3C Dataset Exchange Working Groupadopt
Provenance and evidenceC2PA Content Credentials specificationCoalition for Content Provenance and Authenticity (Joint Development Foundation)adopt
Provenance and evidenceIETF SCITT architecture (Supply Chain Integrity…IETF SCITT working groupprofile
Provenance and evidencein-toto Attestation Frameworkin-toto project (CNCF)adopt
Provenance and evidenceSigstore (Cosign, Fulcio, Rekor)OpenSSF (Linux Foundation); graduated project March 2024adopt
Provenance and evidenceW3C PROV-O: The PROV OntologyW3C Provenance Working Groupadopt
Provenance and evidenceW3C Verifiable Credentials Data Model v2.0W3C Verifiable Credentials Working Groupcrosswalk

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.

05Adoption

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.

Adoption · PROV-OCompiled from public sources
అమలుByఇది ఏమిటి
prov (Python)Trung Dong Huynh and contributorsPROV data model library with PROV-O serialisation
PROV implementation reportW3C Provenance Working Groupimplementations reported at the time the Recommendation was published
ProvToolboxLuc Moreau and contributorsJava toolbox for PROV, including PROV-O
Test suite or validatorWhat it checks
PROV-CONSTRAINTS validators listed in the implementation reportvalidators recorded by the working group
Stack entryపాత్రఎగుమతి
W3C PROV-Oprovenance 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.

06సహకరించండి

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ఇది ఏమిటిWhat it requiresలింక్
Comment listpublic-prov-comments archive: comments on the PROV documentsan email address; the archive is publicOpen the comment list page
Errataerrata of the PROV family of documentserrata are reported through the comment listOpen the errata page
Process documentW3C Process Document (registry entry w3c-process-2025)to be read before participatingOpen the process document page
Community groupsW3C Community Groups: open to anyone with a W3C accounta W3C account and the community contributor agreementOpen the community groups page

Process explorer · NXS · Process

Contributing through a standards body

11 steps3 stages1 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.

  1. 01 Contributor

    1. 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
    2. 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
    3. 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.
    4. 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
  2. 02 The standards body

    1. 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.
    2. 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.
    3. 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.
    4. 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
  3. 03 Nexus Standards

    1. 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.
    2. 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.
    3. 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
Process · from a comment at the body to a register change11 operations
దశPhaseకార్యకలాపంWhoDecision ruleరికార్డు
01ContributorIdentify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document.the contributorthe register names the body and links to its own pagethe body’s page, linked from the package
02ContributorRead 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 contributormembership, patent policy and contributor agreements are set by the body and read at the sourcethe requirements of the channel
03The standards bodyJoin 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 committeethe channel belongs to the body and follows its process documenta list subscription, an issue account, a membership
04The standards bodyFile 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 trackeran issue is the body’s record, cited by URLan issue with a stable link
05The standards bodyPublic 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 processthe body decides under its own rules; the Nexus Standards record the public outcomecomment dispositions by the body
06ContributorPropose 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 channeltext is proposed through the body’s own channel; the body’s text remains with the bodya change request, an Internet-Draft or a comment with wording
07ContributorImplement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one.the contributora passing run is evidence of implementationa test run with the suite version and time
08The standards bodyImplementation report (record). Implementations are listed as submitted, in alphabetical order.the body or the working grouplisted as the body publishes it, without rankingthe report, linked
09Nexus StandardsCite 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 editorscited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalencea crosswalk entry or a clause citing the source
10Nexus StandardsChange 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 recordedevery change is submitted as a change proposal under NS-13a change proposal with a UNI
11Nexus StandardsRegister change (end). The register entry is amended and the package page is regenerated from it.editors, with reasons on recordaccepted, rejected or withdrawn in writing; the history is retainedthe 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.

08Updates

Latest releases from the body

Updates · listed for reference

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రిజిస్ట్రీఫార్మాట్Browser readDeliveryCadence
w3c.tr.feeddata-sourcesrdfunknowngoverned data service, build-time snapshotdaily
w3c.news.feeddata-sourcesrssunknowngoverned data service, build-time snapshotdaily
w3c.prov.comments.archivedata-sourceshtmlunknownbuild-time snapshotweekly

3 data sources listed.

09ప్రశ్నలు

ప్రశ్నలు మరియు సమాధానాలు.

Do the standards reproduce PROV-O?
No. The page names and links the document, lists its part numbers and titles, and cites it by identifier and clause number; the text remains with the body.
Where do the updates come from?
From the body’s own channels, once licence review of the data source is complete; until then, the page shows the latest version recorded in the registry.
Is the relation a conformance statement?
No. A relation is a registry entry. Conformance is shown clause by clause through attestations under NS-11.
ప్రమాణాలు

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.

స్థితి మరియు వినియోగం. Nexus Standards అనేవి NS-13 కింద బహిరంగ ప్రక్రియ ద్వారా అభివృద్ధి చేయబడి స్వచ్ఛంద వినియోగం కోసం ప్రచురించబడిన ప్రతిపాదిత ప్రమాణాలు; అవి ధృవీకరణ, గుర్తింపు లేదా నియంత్రణ ఆమోదం కావు, మరియు స్వీకరణ గ్లోబల్ స్టాండర్డ్స్ కౌన్సిల్ నిర్ణయంగా, మరియు ప్రతి దేశంలో దాని జాతీయ ప్రమాణాల మండలి నిర్ణయంగా ఉంటుంది. UNI (Unique Nexus Identifier) ఒక కళాఖండాన్ని గుర్తిస్తుంది; దానిని ధృవీకరించదు. ప్రమాణ సంస్థల పేర్లు మరియు వాటి ప్రమాణాలు వాటి సంరక్షకులకు చెందినవి మరియు పత్రాలను గుర్తించడానికి మాత్రమే ఉపయోగించబడతాయి; ఇక్కడ ఏ బాహ్య ప్రమాణ పాఠ్యమూ పునరుత్పత్తి చేయబడలేదు. Nexus Standardsకు ఇక్కడ పేర్కొన్న ఏ ప్రమాణ సంస్థతోనూ అనుబంధం లేదు, వాటి ఆమోదం లేదా ధృవీకరణ లేదు.

లైసెన్సులు: ప్రమాణాల పాఠ్యం, రిజిస్ట్రీలు, స్కీమాలు మరియు డేటా కోసం CC BY 4.0; సూచన కోడ్ కోసం Apache-2.0. బాహ్య ప్రమాణాలు వాటి సొంత లైసెన్సుల కింద పేరు, సంఖ్య మరియు లింక్ ద్వారా ఉల్లేఖించబడతాయి. మూడవ పక్ష డేటా, లైబ్రరీలు మరియు ఫాంట్‌లు వాటి సొంత లైసెన్సులను నిలుపుకుంటాయి: మూడవ పక్ష ప్రకటనలు చూడండి.