Merge branch 'release/2016-11-03_update'

Author: ahouseholder

README.md

@@ -1,10 +1,13 @@
 # CERT Coordination Center Vulnerability Data Archive
 
-Release 2016-03-30
+Release 2016-06-24
 
 
 ### Change Log
 
+2016-06-24  Changed search URL, sponsorship, added GitHub migration,
+            no change to data
+
 2016-03-30  Updated data
 
 2014-12-08  Updated data, note significant number of nearly identical
@@ -23,15 +26,15 @@ Release 2016-03-30
 ## Description
 
 This data archive contains nearly all of the non-sensitive vulnerability 
-data collected by the CERT/CC, from the inception of the vulnerability 
-notes database (approximately May 1998) to the date the archive was 
-prepared, as noted above in the Change Log.
+data collected by CERT, from the inception of the vulnerability notes 
+database (approximately May 1998) to the date the archive was prepared, 
+as noted above in the Change Log.
 
-Since roughly 2004, the United States Department of Homeland
-Security (DHS) United States Computer Emergency Readiness Team (US-CERT)
-has funded the vulnerability analysis and coordination work that
-includes this vulnerability data and the publication of Vulnerability
-Notes: <http://www.kb.cert.org/vuls>
+Since roughly 2004, the United States Department of Homeland Security 
+(DHS) United States Computer Emergency Readiness Team (US-CERT) and 
+other government sponsors have funded the vulnerability analysis and 
+coordination work that includes this vulnerability data and the 
+publication of [Vulnerability Notes](http://www.kb.cert.org/vuls).
 
 This data is incomplete.  All records (reports) should have an ID, 
 title, and creation date.  Only some (~6%) of the reports have been 
@@ -72,18 +75,17 @@ See <https://github.com/CERTCC-Vulnerability-Analysis/Vulnerability-Data-Archive
 
 ### Tell Us About It
 
-Did you find something interesting in the data? Did you come up with some cool way of slicing it or remixing it and you want to share? You can tweet us [@certcc](https://twitter.com/certcc). Or send mail to [cert@cert.org](mailto:cert@cert.org?subject=INFO%23365908%20Vulnerability%20Data%20Archive%20Feedback).
+Did you find something interesting in the data? Did you come up with some cool way of slicing it or remixing it and you want to share? You can tweet us [@certcc](https://twitter.com/certcc). Or send mail to [cert@cert.org](mailto:cert@cert.org?subject=VCALL-119%20Vulnerability%20Data%20Archive%20Feedback).
 
 If you find a problem with the data or the tools, please create an issue report in the appropriate repository.
 
 Please be aware though that we offer no formal support, however we may respond to questions and 
-feedback sent to [cert@cert.org](mailto:cert@cert.org?subject=INFO%23365908%20Vulnerability%20Data%20Archive%20Feedback) with the tag INFO#365908 in the subject. 
+feedback sent to [cert@cert.org](mailto:cert@cert.org?subject=VCALL-119%20Vulnerability%20Data%20Archive%20Feedback) with the tag VCALL-119 in the subject. 
 
 
 ## Data Format
 
-The data in this repository has been transformed from the data found at <http://www.cert.org/download/vul_data_archive/>. That data set contains 
-archives raw exports of the CERT Vulnerability Notes database. The vulnerability notes database is a Lotus Notes application, and the raw JSON and XML exports in the original archive can be difficult to work with. In this repository we've converted the JSON data to more conventional key-value pairs to make it easier to use.
+The data in this repository has been transformed from the data found at <http://www.cert.org/download/vul_data_archive/>. That data set contains archives raw exports of the CERT Vulnerability Notes database. The Vulnerability Notes Database is a Lotus Notes application, and the raw JSON and XML exports in the original archive can be difficult to work with. In this repository we've converted the JSON data to more conventional key-value pairs to make it easier to use.
 
 The directory structure is as follows:
 
@@ -99,9 +101,7 @@ In the Lotus Notes application from which this data was exported, s\Some fields
 ## [Field Definitions for Vulnerability Reports](id:vrdesc)
 
 Descriptions for fields included in published Vulnerability Notes are
-also available here:
-
-  <http://www.kb.cert.org/vuls/html/fieldhelp>
+also available [here](http://www.kb.cert.org/vuls/html/fieldhelp).
 
 Some of the fields in this archive are not included in published 
 Vulnerability Notes.