The Web Payments Working Group is focusing on the payment transaction. There is an opportunity for future work on the commercial transaction of which the payment is just a part. When you use a credit card in a brick and mortar store, you are given the credit card transaction receipt and a receipt that lists what you purchased along with the associated terms and conditions. This is what you need to keep if you want to return the goods. There is an opportunity for work on standards for digital receipts that can be issued electronically at the time of purchase. One use case is when are checking out at a store and you are required to provide a receipt to prove that you purchased an item, that you are carrying, in another store. Another use case is to enable third party applications to have access to the digital receipts for your purchases, e.g. to provide categorised summaries on a monthly basis. One idea is to use annotated HTML to enable machine interpretation whilst giving the issuer control over the branding and look of the receipt.

This is related to other opportunities on loyalty schemes, discount coupons, and prepaid vouchers, tickets for events (e.g. concerts) and even for metropolitan transportation. A common thread is the idea of a digital wallet with open standards for data formats and APIs. This work could be picked up by the Web Payments Interest Group, but a good first step could be a W3C workshop to bring together a broad range of stakeholders to discuss the opportunities and see if there is sufficient interest to take these ideas further.

conversation with @philarcher1, cc @nitedog

From @tidoust on October 12, 2016 7:3

https://www.w3.org/2002/09/wbs/33280/wotwg2016/results

Copied from original issue: tidoust#11

The Second Screen CG started to discuss an Open Screen Protocol for the Presentation API and the Remote Playback API developed by the Second Screen WG. This would improve the interoperability of implementations of these APIs.

From @tidoust on October 12, 2016 6:57

https://www.w3.org/2002/09/wbs/33280/sswg-charter-2016/results

Copied from original issue: tidoust#4

There is a Community Group

There are many technical issues in presenting mathematics in today's Open Web Platform, which has led to the poor access to Mathematics in Web Pages. This is in spite of the existing de jure or de facto standards for authoring mathematics, like MathML, LaTeX, or asciimath, which have been around for a very long time and are widely used by the mathematical and technical communities.

While MathML was supposed to solve the problem of rendering mathematics on the web it lacks in both implementations and general interest from browser vendors. However, in the past decade, many math rendering tools have been pushing math on the web forward using HTML/CSS and SVG.

One of the identified issues is that, while browser manufacturers have continually improved and extended their HTML and CSS layout engines, the approaches to render mathematics have not been able to align with these improvements. In fact, the current approaches to math layout could be considered to be largely disjoint from the other technologies of OWP. Another key issue, is that exposing (and thus leveraging) semantic information of mathematical and scientific content on the web needs to move towards modern practices and standards instead of being limited to a single solution (MathML). Such information is critical for accessibility, machine-readability, and re-use of mathematical content.

This Community Group intends to look at the problems of math on the web in a very bottom-up manner. Experts in this group should identify how the core OWP layout engines, centered around HTML, SVG, and CSS, can be re-used for the purpose of mathematical layout by mapping mathematical entities on top of these, thereby ensuring a much more efficient result, and making use of current and future OWP optimization possibilities. Similarly, experts should work to identify best practices for semantics from the point of view of today's successful solutions.

Where do we focus when WebAuthn goes to Rec?

The Web Media API CG develops the Web Media APIs 2017 spec which "defines the Web APIs that should be included in device implementations to support media web apps in 2017".

https://www.ampproject.org/docs/reference/spec.html

From @tidoust on October 12, 2016 7:4

null

Copied from original issue: tidoust#13

The much talked about but yet to be implemented plans for creating the environment and processes necessary to enable community development and management of vocabularies at W3C.

https://www.w3.org/2002/09/wbs/33280/autowg-2016/results

From @tidoust on October 12, 2016 6:52

null

Copied from original issue: tidoust#3

From @tidoust on October 12, 2016 7:1

null

Copied from original issue: tidoust#5

There is a Community Group:

The mission of this group is to build a common, open format for the exchange of scholarly information.

This work may become important insofar as scholarly publishing might be one of the areas for some specific HTML or Web Publication profiles in the future.

test

See the Digital Offers CG
https://www.w3.org/community/digitaloffers/

From @tidoust on October 12, 2016 7:3

null

Copied from original issue: tidoust#10

See MLS vocab http://ml-schema.github.io/documentation/ML%20Schema.html from MLS CG https://www.w3.org/community/ml-schema/

Continue? Interact with WoT? So new charter with different deliverables?

https://pbos.github.io/mst-content-hint/

From the abstract:

