Subscribe: W3C News
http://www.w3.org/2000/08/w3c-synd/home.rss
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
css  data  document  group published  group  language  published  recommendation  specification  web  working group  working  xquery 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: W3C News

W3C News



Leading the Web to its Full Potential



Updated: 2017-03-22T14:28:37Z

 



XQuery 3.1, XQueryX 3.1, XPath 3.1 and supporting documents now a W3C Recommendation

2017-03-22T14:25:58Z

The XML Query Working Group and the XSLT Working Group have published six documents as W3C Recommendations to strengthen JSON and Web Platform support through maps, arrays, new functions: XQuery 3.1: An XML Query Language XQueryX 3.1 XML Path Language (XPath) 3.1 XQuery and XPath Data Model 3.1 XPath and XQuery Functions and Operators 3.1 […]The XML Query Working Group and the XSLT Working Group have published six documents as W3C Recommendations to strengthen JSON and Web Platform support through maps, arrays, new functions: XQuery 3.1: An XML Query Language XQueryX 3.1 XML Path Language (XPath) 3.1 XQuery and XPath Data Model 3.1 XPath and XQuery Functions and Operators 3.1 XSLT and XQuery Serialization 3.1 The 3.1 work extends XPath and XQuery with map and array data structures along with additional functions and operators for manipulating them; a primary motivation was to enhance JSON support. XPath is a domain-specific language for identifying and extracting nodes from a tree (typically) built from XML or JSON and defined by the XQuery and XPath Data Model) and also an expression language with typed tree nodes and functions among the first-class objects. XPath expressions can call functions and use operators defined in the Functions and Operators specification. XQuery extends XPath to support complex joins, windowing, grouping and other operations across collections of trees that are potentially stored in high-performance indexed databases. XQueryX is an XML representation of XQuery expressions. The Serialization specification describes how results of XPath and XQuery(X) expressions can be delivered in HTML, XHTML, JSON, XML or text. [...]



Call for Review: Encrypted Media Extensions Proposed Recommendation Published

2017-03-20T16:39:30Z

The HTML Media Extensions Working Group has published a Proposed Recommendation of Encrypted Media Extensions. The specification extends HTMLMediaElement to define a common API to control playback of protected content. EME does not define a content protection or Digital Rights Management system. The common API may be used to discover, select and interact with such […](image)

The HTML Media Extensions Working Group has published a Proposed Recommendation of Encrypted Media Extensions. The specification extends HTMLMediaElement to define a common API to control playback of protected content. EME does not define a content protection or Digital Rights Management system. The common API may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Comments are welcome through 13 April. Please, read more in the public announcement.

(image)



Patent Advisory Group Recommends Continuing Work on Web Payments Specifications

2017-03-16T12:46:53Z

The Web Payments Working Group Patent Advisory Group (PAG), launched in August 2016, has published a report recommending that W3C continue work on the Web Payments Specifications. W3C launches a PAG to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the W3C Royalty-Free licensing […](image)

The Web Payments Working Group Patent Advisory Group (PAG), launched in August 2016, has published a report recommending that W3C continue work on the Web Payments Specifications. W3C launches a PAG to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the W3C Royalty-Free licensing terms.

(image)



Ivan Herman and Bill McCoy to address the Publishing and EPUB road-map at EPUB Summit

2017-03-16T12:49:18Z

Publishing@W3C champion Bill McCoy and W3C Fellow from CWI Dr. Ivan Herman will join an impressive line-up of speakers next week at the EPUB Summit, 9-10 March 2017 in Brussels, Belgium, hosted by W3C member EDRLab. The second such event, EPUB Summit will focus on the future direction of EPUB 3, now under W3C oversight […](image)

(image) Publishing@W3C champion Bill McCoy and W3C Fellow from CWI Dr. Ivan Herman will join an impressive line-up of speakers next week at the EPUB Summit, 9-10 March 2017 in Brussels, Belgium, hosted by W3C member EDRLab. The second such event, EPUB Summit will focus on the future direction of EPUB 3, now under W3C oversight following the combination with IDPF. Registration for the EPUB Summit is still open.

