Skip to content
PDTF PDTF2
Proposed specification for review. We are seeking feedback on key architectural choices in the industry consultation.

Contribute

PDTF 2.0 is developed in the open. Contributions are welcome across specifications, reference implementations, test vectors, and documentation.

Where to contribute

Section titled “Where to contribute”

Work happens in the Property Data Standards Company GitHub organisation:

  • spec: protocol and implementation specs
  • core-*: reference implementations
  • federation-registry: OpenID Federation Trust Anchor
  • web: this website

How to propose changes

Section titled “How to propose changes”
  1. Open an issue describing the change and the motivation.
  2. Submit a pull request with the smallest coherent update.
  3. Keep terminology consistent across docs and specs.
  4. If a change affects trust, identifiers, or schema boundaries, call it out explicitly.

What makes a good PR

Section titled “What makes a good PR”
  • Examples that validate or compile.
  • Tests where code changes.
  • Docs updated alongside code.
  • Clear changelog entries in specs when semantics change.

Security

Section titled “Security”

If you believe you have found a security issue, avoid posting details publicly. Use the repository’s security reporting mechanism where available, or contact maintainers directly.