Updating deprecation policy - closes #367

open-contracting · Feb 7, 2017 · 47edbc8 · 47edbc8
1 parent 9c1a247
commit 47edbc8
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 1 deletion.
diff --git a/standard/docs/en/schema/deprecation.md b/standard/docs/en/schema/deprecation.md
@@ -0,0 +1,12 @@
+# Deprecation
+
+From time to time fields and codelist values may be removed from the Open Contracting Data Standard.
+
+This will be either due to limited use, or because they have been replaced by alternative fields or codelists.
+
+Before a field or codelist value is removed, it will be first marked as deprecated in a major or minor release (e.g. in 1.1), and removal will only take place, subject to the [governance](governance.md) process, in the next major version (e.g. 2.0).
+
+
+
+
+
diff --git a/standard/docs/en/schema/index.md b/standard/docs/en/schema/index.md
@@ -25,6 +25,7 @@ The [release schema reference](reference.md) page provides guidance on using eac
    identifiers
    codelists
    conformance_and_extensions
+   deprecation
    changelog
 
 ```
diff --git a/standard/docs/en/support/governance.md b/standard/docs/en/support/governance.md
@@ -174,7 +174,7 @@ Following **working group** approval, the revision branch can be set to live.
 
 See https://github.com/open-contracting/standard/issues/189
 
-If a term (a class or property) is scheduled to be renamed or removed from the specification as a result of the revision process, the next major release of the specification must [deprecate](https://en.wikipedia.org/wiki/Deprecation) the term within the schema, and the following major release must rename or remove the term from the schema, making the term obsolete. Implementations may use deprecated terms, but will receive warnings from the OCDS validator described below. Implementations may not use obsolete terms, and will receive errors from the OCDS validator.
+If a term (a class or property) is scheduled to be renamed or removed from the specification as a result of the revision process, the next minor release of the specification must [deprecate](https://en.wikipedia.org/wiki/Deprecation) the term within the schema, and the following major release must rename or remove the term from the schema, making the term obsolete. Implementations may use deprecated terms, but will receive warnings from the OCDS validator described below. Implementations may not use obsolete terms, and will receive errors from the OCDS validator.
 
 ## Support policy