A technical expert in the field, Herman is part of the leadership team of Publishing@W3C as well as the overall Strategy team of W3C. Herman was recently appointed a W3C Fellow by CWI, Amsterdam, where he is a member of the Distributed and Interactive Systems research group. He played a seminal role in the combination of W3C and IDPF and has served as primary technical staff driver for the Digital Publishing at the W3C since inception in 2013. At the EPUB Summit Herman will talk about the IDPF/W3C combination, and the roadmap for upcoming technical work for the development of new standards in Publishing.

McCoy, former Executive Director for IDPF, will lead the closing session at the EPUB Summit, integrating the collective sessions and ideas into the roadmap for Publishing@W3C.

(image)



W3C Security Disclosures Best Practices is a W3C Team Submission

2017-03-22T14:26:05Z

W3C published a Team Submission of W3C Security Disclosures Best Practices, a proposal for security and privacy disclosure programs, which will serve as a basis for further work in the space of security and privacy researchers protection, further to our announcement late January. This document contains a template intended for organizations interested in protecting their […](image)

(image) W3C published a Team Submission of W3C Security Disclosures Best Practices, a proposal for security and privacy disclosure programs, which will serve as a basis for further work in the space of security and privacy researchers protection, further to our announcement late January. This document contains a template intended for organizations interested in protecting their users and applications from fraud, malware, and computer viruses, as well as interested in ensuring proper adherence to security and privacy considerations included in W3C Recommendations. It also helps to support broad participation, testing, and audit from the security community to keep users safe and the web’s security model intact.

In the coming days, the W3C Director will send the W3C Membership a Call for Review for the Encrypted Media Extensions Proposed Recommendation; and solicit feedback and expression of interest for the specification and the W3C Security Disclosures Best Practices Team Submission.

You may read more in the January 2017 Information about W3C Guidelines for Vulnerability Disclosure Programs and in the article on EME in HTML5 published this week by W3C Director’s Tim Berners-Lee.

(image)



W3C updates its Process Document

2017-03-22T14:28:37Z

W3C Membership approved the 1 March 2017 W3C Process Document, which becomes in effect today. Notable major changes of the 2017 update include: A process for marking a Recommendation as Obsolete (distinct from Rescinding a Recommendation); Voting mechanism used for AB and TAG elections is Single Transferable Vote; Clarified the process for continuing work on […](image)

W3C Membership approved the 1 March 2017 W3C Process Document, which becomes in effect today. Notable major changes of the 2017 update include:

  • A process for marking a Recommendation as Obsolete (distinct from Rescinding a Recommendation);
  • Voting mechanism used for AB and TAG elections is Single Transferable Vote;
  • Clarified the process for continuing work on a specification initially developed under another charter (aka Supergroups).

You may read more in the W3C Blog post “What’s new in the W3C Process 2017?“. This document was developed between the W3C Advisory Board and the public Revising W3C Process Community Group.

(image)



First Public Working Draft: Web Content Accessibility Guidelines 2.1

2017-03-03T16:53:11Z

Web Content Accessibility Guidelines (WCAG) 2.1 has been published as a First Public Working Draft. This will be the first update to Web Content Accessibility Guidelines since WCAG 2.0. Sites that conform to WCAG 2.1 will also conform to WCAG 2.0, which means they meet the requirements of any policies that reference WCAG 2.0, while also better meeting the […](image)

Web Content Accessibility Guidelines (WCAG) 2.1 has been published as a First Public Working Draft. This will be the first update to Web Content Accessibility Guidelines since WCAG 2.0. Sites that conform to WCAG 2.1 will also conform to WCAG 2.0, which means they meet the requirements of any policies that reference WCAG 2.0, while also better meeting the needs of users on the current Web. This first draft includes 28 new Success Criteria, three of which have been formally accepted by the Working Group and the remainder included as proposals to provide an opportunity for early feedback. Public feedback will be important to next steps on these proposals.

Further information is available in the blog post: Web Content Accessibility Guidelines 2.1 First Public Working Draft.

Please comment by filing GitHub issues in the WCAG 2.1 repository or, if this is not feasible, by email to public-agwg-comments@w3.org, by 31 March 2017. Read about the Accessibility Guidelines Working Group and the Web Accessibility Initiative (WAI).

