--- 0.20200227.2-CC-WM.txt	2020-02-27 16:18:36.405180683 +0000
+++ 0.20200227.3-CC-WM.txt	2020-02-27 17:12:16.786915088 +0000
@@ -1,7 +1,7 @@
 PeeringDB Data Ownership Policy Document
 
 Date: TBD
-Version: 0.20200227.2-CC-WM
+Version: 0.20200227.3-CC-WM
 
 1) Background
 
@@ -81,11 +81,18 @@
 3.4) Conflicted Data
 
 In some cases ownership of data elements may not be either/or, but rather 
-may be nuanced. For example, an Internet Exchange (IX) may have shared an 
-IP assignment with a new participant in advance of updating the IX's 
-public records, some of which may be processed by PeeringDB in an 
-automated fashion. This can result in a conflict based on PeeringDB 
-receiving differing information from two sources.
+may be nuanced. PeeringDB data is often used for Internet operations and 
+changes should not disrupt existing operational processes. This policy 
+specifies a principle of minimal disruption. This principle means that 
+conflicted data which is already published shall not be taken down unless 
+done so by the Network, PeeringDB automation explicitly authorized by the 
+Network, or by a resolution process mediated by the Admin Committee.
+
+For example, an Internet Exchange (IX) may have shared an IP assignment 
+with a new participant in advance of updating the IX's public records, 
+some of which may be processed by PeeringDB in an automated fashion. This 
+can result in a conflict based on PeeringDB receiving differing 
+information from two sources.
 
 4) High Level Data Descriptions
 
@@ -515,7 +522,8 @@
 
   Similarly, conflicted data which has not been published shall not be 
   published until a resolution process has been mediated by the Admin 
-  Committee.
+  Committee and/or the conflict is resolved due to updated data from the 
+  Internet Exchange or the Network.
 
   The Task Force recommends PeeringDB employ user interface methods and 
   email notifications to encourage data harmony between a Network and an