[[
This specification extends MediaStreamTrack as defined in [GETUSERMEDIA] to provide an media-content hint attribute. This optional hint permits MediaStreamTrack consumers such as PeerConnection or MediaRecorder to encode or process contained media with methods more appropriate to the type of content that is being consumed.

Adding a media-content hint provides a way for an application to help track consumers make more informed decision of what encoder parameters and processing algorithms to use on the consumed content.
]]

The JSON-LD CG is re-energising itself to work on a version 1.1. See Greg's e-mail at https://lists.w3.org/Archives/Public/public-linked-json/2016Oct/0004.html for details. The transition of the Sem Web Interest Group to a CG means there's no immediately obvious route for the JSON-LD 1.1 work to get into /TR space - but we should probably find one, given the growing practical and strategic importance the technology .

There is a community group:

The Music Notation Community Group develops and maintains format and language specifications for notated music used by web, desktop, and mobile applications. The group aims to serve a broad range of users engaging in music-related activities involving notation, and will document these use cases.

The initial task of the Community Group is to maintain and update the MusicXML and SMuFL (Standard Music Font Layout) specifications. The goals are to evolve the specifications to handle new use cases and technologies, including greater use of music notation on the web, while maximizing the existing investment in implementations of the existing MusicXML 3.0 and SMuFL specifications.

They may come back to us at some point to try to get this notation through a WG

There is a community group

The goal of this CG is to develop specs to describe an object model for Publications (think EPUB, PDF, OOXML, and other complex friends) that hides the complexity of package, metadata and resource access inside those formats. A secondary goal is the development and release of a multi-purpose framework, in at least JavaScript and if possible c++ too, implementing those specs.

Though not verbatim, but the work may also be of interest for a future DPUB WG

Early conversations underway that could lead to profound advance in the way scientific research is shared and the Web is used to make connections. Currently way too early for any detail but potential is substantial.

Early conversations underway that could lead to profound advance in the way scientific research is shared and the Web is used to make connections. Currently way too early for any detail but potential is substantial.

Rechartering WebSec IG. Charter expired in June 2016. Planning to recharter for two years, adding two additional co-chairs.

TPAC breakout report

CG: https://www.w3.org/community/hb-secure-services/
CG Report: https://rawgit.com/w3c/websec/gh-pages/hbss.html

From @tidoust on October 12, 2016 7:3

null

Copied from original issue: tidoust#8

How should we track items that incubate in WICG?
https://github.com/WICG/admin/wiki/stats lists many

From @tidoust on October 12, 2016 7:4

https://www.w3.org/2002/09/wbs/33280/audio-2016/results à cette carte

Copied from original issue: tidoust#12

https://www.w3.org/2016/04/blockchain-workshop/

Geolocation want to move some of their deliverables to Device & Sensor WG.

From @tidoust on October 12, 2016 7:3

null

Copied from original issue: tidoust#9

The Multi-Device Timing CG has been discussing single- and cross-device synchronization issues and possible improvements to existing algorithms that deal with time.

The Timing Object spec proposes to expose a "local object that may be used by Web clients to ensure precisely timed operation as well as flexible timing control".

From @tidoust on October 12, 2016 6:50

https://www.w3.org/2016/11/sdsvoc/

Copied from original issue: tidoust#2

From @tidoust on October 12, 2016 6:49

null

Copied from original issue: tidoust#1

http://webassembly.org/roadmap/

Status says: The WebAssembly Community Group has an initial (MVP) binary format release candidate and JavaScript API which are implemented in several browsers. The CG is now soliciting feedback from the broader community as part of a Browser Preview period. The tentative goal of the CG is for the Browser Preview to conclude in Q1 2017, though significant findings during the Browser Preview could potentially extend the duration. When the Browser Preview concludes, the CG will produce a draft specification of WebAssembly and browser vendors can start to ship conforming implementations on-by-default.

The Media Resource In-band Tracks CG developed the Sourcing In-band Media Resource Tracks from Media Containers into HTML spec, informatively referenced by HTML5.

Specification is useful to media companies, but has no official standing and probably needs to be completed.

Web browsers can be used to provide user interfaces for services for the Web of Things. This can be implemented using JavaScript and the browser supported protocols (HTTP, WebSockets, WebRTC). There is a further opportunity for using Web browsers for installing apps onto your smart home hub when visiting a vendor's website. This raises challenges around how the browser identifies the home hub, and gets the user's permission for installing the app, along with the associated security and privacy concerns. I am expecting home hubs that support apps written in JavaScript, and this raises opportunities for re-use of browser APIs on home hubs. This will require incubation, but a first step could be a workshop that looks at web of things related work across different groups as well as the expected need for new standards. A workshop would bring together people from different communities and help prepare the ground for further collaboration.

Web Bluetooth describes an API to discover and communicate with devices over the Bluetooth 4 wireless standard using the Generic Attribute Profile (GATT).