(image)



W3C Begins Standards Work on Web of Things to Reduce IoT Fragmentation

2017-03-22T14:27:50Z

To further the growth of market for IoT devices and services, W3C has launched the Web of Things Working Group to develop initial standards for the Web of Things, tasked with the goal to counter the fragmentation of the IoT; reduce the costs of development; lessen the risks to both investors and customers; and encourage […](image)

(image) To further the growth of market for IoT devices and services, W3C has launched the Web of Things Working Group to develop initial standards for the Web of Things, tasked with the goal to counter the fragmentation of the IoT; reduce the costs of development; lessen the risks to both investors and customers; and encourage exponential growth in the market for IoT devices and services.

In advance of W3C’s presence at Mobile World Congress 2017 next week, where W3C executives will be available on 27-29 February, W3C CEO Dr. Jeff Jaffe commented, “There are huge, transformative opportunities not only for mobile operators but for all businesses if we can overcome the fragmentation of the IoT. As stewards of the Open Web Platform, W3C is in a unique position to create the royalty-free and platform-independent standards needed to achieve this goal.

Read the Media Advisory to learn about the technical approach the Working Group will take and the broad range of collaboration.

(image)



Three recommendations to enable Annotations on the Web

2017-03-22T14:27:39Z

The Web Annotation Working Group has just published a Recommendation for Web Annotation in the form of three documents: Web Annotation Data Model—specification describes a structured model and format, in JSON, to enable annotations to be shared and reused across different hardware and software platforms. Common use cases can be modeled in a manner that […](image)

The Web Annotation Working Group has just published a Recommendation for Web Annotation in the form of three documents:

  • Web Annotation Data Model—specification describes a structured model and format, in JSON, to enable annotations to be shared and reused across different hardware and software platforms. Common use cases can be modeled in a manner that is simple and convenient, while at the same time enabling more complex requirements, including linking arbitrary content to a particular data point or to segments of timed multimedia resources.
  • Web Annotation Vocabulary—specifies the set of RDF classes, predicates and named entities that are used by the Web Annotation Data Model. It also lists recommended terms from other ontologies that are used in the model, and provides the JSON-LD Context and profile definitions needed to use the Web Annotation JSON serialization in a Linked Data context.
  • Web Annotation Protocol—describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.

The group has also produced two additional Working Group Notes:

  • Embedding Web Annotations in HTML—describes and illustrates potential approaches for including annotations within HTML documents. Examples also are included illustrating the use within an HTML document of annotation Selectors as fragment identifiers.
  • Selectors and States—selecting part of a resource on the Web is an ubiquitous action. This document does not define any new approach to selection; instead, it relies on the formal specification and the semantics in the Web Annotation Data Model. The current document only “extracts” Selectors and States from that data model; by doing so, it makes their usage easier for applications developers whose concerns are not related to annotations.
(image)



First Public Working Drafts: CSS Timing Functions Level 1; CSS Containment Module Level 1

2017-03-16T12:48:53Z

The CSS Working Group has published two First Public Working Drafts today: CSS Timing Functions Level 1, a module that describes a way for authors to define a transformation to be applied to the time of an animation. This can be used to produce animations that mimic physical phenomena such as momentum or to cause […](image)

The CSS Working Group has published two First Public Working Drafts today:

  • CSS Timing Functions Level 1, a module that describes a way for authors to define a transformation to be applied to the time of an animation. This can be used to produce animations that mimic physical phenomena such as momentum or to cause the animation to move in discrete steps producing robot-like movement.
  • CSS Containment Module Level 1, a module which describes the ‘contain’ property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
(image)



W3C Workshop Report: Smart Descriptions and Smarter Vocabularies (SDSVoc)

2017-03-03T17:05:06Z

W3C published today the report from the W3C “Smart Descriptions & Smarter Vocabularies (SDSVoc)” workshop, held on 30 November – 1 December 2016 in Amsterdam. The report contains an executive summary and conclusions, as well as a brief summary and visual report of each session, with links to all presentation slides. The event’s agenda also […](image)

(image) W3C published today the report from the W3C “Smart Descriptions & Smarter Vocabularies (SDSVoc)” workshop, held on 30 November – 1 December 2016 in Amsterdam.

The report contains an executive summary and conclusions, as well as a brief summary and visual report of each session, with links to all presentation slides. The event’s agenda also links to the papers received and the rough notes taken throughout the event. The clear conclusion from the well attended workshop was that a new Working Group is needed to achieve two goals:

  1. Revise and expand the Data Catalog Vocabulary, DCAT to cover versioning, data series, APIs and more.
  2. Develop the concepts of data profiles (cardinality constraints and enumerated allowed values) and, from that, the mechanisms for content negotiation by those profiles. Following a careful analysis of the current state of the art, presented at the workshop, an Internet Draft is already in preparation on this topic. The WG’s role will be to put this in context and explain how fallback mechanisms can be used.

We’ve shared advance notice today that the W3C team is working on a draft charter for a new Data Exchange Working Group, and encourage public comments and suggestions on the draft charter in the dxwg GitHub issue repository.

We thank our Workshop sponsors: the EU-funded VRE4EIC project and Informatie Vlaanderen, the Flemish government’s digital agency, as well as our host, CWI, for making this event possible.

(image)



Spatial Data on the Web Best Practices Note Published

2017-03-02T13:44:21Z

The Spatial Data on the Web Working Group has published a Group Note of Spatial Data on the Web Best Practices. This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are […](image)

The Spatial Data on the Web Working Group has published a Group Note of Spatial Data on the Web Best Practices. This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting a Linked Data approach. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Linked Data cloud; the 5 Stars of Linked Data paradigm is promoted where relevant.

(image)



Ready-made Counter Styles Note Published

2017-03-02T13:44:15Z

The Internationalization Working Group has published a Working Group Note that contains templates for counter styles used by various cultures around the world. It can be used as a reference for those wishing to add user-defined counter styles in their CSS style sheets. The content of this document was originally part of the CSS Lists […](image)

The Internationalization Working Group has published a Working Group Note that contains templates for counter styles used by various cultures around the world. It can be used as a reference for those wishing to add user-defined counter styles in their CSS style sheets. The content of this document was originally part of the CSS Lists and Counters specification, but is now published as a standalone document. It is expected that the document will be updated from time to time to include new counter styles.

(image)



First Public Working Draft: International text layout and typography index

2017-02-28T11:10:23Z

The Internationalization Working Group has published a First Public Working Draft of International text layout and typography index. This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to […](image)

The Internationalization Working Group has published a First Public Working Draft of International text layout and typography index. This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to useful articles and papers. It is not exhaustive, and will be added to from time to time.

(image)



W3C Invites Implementations of XSL Transformations (XSLT) Version 3.0

2017-02-24T13:14:14Z

The XSLT Working Group invites implementations of the Candidate Recommendation of XSL Transformations (XSLT) Version 3.0 . This specification defines the syntax and semantics of XSLT 3.0, a language designed primarily for transforming XML documents into other XML documents. XSLT 3.0 is a revised version of the XSLT 2.0 Recommendation XSLT 2.0 published on 23 […](image)

The XSLT Working Group invites implementations of the Candidate Recommendation of XSL Transformations (XSLT) Version 3.0 . This specification defines the syntax and semantics of XSLT 3.0, a language designed primarily for transforming XML documents into other XML documents. XSLT 3.0 is a revised version of the XSLT 2.0 Recommendation XSLT 2.0 published on 23 January 2007.

The primary purpose of the changes in this version of the language is to enable transformations to be performed in streaming mode, where neither the source document nor the result document is ever held in memory in its entirety. Another important aim is to improve the modularity of large stylesheets, allowing stylesheets to be developed from independently-developed components with a high level of software engineering robustness.

(image)



First Public Working Draft: TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1)

2017-02-23T04:59:37Z

The Timed Text Working Group has published a Working Draft of TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1). This document specifies two profiles of TTML1: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and […](image)

The Timed Text Working Group has published a Working Draft of TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1). This document specifies two profiles of TTML1: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.

(image)



Two Notes Published by the Multimodal Interaction Working Group

2017-02-20T10:44:08Z

