Skip to content

Conversation

@mrshll1001
Copy link
Contributor

Following the decision of the Stewardship Committee on 2025-06-17, this PATCH updates the deprecation policy in the standard documentation to read as the following:

If a term, such as a field title (known as a class or property in JSON schema) is scheduled to be renamed or removed as a result of the revision process, the next release must deprecate the term within the schema. The following MAJOR release must rename or remove the term from the schema, making it obsolete. Data that is published may use deprecated terms, but will receive warnings from the 360Giving Data Quality tool. Once obsolete, terms in published data will be treated like any other non-Standard fields.

Updated the governance policy to permit the use of obsolete terms in
the standard, as per the result of the SC meeting on 2025-06-17.
Updated the governance policy to permit the use of obsolete terms in
the standard, as per the result of the SC meeting on 2025-06-17.
@mrshll1001
Copy link
Contributor Author

Just noting that I have run a docs build and everything appears to be fine:

@mariongalley
Copy link
Contributor

Approving but could we uppercase the T on Data Quality Tool?

"Data Quality Tool" was not properly capitalised, as per

#417 (comment)
@mrshll1001
Copy link
Contributor Author

Good catch, I've fixed that. It's reflected on the docs build as well, so I'll proceed with the merge now.

@mrshll1001 mrshll1001 merged commit 34344ea into main Aug 20, 2025
4 checks passed
@mrshll1001 mrshll1001 deleted the update-deprecation-policy branch August 20, 2025 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants