The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Regions Module Level 1.
The CSS Regions module allows content from one or more elements to flow
through one or more boxes called CSS Regions, fragmented as defined in
CSS3-BREAK. This module also defines CSSOM to expose both the inputs and
outputs of this fragmentation. CSS is a language for describing the
rendering of structured documents (such as HTML and XML) on screen, on
paper, in speech, etc. Learn more about the Style Activity.
Search Engine Marketing| seo tips | w3c Release | Unlock the secrets of SEO success and W3C standards mastery on our blog. Elevate your online presence with expert insights, staying visible and accessible
Friday, October 10, 2014
Last Call: XQuery 3.1 and XQueryX 3.1; and additional supporting documents
Today the XQuery Working Group published a Last Call Working Draft of XQuery 3.1 and XQueryX 3.1. Additional supporting documents were published jointly with the XSLT Working Group: a Last Call Working Draft of XPath 3.1, together with XPath Functions and Operators, XQuery and XPath Data Model, and XSLT and XQuery Serialization.
XQuery 3.1 and XPath 3.1 introduce improved support for working with
JSON data with map and array data structures as well as loading and
serializing JSON; additional support for HTML class attributes, HTTP
dates, scientific notation, cross-scaling between XSLT and XQuery and
more. Comments are welcome through 7 November 2014. Learn more about the XML Activity.
Selection API First Public Draft Published; Push API Draft Published
The Web Applications Working Group has published two documents today:
- A First Public Working Draft of Selection API. This document is a preliminary draft of a specification for the Selection API and selection related functionality. It replaces a couple of old sections of the HTML specification, the selection part of the old DOM Range specification.
- A Working Draft of Push API. The Push API provides webapps with scripted access to server-sent messages, for simplicity referred to here as push messages, as delivered by push services. A push service allows a webapp server to send messages to a webapp, regardless of whether the webapp is currently active on the user agent. The push message will be delivered to a Service Worker, which could then store the message’s data or display a notification to the user. This specification is designed to promote compatibility with any delivery method for push messages from push services to user agents.
Subscribe to:
Posts (Atom)