The Multimodal Interaction Working Group has published two Group Notes: Discovery & Registration of Multimodal Modality Components: This document is addressed to people who want to develop Modality Components for Multimodal Applications distributed over a local network or “in the cloud”. With this goal, in a multimodal system implemented according to the Multimodal Architecture Specification, […](image)

The Multimodal Interaction Working Group has published two Group Notes:

  • Discovery & Registration of Multimodal Modality Components: This document is addressed to people who want to develop Modality Components for Multimodal Applications distributed over a local network or “in the cloud”. With this goal, in a multimodal system implemented according to the Multimodal Architecture Specification, over a network, to configure the technical conditions needed for the interaction, the system must discover and register its Modality Components in order to monitor and preserve the overall state of the distributed elements. Therefore, Modality Components can be composed with automation mechanisms in order to adapt the Application to the state of the surrounding environment.
  • EMMA: Extensible MultiModal Annotation markup language Version 2.0: The W3C Multimodal Interaction Working Group aims to develop specifications to enable access to the Web using multimodal interaction. This document is part of a set of specifications for multimodal systems, and provides details of an XML markup language for containing and annotating the interpretation of user input and production of system output.
(image)



Seven Notes Published by the Evaluation and Repairs Tool Working Group

2017-02-07T21:06:45Z

The Evaluation and Repairs Tool Working Group has published seven Group Notes: Requirements for the Evaluation and Report Language 1.0: This document describes the requirements for the scope, design, and features of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and […]The Evaluation and Repairs Tool Working Group has published seven Group Notes: Requirements for the Evaluation and Report Language 1.0: This document describes the requirements for the scope, design, and features of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. Evaluation and Report Language 1.0 Schema describes the formal schema of the Evaluation and Report Language 1.0. The Evaluation and Report Language defines a vocabulary for expressing test results. It enables any person, software application, or organization to assert test results for any test subject tested against any set of criteria. The test subject might be a website, an authoring tool, a user agent, or some other entity. The set of criteria may be accessibility guidelines, formal grammars, or other types of quality assurance requirements. Thus, EARL is flexible with regard to the contexts in which it can be applied. Developer Guide for Evaluation and Report Language 1.0: This is a guide to the Evaluation and Report Language 1.0 for developers of software tools and processes. It provides an introduction to EARL and its uses, defines conformance requirements for tools supporting EARL, and describes approaches for serializing EARL data in different formats. Developers’ Guide to Features of Web Accessibility Evaluation Tools: This document describes features that web authoring and quality assurance tools can incorporate, so that they support the evaluation of accessibility requirements, such as those defined by the Web Content Accessibility Guidelines (WCAG) 2.0. The main purpose of this document is to promote awareness of such tool features and to provide introductory guidance for tool developers on what kind of features they could provide in future implementations of their tools. HTTP Vocabulary in RDF 1.0: The identification of resources on the Web by a Uniform Resource Identifier (URI) alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). It provides a representation of the HTTP vocabulary in the Resource Description Framework (RDF), to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by the Internet Assigned Numbers Authority (IANA). These terms can also be used to record HTTPS exchanges. Representing Content in RDF 1.0: This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF). This vocabulary is intended to provide a flexible framework within dif[...]



W3C Welcomes IDPF as Organizations Officially Combine to Develop Roadmap for Future of Publishing

2017-02-23T04:59:28Z

W3C announced on 1 February 2017 that the World Wide Web Consortium (W3C) and the International Digital Publishing Forum (IDPF) have combined organizations to better align Publishing and Web technologies and to create a new roadmap for the future of publishing. “W3C is thrilled to gain the expertise of the publishing industry with its rich […](image)

(image) W3C announced on 1 February 2017 that the World Wide Web Consortium (W3C) and the International Digital Publishing Forum (IDPF) have combined organizations to better align Publishing and Web technologies and to create a new roadmap for the future of publishing.

“W3C is thrilled to gain the expertise of the publishing industry with its rich tradition of excellence in developing many forms of content for books, magazines, journals, educational materials and scholarly publications,” said Dr. Jeff Jaffe, W3C CEO. “Working together, Publishing@W3C will bring exciting new capabilities and features to the future of publishing, authoring and reading using Web technologies.”

