updated the timeline bullet 1 (@agbeltran suggestions) and tidied up …

…the opening paragraphs a little more

charter/index.html

@@ -154,12 +154,12 @@ <h1 id="title">Dataset Exchange Working Group Charter</h1>
 
       <section id="goals" class="goals">
         <h2>Goals</h2>
-        <p>Sharing data among researchers, governments and citizens, whether openly or not, requires the provision of metadata. Different communities use different metadata standards to describe their datasets, some of which are highly specialized. At a general level, W3C’s Data Catalog Vocabulary, <a href="https://www.w3.org/TR/vocab-dcat/">DCAT</a>, is in widespread use, but so too are <a href="https://ckan.org/">CKAN</a>’s native schema, schema.org's <a href="http://schema.org/Dataset">dataset description</a> vocabulary, <a href="http://www.iso.org/iso/catalogue_detail?csnumber=26020">ISO 19115</a>, <a href="http://www.ddialliance.org/explore-documentation">DDI</a>, <a href="https://sdmx.org/">SDMX</a>, <a href="http://www.eurocris.org/cerif/main-features-cerif">CERIF</a>, <a href="https://www.w3.org/TR/void/" title="Describing Linked Datasets with the VoID Vocabulary">VoID</a>, <a href="http://inspire.ec.europa.eu/index.cfm/pageid/101">INSPIRE</a> and, in the healthcare and life sciences domain, the <a href="https://www.w3.org/TR/hcls-dataset/">Dataset Description vocabulary</a> and <a href="https://github.com/biocaddie/WG3-MetadataSpecifications">DATS</a> (<a href="https://doi.org/10.1101/103143" title="DATS: the data tag suite to enable discoverability of datasets">ref</a>) among others.</p>
+        <p>Sharing data among researchers, governments and citizens, whether openly or not, requires the provision of metadata. Different communities use different metadata standards to describe their datasets, some of which are highly specialized. At a general level W3C’s Data Catalog Vocabulary, <a href="https://www.w3.org/TR/vocab-dcat/">DCAT</a>, is in widespread use, but so too are <a href="https://ckan.org/">CKAN</a>’s native schema, schema.org's <a href="http://schema.org/Dataset">dataset description</a> vocabulary, <a href="http://www.iso.org/iso/catalogue_detail?csnumber=26020">ISO 19115</a>, <a href="http://www.ddialliance.org/explore-documentation">DDI</a>, <a href="https://sdmx.org/">SDMX</a>, <a href="http://www.eurocris.org/cerif/main-features-cerif">CERIF</a>, <a href="https://www.w3.org/TR/void/" title="Describing Linked Datasets with the VoID Vocabulary">VoID</a>, <a href="http://inspire.ec.europa.eu/index.cfm/pageid/101">INSPIRE</a> and, in the healthcare and life sciences domain, the <a href="https://www.w3.org/TR/hcls-dataset/">Dataset Description vocabulary</a> and <a href="https://github.com/biocaddie/WG3-MetadataSpecifications">DATS</a> (<a href="https://doi.org/10.1101/103143" title="DATS: the data tag suite to enable discoverability of datasets">ref</a>) among others.  This variety is a clear indication that no single vocabulary offers a complete and universally accepted solution. </p>
 
-<p>This variety is a clear indication that no single vocabulary offers a complete and universally accepted solution.  There are further gaps in DCAT that can be closed, for example around time series and versions. DCAT has been successful and is in wide use, but these gaps must be addressed if usage is to continue to grow across different communities and the variety of metadata schemas is to reduce.</p>
+<p>DCAT has known gaps in coverage, for example around time series and versions. DCAT has been successful and is in wide use, but these gaps must be addressed if usage is to continue to grow across different communities and the variety of metadata schemas is to reduce.</p>
 
 <p>Maximizing interoperability between services such as data catalogs, e-Infrastructures and virtual research environments requires not just the use of standard vocabularies but of <em>application profiles</em>. These define how a vocabulary is used, for example by providing cardinality constraints and/or enumerated lists of allowed values such that data can be validated. The development of several application profiles based on DCAT, such as the European Commission's <a href="https://joinup.ec.europa.eu/asset/dcat_application_profile/description">DCAT-AP</a> is particularly noteworthy in this regard.</p>
