Today’s @tag meeting:
An in-depth discussion of proposed hrefTranslate, for a referring page to hint to the browser/UA that the user is likely to want it to translate the next page into a particular language.
Use cases include: Google Translate, which will assume you want the site you’re clicking on to be translated.
Thanks to @firstname.lastname@example.org & @email@example.com for joining us!
Today's @tag meeting included:
Triaging a load of new reviews:
• MathML Core
• Get Installed Related Apps
• Serial API*
*sadly, not cereal API. We got excited about breakfast delivery... ah well.
On pathologist Alice Hamilton (1869–1970)
“She felt it was one thing to get data & do good science but then you weren’t really finished unless something happened…unless you could use that knowledge to improve labor standards & other [necessary] things.”
Today’s @tag meeting included:
• Should a site have access to your copy/paste clipboard? What action should you take before it can read whatever you last copied?
• Proposed updates to the TAG’s Ethical Web Principles
RT @NHSX@twitter.com Thanks to @firstname.lastname@example.org for inviting @hadleybeeman to share thoughts on the first 100 days and where next for NHSX.
Scale, standards, staff up
Today’s @tag meeting included:
• enterKeyHint, so sites can customise a virtual keyboard’s Enter key to do what a user expects… like send content, search, insert a new line (like android/iOS apps do)
• Many different types of manifests — too many?
This is hilariously bad. And plausible.
“I read your article on B-cell function. I think I could use the data for my work on pancreatic cancer.”
“Everything you need is in the article.”
“No, what I need is the data.”
“I’m not sure that is possible…”
And we’re back with our weekly @w3ctag meetings, after TPAC & our face-to-face meeting in Tokyo.
Today’s included discussions on:
• Raw Clipboard Access API
• CSS Modules
• File Handling
• JS Self-Profiling API
• Reviving the HTML Design Principles
• driving forward NHSX’s £400m cyber security transformation programme
• long-term planning for emerging threats
• developing NHSX’s strategy for developing capability and expertise in the NHS
• resilience & incident response for NHS/social care
Minutes from what we've learned and what new work we're taking on:
I'm starting day 5 (final day! Always a sad moment) of #w3ctpac with a joint @wicg_ / @w3ctag meeting, working out how/when we the TAG can best help with early, incubating ideas for features for the web.
I'm with the JSON-LD working group, who are looking for ways to represent text using languages that are both left-to-right (like English) and right-to-left (like Arabic).
.@ChromiumDev@twitter.com's 2nd proposal:
PIGIN: The browser joins me as user to an "interest group" to tell advertisers what we might respond to–based on something it saw me do, like put an item into a shopping cart
More concerns on how much info on "me as user" may be detectable.
This is what the W3C Web Payments Working Group are up to:
• Payment Request API
• Payment Method IDs
• Basic Card Payment
• Payment Handler API
• Payment Method Manifest
• Web Payments Overview
Well into day 1 of
Technical Plenary and Advisory Group meeting in Fukuoka, Japan. #w3cTPAC
This AM, we
members divided up the agenda, to see where we can help/learn most.
I'm now dropping into Web Payments Working Group: https://github.com/w3c/webpayments/wiki/FTF-Agenda-201909
Architect for #openstandards & the Web. Advisor on tech policy. Co-founder of
. Data & security geek. Active in NHS, UK gov and W3C; views mine.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!