More than 75 organizations provided EPUB 3.1 Member Submission as a Member Submission to ensure that the EPUB 3.1 standard, developed by IDPF, remains royalty-free. To maintain EPUB and advance its further adoption, W3C is setting up a separate EPUB (3.1) Community Group that is free and open to anyone to participate.

A new Publishing Business Group will be the focal point for the community to address new needs and requirements and to serve as a forum for industry discussions. The Publishing@W3C roadmap includes plans to charter new standards work later this year to focus on both online as well as offline access for digital publications.

For more information read the press release.

(image)



CSS Snapshot 2017 Note Published

2017-02-21T07:36:02Z

The CSS Working Group has published a Group Note of CSS Snapshot 2017. This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2017. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not […](image)

The CSS Working Group has published a Group Note of CSS Snapshot 2017. This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2017. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.

(image)



W3C Invites Implementations of Cooperative Scheduling of Background Tasks

2017-02-09T09:53:09Z

The Web Performance Working Group invites implementation of the Candidate Recommendation of Cooperative Scheduling of Background Tasks. This document defines an API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, […](image)

The Web Performance Working Group invites implementation of the Candidate Recommendation of Cooperative Scheduling of Background Tasks. This document defines an API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations and frame compositing. The user agent is in a better position to determine when background tasks can be run without introducing user-perceptible delays or jank in animations and input response, based on its knowledge of currently scheduled tasks, vsync deadlines, user-interaction and so on. Using this API should therefore result in more appropriate scheduling of background tasks during times when the browser would otherwise be idle.

(image)



Data on the Web Best Practices are now a W3C Recommendation

2017-02-16T17:49:25Z

W3C is delighted to publish its Data on the Web Best Practices as a Recommendation. The document offers 35 Best Practices for sharing data, openly or not, in a way that maximizes the potential of the Web as a data platform rather than simply as a way to send data from A to B. The […](image)

(image) W3C is delighted to publish its Data on the Web Best Practices as a Recommendation. The document offers 35 Best Practices for sharing data, openly or not, in a way that maximizes the potential of the Web as a data platform rather than simply as a way to send data from A to B. The Best Practices are prescriptive in their intended outcomes but not in how those outcomes are achieved. They cover everything from the basics (provide metadata!) through nuance (provide structural metadata), to topics like licensing, provenance and basic information on providing APIs through to more advanced topics like data archiving, data enrichment and republishing data.

The work is complemented by two vocabularies, covering dataset usage and data quality, that were completed last year, and is also the basis of more specialist work in spatial data that is also nearing completion. See the blog for more background.

(image)



W3C Invites Implementations of Referrer Policy

2017-02-03T00:23:28Z

The Web Application Security Working Group invites implementations of the Candidate Recommendation of Referrer Policy. This specification describes how Web authors can set a referrer policy for documents they create, and describes the impact on the Referer HTTP header for outgoing requests and navigations.(image)

The Web Application Security Working Group invites implementations of the Candidate Recommendation of Referrer Policy. This specification describes how Web authors can set a referrer policy for documents they create, and describes the impact on the Referer HTTP header for outgoing requests and navigations.

(image)



The Web Cryptography API is a W3C Recommendation

2017-02-02T23:54:14Z

The Web Cryptography Working Group has published a W3C Recommendation of the Web Cryptography API. 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 […](image)

The Web Cryptography Working Group has published a W3C Recommendation of the Web Cryptography API. 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.

(image)



Two Notes Published by XMLQuery Working Group

2017-02-02T23:54:01Z

The XMLQuery Working Group has published two Group Notes: XQuery Update Facility 3.0. This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0. XQuery Update Facility 3.0 […](image)

The XMLQuery Working Group has published two Group Notes:

  • XQuery Update Facility 3.0. This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0.
  • XQuery Update Facility 3.0 Requirements and Use Cases: This document specifies goals, requirements and use cases for the XQuery Update Facility 3.0. XQuery 3.0: An XML Query Language provides queries but has no support for adding new values or changing existing values. The XML Query Working Group intends to add support for updates in a future version of XQuery. This document only contains requirements that have not been previously met by XQuery Update Facility 1.0.
(image)