Skip to main content
Version: 0.2 Draft 2

13. Extension Namespace Promotion to Core

13.1 Purpose​

The PCT core schema is intentionally minimal. It defines the fields that are universally applicable across all jurisdictions and use cases. Extension namespaces address jurisdiction-specific, sector-specific, or use-case-specific obligations that are not universally applicable.

Over time, some extension namespaces may demonstrate sufficient universality, maturity, and implementer consensus to warrant promotion to the core schema. This section defines the criteria and process by which that promotion may occur.

13.2 Promotion criteria​

An extension namespace field or set of fields may be considered for promotion to the core schema when all of the following criteria are satisfied:

Universality. The obligation addressed by the field arises under regulatory frameworks that together govern a significant majority of global personal data processing activity. A field that is relevant only to a single jurisdiction or sector will not meet this criterion regardless of the size of that jurisdiction or sector.

Maturity. The namespace must have been registered and in active documented use for a minimum of one full version cycle of the PCT specification. Fields proposed for promotion from v0.2 extensions must therefore have been registered no later than the publication of v0.2 and must have demonstrable implementation evidence by the time v1.0 is being drafted.

Implementation evidence. There must be documented evidence of real-world implementation of the namespace fields in question by at least three independent organisations. Self-certification by the registrant is not sufficient. Evidence may take the form of public conformance declarations, case studies, or verified implementation reports submitted to the PCT GitHub Discussions board.

Community consensus. There must be broad agreement within the PCT implementer and legal community that the field belongs in the core schema. This is assessed through the GitHub Discussions process and, where necessary, a formal comment period. Significant unresolved objections from substantive contributors will prevent promotion regardless of other criteria being met.

Schema compatibility. The proposed field must be compatible with the existing core schema and must not create conflicts with existing required or optional fields. Where a promoted field would require changes to the core schema beyond simple addition, those changes must themselves be subject to the full comment process.

13.3 Promotion process​

Promotion proposals may be submitted by any party, including the original namespace registrant, any implementer, or DPG Labs itself. A promotion proposal must be submitted as a GitHub Issue using the promotion proposal template and must include:

  • The namespace prefix and specific field or fields proposed for promotion
  • Evidence satisfying each of the criteria in Section 13.2
  • Proposed core schema field name, type, and description
  • Analysis of any backwards compatibility implications
  • Proposed handling of the existing extension namespace field following promotion (deprecation timeline, mapping guidance)

DPG Labs will review promotion proposals and open a formal 60-day public comment period for each substantive proposal. Following the comment period, DPG Labs will publish a decision with reasons. Accepted promotions will be incorporated into the next major or minor version of the specification as appropriate.

13.4 Deprecation of promoted extension fields​

Where an extension namespace field is promoted to core, the original extension namespace field does not become invalid immediately. A deprecation period of at least one full version cycle will apply, during which both the core field and the extension field are accepted by conformant verifiers. Implementers are expected to migrate to the core field during this period.

Following the deprecation period, verifiers are no longer required to process the deprecated extension field. The original namespace registration remains active in the registry but is marked as deprecated with a reference to the core field that replaced it.

13.5 Fields that will not be promoted​

The following categories of field are not eligible for promotion to the core schema regardless of adoption levels:

  • Fields addressing obligations that arise under a single national jurisdiction only, where there is no reasonable prospect of that obligation being adopted universally.
  • Fields addressing highly sector-specific obligations with no applicability outside that sector.
  • Fields that duplicate or overlap substantially with existing core fields.
  • Fields submitted by a registrant with a commercial interest in the promotion that have not achieved independent third-party implementation evidence.