2.2 creation

Updated the scope with right numbers
Updated publish date
Updated status to Commit instead of Living document

Cpix.bs.md

@@ -2,11 +2,9 @@
 
 The scope of this document is to define a Content Protection Information Exchange Format (CPIX). A CPIX document contains keys and DRM information used for encrypting and protecting content and can be used for exchanging this information among entities needing it in many possibly different workflows for preparing, for example, DASH or HLS content. The CPIX document itself can be encrypted, signed and authenticated so that its receivers can be sure that its confidentiality, source and integrity are also protected.
 
-This specification describes version 2.1 of the CPIX document format. Detailed changes with respect to version 2.0 are tracked on [GitHub](https://github.com/Dash-Industry-Forum/CPIX/issues). Highlighted changes are:
+This specification describes version 2.2 of the CPIX document format. Detailed changes with respect to version 2.2 are tracked on [GitHub](https://github.com/Dash-Industry-Forum/CPIX/issues). Highlighted changes are:
 
-* Updated HLS signalization support and added the support for Smooth Streaming
-* Added new label attributes to usages rules for keys and corrected.
-* Added key hierarchy support (2 layers of keys).
+* Bug fixes on the HLS signalization support.
 
 # Disclaimer # {#disclaimer}
 
@@ -1009,11 +1007,11 @@ In addition, the document contains <{DRMSystem}> elements for the two DRM system
 <!-- Document metadata follows. The below sections are used by the document compiler and are not directly visible. -->
 
 <pre class="metadata">
-Date: 2018-07-16
-Revision: 2.1
+Date: 2019-03-22
+Revision: 2.2
 
 Title: DASH-IF Implementation Guidelines: Content Protection Information Exchange Format (CPIX)
-Status: LD
+Status: LS-COMMIT
 Shortname: cpix
 URL: https://dashif.org/guidelines/
 Issue Tracking: GitHub https://github.com/Dash-Industry-Forum/CPIX/issues