-<p>Rather than limit the number of metadata standards and application profiles in use, systems should be able to expose and ingest (meta)-data according to multiple standards through a transparent and sustainable interface. We thus need a mechanism for servers to indicate the available standards and application profiles, and for clients to choose an appropriate one. This leads to the concept of content negotiation by application profile, which is orthogonal to content negotiation by data format and language that is already part of HTTP. A new RFC on this topic currently under development at IETF with input from the Dataset Exchange Working Group, is based on the <a href="http://profilenegotiation.github.io/I-D-Accept--Schema/I-D-accept-schema"> draft</a> presented at the <a href="https://www.w3.org/2016/11/sdsvoc/report#conneg">SDSVoc workshop</a>. Taken together, this external work and the DXWG's definition of what is meant by application profile and how clients and servers may interact in different ways based on that, will provide a powerful means to exchange data in any format (JSON, RDF, XML etc.) according to declared structures against which the data can be validated.</p>
+<p>Rather than limit the number of metadata standards and application profiles in use, systems should be able to expose and ingest (meta)-data according to multiple standards through transparent and sustainable interfaces. We thus need a mechanism for servers to indicate the available standards and application profiles, and for clients to choose an appropriate one. This leads to the concept of content negotiation by application profile, which is orthogonal to content negotiation by data format and language that is already part of HTTP. A new RFC on this topic currently under development at IETF with input from the Dataset Exchange Working Group, is based on the <a href="http://profilenegotiation.github.io/I-D-Accept--Schema/I-D-accept-schema"> draft</a> presented at the <a href="https://www.w3.org/2016/11/sdsvoc/report#conneg">SDSVoc workshop</a>. The combination of DXWG's definition of what is meant by "application profile", together with the DXWG view of how clients and servers may interact in different ways based on these profiles, together with this external work will provide a powerful means to exchange data in any format (JSON, RDF, XML etc.) according to declared structures against which the data can be validated.</p>
 <p>The goals of the working group are to maintain the version 2 of DCAT and extend the standard to version 3 in line with work done to date and the ongoing work on dataset exchange being undertaken by communities more generally, and to develop to a recommendation the work undertaken in the 2017-2019 charter period on content negotiation by profile.</p>
 
       </section>
@@ -247,10 +247,10 @@ <h3> Other Deliverables </h3>
                 <section id="timeline">
                     <h3>Timeline - Expected Delivery Dates</h3>
                     <ul>
-                        <li>Freshen and update the UCR document and the Github milestones to identify the specific elements of of DCAT version 3 -  Q1-2 2020
-                        <li>FPWD for DCAT 3 - Q3-4 2020</li>
-                        <li>CR for Conneg by application profile - Q1 2020</li>
-                        <li>CR for all Rec Track documents - Q4 2023</li>
+                        <li>Define Github milestones based on the backlog use cases and requirements (UCR) from DCAT2 and also considering any new use cases from the community, which will be distilled into a UCR document to guide the work on DCAT3 and subsequent revisions -  Q1-2 2020
+                        <li>Get a first public working draft (FPWD) for DCAT 3 - Q3-4 2020</li>
+                        <li>Get to Candidate Recommendation (CR) the content negotiation by application profile work - Q1 2020</li>
+                        <li>Get to CR all Recommendation Track documents - Q4 2021</li>
                     </ul>
                     <h3>Transition to Evergreen Standards Process</h3>
                     <p>It is expected that within the charter period the deliverables will enter the W3C &quot;evergreen&quot; standards process and procedures and deliverables will transition at an appropriate time.</p>