pubvendors to-be-deprecated

As of the publication of Transparency and Consent Framework April 25, 2019, this specification is marked as to-be-deprecated. Please review the Transparency and Consent Frameworks for public comment to learn how the new specification support the required use cases within the TC String.

pubvendors.json v1.0 Draft for Public Comment.md

@@ -4,6 +4,11 @@
 
 **Draft for Public Comment | May 2018**
 
+## Specification to be deprecated
+*Note, April 25 2019* 
+
+As of the publication of Transparency and Consent Framework April 25, 2019, this specification is marked as to-be-deprecated. Please review the Transparency and Consent Frameworks for public comment to learn how the new specification support the required use cases.
+
 # Table of Contents
 1. [Introduction](#Introduction)
 2. [About the Transparency & Consent Framework](#About-the-Framework)
@@ -311,4 +316,4 @@ We could expand the consent string to support Legitimate Interest in the future.
 
 The goal of pubvendors.json is to publicly identify direct data processing relationships between publishers and ad technology providers. As such publishers should identify all DSPs, SSPs and DMPs who they have an agreement with to process data. Additionally this should include any partners who you feel comfortable gaining consent on their behalf. This list should include: programmatic partners and any third-party data providers you utilize to help build audience segments.  This may exclude downstream third parties who you do not feel comfortable authorizing consent as their legal basis for data collection of your users. 
 
-As needed, additional guidance will be created by the IAB Tech Lab GDPR working group.
+As needed, additional guidance will be created by the IAB Tech Lab GDPR working group.