Open Web Platform year-end Highlights 2016
16 December 2016 | Archive
W3C published today Open Web Platform year-end Highlights 2016. We invite you to read how we are moving the Web ahead by continuously enhancing Web technology in particular in areas such as Virtual Reality, Web Payments, Web security and authentication, media playback, Web and Automotive, and by strengthening the core of the Web, HTML. Celebrate with us the 20th anniversary of CSS starting 17 December and throughout the coming year. Lastly, learn how the Web impacts your industry by meeting Members of the W3C Team at CES on 5-8 January 2017, Las Vegas, NV, USA. Come meet and discuss – we will be in Suite #313 at the Westgate Hotel.
Call for Review: Data on the Web Best Practices
15 December 2016 | Archive
The W3C Data on the Web Best Practices is now a Proposed Recommendation. Complemented by the Dataset Usage and Data Quality vocabularies (both published today as stable Notes), the Best Practices set out how publishers can share data on the Web with maximum benefit by harnessing the Network Effect. Areas like licensing, provenance, access APIs, identifiers for and within datasets, feedback, enrichment and preservation are all covered in this comprehensive work.
The Data on the Web Best Practices Working Group has compiled a substantial implementation report that demonstrates that the Best Practices are followed across many domains including government, scientific research and cultural heritage. The three documents are designed to further develop a dynamic ecosystem in which data can be discovered, understood, evaluated and reused, and that reuse recognized. Comments are welcome through 15 January 2017.
Call for Review: Web Cryptography API Proposed Recommendation Published
15 December 2016 | Archive
The W3C Web Cryptography is now a Proposed Recommendation. This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. Comments are welcome through 15 January 2017.