W3C Strategic Highlights September 2019 This report was prepared for the September 2019 W3C Advisory Committee Meeting (W3C Member link). See the accompanying W3C Fact Sheet — September 2019. For the previous edition, see the April 2019 W3C Strategic Highlights. For future editions of this report, please consult the latest version. A Chinese translation is available. ☰ Contents Introduction Future Web Standards Meeting Industry Needs Web Payments Digital Publishing Media and Entertainment Web & Telecommunications Real-Time Communications (WebRTC) Web & Networks Automotive Web of Things Strengthening the Core of the Web HTML CSS Fonts SVG Audio Performance Web Performance WebAssembly Testing Browser Testing and Tools WebPlatform Tests Web of Data Web for All Security, Privacy, Identity Internationalization (i18n) Web Accessibility Outreach to the world W3C Developer Relations W3C Training Translations W3C Liaisons Introduction This report highlights recent work of enhancement of the existing landscape of the Web platform and innovation for the growth and strength of the Web. 33 working groups and a dozen interest groups enable W3C to pursue its mission through the creation of Web standards, guidelines, and supporting materials. We track the tremendous work done across the Consortium through homogeneous work-spaces in Github which enables better monitoring and management. We are in the middle of a period where we are chartering numerous working groups which demonstrate the rapid degree of change for the Web platform: After 4 years, we are nearly ready to publish a Payment Request API Proposed Recommendation and we need to soon charter follow-on work. In the last year we chartered the Web Payment Security Interest Group. In the last year we chartered the Web Media Working Group with 7 specifications for next generation Media support on the Web. We have Accessibility Guidelines under W3C Member review which includes Silver, a new approach. We have just launched the Decentralized Identifier Working Group which has tremendous potential because Decentralized Identifier (DID) is an identifier that is globally unique, resolveable with high availability, and cryptographically verifiable. We have Privacy IG (PING) under W3C Member review which strengthens our focus on the tradeoff between privacy and function. We have a new CSS charter under W3C Member review which maps the group's work for the next three years. In this period, W3C and the WHATWG have succesfully completed the negotiation of a Memorandum of Understanding rooted in the mutual belief that that having two distinct specifications claiming to be normative is generally harmful for the Web community. The MOU, signed last May, describes how the two organizations are to collaborate on the development of a single authoritative version of the HTML and DOM specifications. W3C subsequently rechartered the HTML Working Group to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and for the production of W3C Recommendations from WHATWG Review Drafts. As the Web evolves continuously, some groups are looking for ways for specifications to do so as well. So-called "evergreen recommendations" or "living standards" aim to track continuous development (and maintenance) of features, on a feature-by-feature basis, while getting review and patent commitments. We see the maturation and further development of an incredible number of new technologies coming to the Web. Continued progress in many areas demonstrates the vitality of the W3C and the Web community, as the rest of the report illustrates. Future Web Standards W3C has a variety of mechanisms for listening to what the community thinks could become good future Web standards. These include discussions with the Membership, discussions with other standards bodies, the activities of thousands of participants in over 300 community groups, and W3C Workshops. There are lots of good ideas. The W3C strategy team has been identifying promising topics and invites public participation. Future, recent and under consideration Workshops include: Inclusive XR (5-6 November 2019, Seattle, WA, USA) to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive, including to people with disabilities; W3C Workshop on Data Models for Transportation (12-13 September 2019, Palo Alto, CA, USA) W3C Workshop on Web Games (27-28 June 2019, Redmond, WA, USA), view report Second W3C Workshop on the Web of Things (3-5 June 2019, Munich, Germany) W3C Workshop on Web Standardization for Graph Data; Creating Bridges: RDF, Property Graph and SQL (4-6 March 2019, Berlin, Germany), view report Web & Machine Learning. The Strategy Funnel documents the staff's exploration of potential new work at various phases: Exploration and Investigation, Incubation and Evaluation, and eventually to the chartering of a new standards group. The Funnel view is a GitHub Project where new area are issues represented by “cards” which move through the columns, usually from left to right. Most cards start in Exploration and move towards Chartering, or move out of the funnel. Public input is welcome at any stage but particularly once Incubation has begun. This helps W3C identify work that is sufficiently incubated to warrant standardization, to review the ecosystem around the work and indicate interest in participating in its standardization, and then to draft a charter that reflects an appropriate scope. Ongoing feedback can speed up the overall standardization process. Since the previous highlights document, W3C has chartered a number of groups, and started discussion on many more: Newly Chartered or Rechartered Web Application Security WG (03-Apr) Web Payment Security IG (17-Apr) Patent and Standards IG (24-Apr) Web Applications WG (14-May) Web & Networks IG (16-May) Media WG (23-May) Media and Entertainment IG (06-Jun) HTML WG (06-Jun) Decentralized Identifier WG (05-Sep) Extended Privacy IG (PING) (30-Sep) Verifiable Claims WG (30-Sep) Service Workers WG (31-Dec) Dataset Exchange WG (31-Dec) Web of Things Working Group (31-Dec) Web Audio Working Group (31-Dec) Proposed charters / Advance Notice Accessibility Guidelines WG Privacy IG (PING) RDF Literal Direction WG Timed Text WG CSS WG Web Authentication WG Closed Internationalization Tag Set IG Meeting Industry Needs Web Payments All Web Payments specifications W3C's payments standards enable a streamlined checkout experience, enabling a consistent user experience across the Web with lower front end development costs for merchants. Users can store and reuse information and more quickly and accurately complete online transactions. The Web Payments Working Group has republished Payment Request API as a Candidate Recommendation, aiming to publish a Proposed Recommendation in the Fall 2019, and is discussing use cases and features for Payment Request after publication of the 1.0 Recommendation. Browser vendors have been finalizing implementation of features added in the past year (view the implementation report). As work continues on the Payment Handler API and its implementation (currently in Chrome and Edge Canary), one focus in 2019 is to increase adoption in other browsers. Recently, Mastercard demonstrated the use of Payment Request API to carry out EMVCo's Secure Remote Commerce (SRC) protocol whose payment method definition is being developed with active participation by Visa, Mastercard, American Express, and Discover. Payment method availability is a key factor in merchant considerations about adopting Payment Request API. The ability to get uniform adoption of a new payment method such as Secure Remote Commerce (SRC) also depends on the availability of the Payment Handler API in browsers, or of proprietary alternatives. Web Monetization, which the Web Payments Working Group will discuss again at its face-to-face meeting in September, can be used to enable micropayments as an alternative revenue stream to advertising. Since the beginning of 2019, Amazon, Brave Software, JCB, Certus Cybersecurity Solutions and Netflix have joined the Web Payments Working Group. In April, W3C launched the Web Payment Security Group to enable W3C, EMVCo, and the FIDO Alliance to collaborate on a vision for Web payment security and interoperability. Participants will define areas of collaboration and identify gaps between existing technical specifications in order to increase compatibility among different technologies, such as: How do SRC, FIDO, and Payment Request relate? The Payment Services Directive 2 (PSD2) regulations in Europe are scheduled to take effect in September 2019. What is the role of EMVCo, W3C, and FIDO technologies, and what is the current state of readiness for the deadline? How can we improve privacy on the Web at the same time as we meet industry requirements regarding user identity? Digital Publishing All Digital Publishing specifications, Publication milestones The Web is the universal publishing platform. Publishing is increasingly impacted by the Web, and the Web increasingly impacts Publishing. Topic of particular interest to Publishing@W3C include typography and layout, accessibility, usability, portability, distribution, archiving, offline access, print on demand, and reliable cross referencing. And the diverse publishing community represented in the groups consist of the traditional "trade" publishers, ebook reading system manufacturers, but also publishers of audio book, scholarly journals or educational materials, library scientists or browser developers. The Publishing Working Group currently concentrates on Audiobooks which lack a comprehensive standard, thus incurring extra costs and time to publish in this booming market. Active development is ongoing on the future standard: Publication Manifest Audiobook profile for Web Publications Lightweight Packaging Format The BD Comics Manga Community Group, the Synchronized Multimedia for Publications Community Group, the Publishing Community Group and a future group on archival, are companions to the working group where specific work is developed and incubated. The Publishing Community Group is a recently launched incubation channel for Publishing@W3C. The goal of the group is to propose, document, and prototype features broadly related to: publications on the Web reading modes and systems and the user experience of publications The EPUB 3 Community Group has successfully completed the revision of EPUB 3.2. The Publishing Business Group fosters ongoing participation by members of the publishing industry and the overall ecosystem in the development of Web infrastructure to better support the needs of the industry. The Business Group serves as an additional conduit to the Publishing Working Group and several Community Groups for feedback between the publishing ecosystem and W3C. The Publishing BG has played a vital role in fostering and advancing the adoption and continued development of EPUB 3. In particular the BG provided critical support to the update of EPUBCheck to validate EPUB content to the new EPUB 3.2 specification. This resulted in the development, in conjunction with the EPUB3 Community Group, of a new generation of EPUBCheck, i.e., EPUBCheck 4.2 production-ready release. Media and Entertainment All Media specifications The Media and Entertainment vertical tracks media-related topics and features that create immersive experiences for end users. HTML5 brought standard audio and video elements to the Web. Standardization activities since then have aimed at turning the Web into a professional platform fully suitable for the delivery of media content and associated materials, enabling missing features to stream video content on the Web such as adaptive streaming and content protection. Together with Microsoft, Comcast, Netflix and Google, W3C received an Technology & Engineering Emmy Award in April 2019 for standardization of a full TV experience on the Web. Current goals are to: Reinforce core media technologies: Creation of the Media Working Group, to develop media-related specifications incubated in the WICG (e.g. Media Capabilities, Picture-in-picture, Media Session) and maintain maintain/evolve Media Source Extensions (MSE) and Encrypted Media Extensions (EME). Improve support for Media Timed Events: data cues incubation. Enhance color support (HDR, wide gamut), in scope of the CSS WG and in the Color on the Web CG. Reduce fragmentation: Continue annual releases of a common and testable baseline media devices, in scope of the Web Media APIs CG and in collaboration with the CTA WAVE Project. Maintain the Road-map of Media Technologies for the Web which highlights Web technologies that can be used to build media applications and services, as well as known gaps to enable additional use cases. Create the future: Discuss perspectives for Media and Entertainment for the Web. Bring the power of GPUs to the Web (graphics, machine learning, heavy processing), under incubation in the GPU for the Web CG. Transition to a Working Group is under discussion. Determine next steps after the successful W3C Workshop on Web Games of June 2019. View the report. Timed Text The Timed Text Working Group develops and maintains formats used for the representation of text synchronized with other timed media, like audio and video, and notably works on TTML, profiles of TTML, and WebVTT. Recent progress includes: A robust WebVTT implementation report poises the specification for publication as a proposed recommendation. Discussions around re-chartering, notably to add a TTML Profile for Audio Description deliverable to the scope of the group, and clarify that rendering of captions within XR content is also in scope. Immersive Web Hardware that enables Virtual Reality (VR) and Augmented Reality (AR) applications are now broadly available to consumers, offering an immersive computing platform with both new opportunities and challenges. The ability to interact directly with immersive hardware is critical to ensuring that the web is well equipped to operate as a first-class citizen in this environment. The Immersive Web Working Group has been stabilizing the WebXR Device API while the companion Immersive Web Community Group incubates the next series of features identified as key for the future of the Immersive Web. W3C plans a workshop focused on the needs and benefits at the intersection of VR & Accessibility (Inclusive XR), on 5-6 November 2019 in Seattle, WA, USA, to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive. Web & Telecommunications The Web is the Open Platform for Mobile. Telecommunication service providers and network equipment providers have long been critical actors in the deployment of Web technologies. As the Web platform matures, it brings richer and richer capabilities to extend existing services to new users and devices, and propose new and innovative services. Real-Time Communications (WebRTC) All Real-Time Communications specifications WebRTC has reshaped the whole communication landscape by making any connected device a potential communication end-point, bringing audio and video communications anywhere, on any network, vastly expanding the ability of operators to reach their customers. WebRTC serves as the corner-stone of many online communication and collaboration services. The WebRTC Working Group aims to bringing WebRTC 1.0 (and companion specification Media Capture and Streams) to Recommendation by the end of 2019. Intense efforts are focused on testing (supported by a dedicated hackathon at IETF 104) and interoperability. The group is considering pushing features that have not gotten enough traction to separate modules or to a later minor revision of the spec. Beyond WebRTC 1.0, the WebRTC Working Group will focus its efforts on WebRTC NV which the group has started documenting by identifying use cases. Web & Networks Recently launched, in the wake of the May 2018 Web5G workshop, the Web & Networks Interest Group is chaired by representatives from AT&T, China Mobile and Intel, with a goal to explore solutions for web applications to achieve better performance and resource allocation, both on the device and network. The group's first efforts are around use cases, privacy & security requirements and liaisons. Automotive All Automotive specifications To create a rich application ecosystem for vehicles and other devices allowed to connect to the vehicle, the W3C Automotive Working Group is delivering a service specification to expose all common vehicle signals (engine temperature, fuel/charge level, range, tire pressure, speed, etc.) The Vehicle Information Service Specification (VISS), which is a Candidate Recommendation, is seeing more implementations across the industry. It provides the access method to a common data model for all the vehicle signals –presently encapsulating a thousand or so different data elements– and will be growing to accommodate the advances in automotive such as autonomous and driver assist technologies and electrification. The group is already working on a successor to VISS, leveraging the underlying data model and the VIWI submission from Volkswagen, for a more robust means of accessing vehicle signals information and the same paradigm for other automotive needs including location-based services, media, notifications and caching content. The Automotive and Web Platform Business Group acts as an incubator for prospective standards work. One of its task forces is using W3C VISS in performing data sampling and off-boarding the information to the cloud. Access to the wealth of information that W3C's auto signals standard exposes is of interest to regulators, urban planners, insurance companies, auto manufacturers, fleet managers and owners, service providers and others. In addition to components needed for data sampling and edge computing, capturing user and owner consent, information collection methods and handling of data are in scope. The upcoming W3C Workshop on Data Models for Transportation (September 2019) is expected to focus on the need of additional ontologies around transportation space. Web of Things All Web of Things specifications W3C's Web of Things work is designed to bridge disparate technology stacks to allow devices to work together and achieve scale, thus enabling the potential of the Internet of Things by eliminating fragmentation and fostering interoperability. Thing descriptions expressed in JSON-LD cover the behavior, interaction affordances, data schema, security configuration, and protocol bindings. The Web of Things complements existing IoT ecosystems to reduce the cost and risk for suppliers and consumers of applications that create value by combining multiple devices and information services. There are many sectors that will benefit, e.g. smart homes, smart cities, smart industry, smart agriculture, smart healthcare and many more. The Web of Things Working Group is finishing the initial Web of Things standards, with support from the Web of Things Interest Group: Web of Things Architecture Thing Descriptions Strengthening the Core of the Web HTML The HTML Working Group was chartered early June to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and to produce W3C Recommendations from WHATWG Review Drafts. A few days before, W3C and the WHATWG signed a Memorandum of Understanding outlining the agreement to collaborate on the development of a single version of the HTML and DOM specifications. Issues and proposed solutions for HTML and DOM done via the newly rechartered HTML Working Group in the WHATWG repositories The HTML Working Group is targetting November 2019 to bring HTML and DOM to Candidate Recommendations. CSS All CSS specifications CSS is a critical part of the Open Web Platform. The CSS Working Group gathers requirements from two large groups of CSS users: the publishing industry and application developers. Within W3C, those groups are exemplified by the Publishing groups and the Web Platform Working Group. The former requires things like better pagination support and advanced font handling, the latter needs intelligent (and fast!) scrolling and animations. What we know as CSS is actually a collection of almost a hundred specifications, referred to as ‘modules’. The current state of CSS is defined by a snapshot, updated once a year. The group also publishes an index defining every term defined by CSS specifications. Fonts All Fonts specifications The Web Fonts Working Group develops specifications that allow the interoperable deployment of downloadable fonts on the Web, with a focus on Progressive Font Enrichment as well as maintenance of WOFF Recommendations. Recent and ongoing work includes: Early API experiments by Adobe and Monotype have demonstrated the feasibility of a font enrichment API, where a server delivers a font with minimal glyph repertoire and the client can query the full repertoire and request additional subsets on-the-fly. In other experiments, the Brotli compression used in WOFF 2 was extended to support shared dictionaries and patch update. Metrics to quantify improvement are a current hot discussion topic. The group will meet at ATypi 2019 in Japan, to gather requirements from the international typography community. The group will first produce a report summarizing the strengths and weaknesses of each prototype solution by Q2 2020. SVG All SVG specifications SVG is an important and widely-used part of the Open Web Platform. The SVG Working Group focuses on aligning the SVG 2.0 specification with browser implementations, having split the specification into a currently-implemented 2.0 and a forward-looking 2.1. Current activity is on stabilization, increased integration with the Open Web Platform, and test coverage analysis. The Working Group was rechartered in March 2019. A new work item concerns native (non-Web-browser) uses of SVG as a non-interactive, vector graphics format. Audio The Web Audio Working Group was extended to finish its work on the Web Audio API, expecting to publish it as a Recommendation by year end. The specification enables synthesizing audio in the browser. Audio operations are performed with audio nodes, which are linked together to form a modular audio routing graph. Multiple sources — with different types of channel layout — are supported. This modular design provides the flexibility to create complex audio functions with dynamic effects. The first version of Web Audio API is now feature complete and is implemented in all modern browsers. Work has started on the next version, and new features are being incubated in the Audio Community Group. Performance Web Performance All Web Performance specifications There are currently 18 specifications in development in the Web Performance Working Group aiming to provide methods to observe and improve aspects of application performance of user agent features and APIs. The W3C team is looking at related work incubated in the W3C GPU for the Web (WebGPU) Community Group which is poised to transition to a W3C Working Group. A preliminary draft charter is available. WebAssembly All WebAssembly specifications WebAssembly improves Web performance and power by being a virtual machine and execution environment enabling loaded pages to run native (compiled) code. It is deployed in Firefox, Edge, Safari and Chrome. The specification will soon reach Candidate Recommendation. WebAssembly enables near-native performance, optimized load time, and perhaps most importantly, a compilation target for existing code bases. While it has a small number of native types, much of the performance increase relative to Javascript derives from its use of consistent typing. WebAssembly leverages decades of optimization for compiled languages and the byte code is optimized for compactness and streaming (the web page starts executing while the rest of the code downloads). Network and API access all occurs through accompanying Javascript libraries -- the security model is identical to that of Javascript. Requirements gathering and language development occur in the Community Group while the Working Group manages test development, community review and progression of specifications on the Recommendation Track. Testing Browser testing plays a critical role in the growth of the Web by: Improving the reliability of Web technology definitions; Improving the quality of implementations of these technologies by helping vendors to detect bugs in their products; Improving the data available to Web developers on known bugs and deficiencies of Web technologies by publishing results of these tests. Browser Testing and Tools The Browser Testing and Tools Working Group is developing WebDriver version 2, having published last year the W3C Recommendation of WebDriver. WebDriver acts as a remote control interface that enables introspection and control of user agents, provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behavior of Web, and emulates the actions of a real person using the browser. WebPlatform Tests The WebPlatform Tests project now provides a mechanism which allows to fully automate tests that previously needed to be run manually: TestDriver. TestDriver enables sending trusted key and mouse events, sending complex series of trusted pointer and key interactions for things like in-content drag-and-drop or pinch zoom, and even file upload. Since 2014 W3C began work on this coordinated open-source effort to build a cross-browser test suite for the Web Platform, which WHATWG, and all major browsers adopted. Web of Data All Data specifications There have been several great success stories around the standardization of data on the web over the past year. Verifiable Claims seems to have significant uptake. It is also significant that the Distributed Identifier WG charter has received numerous favorable reviews, and was just recently launched. JSON-LD has been a major success with the large deployment on Web sites via schema.org. JSON-LD 1.1 completed technical work, about to transition to CR More than 25% of websites today include schema.org data in JSON-LD The Web of Things description is in CR since May, making use of JSON-LD Verifiable Credentials data model is in CR since July, also making use of JSON-LD Continued strong interest in decentralized identifiers Engagement from the TAG with reframing core documents, such as Ethical Web Principles, to include data on the web within their scope Data is increasingly important for all organizations, especially with the rise of IoT and Big Data. W3C has a mature and extensive suite of standards relating to data that were developed over two decades of experience, with plans for further work on making it easier for developers to work with graph data and knowledge graphs. Linked Data is about the use of URIs as names for things, the ability to dereference these URIs to get further information and to include links to other data. There are ever-increasing sources of open Linked Data on the Web, as well as data services that are restricted to the suppliers and consumers of those services. The digital transformation of industry is seeking to exploit advanced digital technologies. This will facilitate businesses to integrate horizontally along the supply and value chains, and vertically from the factory floor to the office floor. W3C is seeking to make it easier to support enterprise-wide data management and governance, reflecting the strategic importance of data to modern businesses. Traditional approaches to data have focused on tabular databases (SQL/RDBMS), Comma Separated Value (CSV) files, and data embedded in PDF documents and spreadsheets. We're now in midst of a major shift to graph data with nodes and labeled directed links between them. Graph data is: Faster than using SQL and associated JOIN operations More favorable to integrating data from heterogeneous sources Better suited to situations where the data model is evolving In the wake of the recent W3C Workshop on Graph Data we are in the process of launching a Graph Standardization Business Group to provide a business perspective with use cases and requirements, to coordinate technical standards work and liaisons with external organizations. Web for All Security, Privacy, Identity All Security specifications, all Privacy specifications Authentication on the Web As the WebAuthn Level 1 W3C Recommendation published last March is seeing wide implementation and adoption of strong cryptographic authentication, work is proceeding on Level 2. The open standard Web API gives native authentication technology built into native platforms, browsers, operating systems (including mobile) and hardware, offering protection against hacking, credential theft, phishing attacks, thus aiming to end the era of passwords as a security construct. You may read more in our March press release. Privacy An increasing number of W3C specifications are benefitting from Privacy and Security review; there are security and privacy aspects to every specification. Early review is essential. Working with the TAG, the Privacy Interest Group has updated the Self-Review Questionnaire: Security and Privacy. Other recent work of the group includes public blogging further to the exploration of anti-patterns in standards and permission prompts. Security The Web Application Security Working Group adopted Feature Policy, aiming to allow developers to selectively enable, disable, or modify the behavior of some of these browser features and APIs within their application; and Fetch Metadata, aiming to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used. The Web Payment Security Interest Group, launched last April, convenes members from W3C, EMVCo, and the FIDO Alliance to discuss cooperative work to enhance the security and interoperability of Web payments (read more about payments). Internationalization (i18n) All Internationalization specifications, educational articles related to Internationalization, spec developers checklist Only a quarter or so current Web users use English online and that proportion will continue to decrease as the Web reaches more and more communities of limited English proficiency. If the Web is to live up to the "World Wide" portion of its name, and for the Web to truly work for stakeholders all around the world engaging with content in various languages, it must support the needs of worldwide users as they engage with content in the various languages. The growth of epublishing also brings requirements for new features and improved typography on the Web. It is important to ensure the needs of local communities are captured. The W3C Internationalization Initiative was set up to increase in-house resources dedicated to accelerating progress in making the World Wide Web "worldwide" by gathering user requirements, supporting developers, and education & outreach. For an overview of current projects see the i18n radar. W3C's Internationalization efforts progressed on a number of fronts recently: Requirements: New African and European language groups will work on the gap analysis, errata and layout requirements. Gap analysis: Japanese, Devanagari, Bengali, Tamil, Lao, Khmer, Javanese, and Ethiopic updated in the gap-analysis documents. Layout requirements document: notable progress tracked in the Southeast Asian Task Force while work continues on Chinese layout requirements. Developer support: Spec reviews: the i18n WG continues active review of specifications of the WHATWG and other W3C Working Groups. Short review checklist: easy way to begin a self-review to help spec developers understand what aspects of their spec are likely to need attention for internationalization, and points them to more detailed checklists for the relevant topics. It also helps those reviewing specs for i18n issues. Strings on the Web: Language and Direction Metadata lays out issues and discusses potential solutions for passing information about language and direction with strings in JSON or other data formats. The document was rewritten for clarity, and expanded. The group is collaborating with the JSON-LD and Web Publishing groups to develop a plan for updating RDF, JSON-LD and related specifications to handle metadata for base direction of text (bidi). User-friendly test format: a new format was developed for Internationalization Test Suite tests, which displays helpful information about how the test works. This particularly useful because those tests are pointed to by educational materials and gap-analysis documents. Web Platform Tests: a large number of tests in the i18n test suite have been ported to the WPT repository, including: css-counter-styles, css-ruby, css-syntax, css-test, css-text-decor, css-writing-modes, and css-pseudo. Education & outreach: (for all educational materials, see the HTML & CSS Authoring Techniques) Web Accessibility All Accessibility specifications, WAI resources The Web Accessibility Initiative supports W3C's Web for All mission. Recent achievements include: Education and training: Inaccessibility of CAPTCHA updated to bring our analysis and recommendations up to date with CAPTCHA practice today, concluding two years of extensive work and invaluable input from the public (read more on the W3C Blog Learn why your web content and applications should be accessible. The Education and Outreach Working Group has completed revision and updating of the Business Case for Digital Accessibility. Accessibility guidelines: The Accessibility Guidelines Working Group has continued to update WCAG Techniques and Understanding WCAG 2.1; and published a Candidate Recommendation of Accessibility Conformance Testing Rules Format 1.0 to improve inter-rater reliability when evaluating conformance of web content to WCAG An updated charter is being developed to host work on "Silver", the next generation accessibility guidelines (WCAG 2.2) There are accessibility aspects to most specifications. Check your work with the FAST checklist. Outreach to the world W3C Developer Relations To foster the excellent feedback loop between Web Standards development and Web developers, and to grow participation from that diverse community, recent W3C Developer Relations activities include: @w3cdevs tracks the enormous amount of work happening across W3C W3C Track during the Web Conference 2019 in San Francisco Tech videos: W3C published the 2019 Web Games Workshop videos The 16 September 2019 Developer Meetup in Fukuoka, Japan, is open to all and will combine a set of technical demos prepared by W3C groups, and a series of talks on a selected set of W3C technologies and projects W3C is involved with Mozilla, Google, Samsung, Microsoft and Bocoup in the organization of ViewSource 2019 in Amsterdam (read more on the W3C Blog) W3C Training In partnership with EdX, W3C's MOOC training program, W3Cx offers a complete "Front-End Web Developer" (FEWD) professional certificate program that consists of a suite of five courses on the foundational languages that power the Web: HTML5, CSS and JavaScript. We count nearly 900K students from all over the world. Translations Many Web users rely on translations of documents developed at W3C whose official language is English. W3C is extremely grateful to the continuous efforts of its community in ensuring our various deliverables in general, and in our specifications in particular, are made available in other languages, for free, ensuring their exposure to a much more diverse set of readers. Last Spring we developed a more robust system, a new listing of translations of W3C specifications and updated the instructions on how to contribute to our translation efforts. W3C Liaisons Liaisons and coordination with numerous organizations and Standards Development Organizations (SDOs) is crucial for W3C to: make sure standards are interoperable coordinate our respective agenda in Internet governance: W3C participates in ICANN, GIPO, IGF, the I* organizations (ICANN, IETF, ISOC, IAB). ensure at the government liaison level that our standards work is officially recognized when important to our membership so that products based on them (often done by our members) are part of procurement orders. W3C has ARO/PAS status with ISO. W3C participates in the EU MSP and Rolling Plan on Standardization ensure the global set of Web and Internet standards form a compatible stack of technologies, at the technical and policy level (patent regime, fragmentation, use in policy making) promote Standards adoption equally by the industry, the public sector, and the public at large Coralie Mercier, Editor, W3C Marketing & Communications $Id: Overview.html,v 1.60 2019/10/15 12:05:52 coralie Exp $ Copyright © 2019 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.

Welcome to bear market of 2022. We aren't just talking about cryptocurrency, literally ever market seems to be in tank. The war in Ukraine, high gas prices, and continuation of high inflation is plaguing our economy. At this point, it is almost too late to do anything. The monthly FOMC meetings have brought new regulation to the markets. The big question though is it enough? The US national debt at time of writing is flirting just under $100 trillion. Let that sink in for a second. To give you a scale of how much money that is, to make $1 million you would have to make a dollar every second for 10 days straight. To make $1 billion, you would have to make a dollar every second for almost 32 years. Now this is where it gets crazy, to make $1 trillion, you would have to make a dollar every second for 31,709.79 years. We have more debt than we could ever pay back. But what caused this debt? Debt in itself is kind of an interesting topic. A lot of the world's debt has to deal with credit and interest rates. We as people use credit and loans to obtain assets. Some debt is good, while other debt is bad. At the end of the day credit is necessary for everyone to have. It is a way that the banks can judge you as a person financially. Just because someone is nice in character, doesn't mean they know how to manage a check book or a bank account. These types of under the hood details are important when running a business or buying a house or car. The lenders need to make sure that you personally are not a bad investment, and that they will get their money back. Due to interest rates, money is deposited into a bank account, and then the bank takes that same money and loans it out to other people. They then get a percentage of returns (interest). This is why our debt will never be paid back. Every dollar that is deposited, more dollars are basically magically created from thin air. This is the result of interest. Unless we changed our whole credit situation, the whole world will always carry this massive debt. With that being said, that may just be the best option. If you look at history over thousands of years. Every society has different exchanges of currency. From salt, to livestock, rocks, gold, silver, etc. The point is, the average for these changes historically is every 100-200 years. A good is mutually decided by the population and is agreed upon as an exchange of value. This is what defines a currency. A unit of exchange for goods and services. In our current day and age, it is typically denoted in paper money. Good old fiat currency. Cheddar, scratch, benjamins, green, bread, stacks, racks, etc. you get the point. Although the dollar, particularly the US dollar has been a global leader for quite some time, over recent years it has become pretty evident that this current financial system is on the verge of collapse. At the rate at which we are going, financial collapse is inevitable. A time that will be way worse than the 2008 subprime mortgage crisis. The worst part about it is, no one seems to know or even care. This is why our government, the federal reserve, and banks have to come to an agreement on what the next move is and very quickly. Ever hear of hyperinflation? Just google hyperinflation and tons of historic accounts with pop up of countries such as Brazil, Germany, Hungary, etc. The currencies for these countries basically become worthless in a short period of time due to irresponsible money printing. Sounds familiar right? The whole quantitative easing that the US government introduced a few years back was designed to help the country in times of a crisis. In theory it sounds like a good idea, a way to bring new money into the economy and to offer new invests and loans to people at very low interest rates. Sounds almost too good to be true. Well usually in life, things that are too good to be true, never end well. Just look around to what is happening in our everyday lives. Let's say you have been working at the same job for 10 years. Over the first couple years, you got pretty decent pay raises because you advanced up the ranks. But now as you have reached the top, you aren't receiving that significant pay raise over the first term of employment, because you have hit your max rank. The only way to advance in position is if someone leaves. That is okay though, you love your job and are promised a 3-5% raise every year moving forward. As long as the company is in the positive in. terms of revenue and you are still doing well at your day-to-day tasks, why wouldn't you get a raise. Well that is all great, but let's look at the price of goods. Gas has gone up so much over the course of a decade. Even over the past two years, gas have more than doubled. Food has also gone up substantially, what might have cost you $100 at the grocery store, now costs you $120. Don't even get me started about house prices and the cost of rent. These massive prices are not good for the economy at all. Every ten or so years, we see this happen in the housing market. The prices should always raise in real estate, but at a reasonable level. At the rate they have been going lately, no average person can afford to buy a house. You may have bought a house for $200,000 two years ago and now are sitting on a property that is literally double. Now short term, that is good for the seller. But in the long term, it doesn't help anyone at all. At the end of the day, the rate at which our inflation is impacting the purchase power, it doesn't matter really what you are being paid. For money to be successful for a long term currency, it has to be backed or pegged to a deflationary asset. Gold is a perfect example of this. While gold technically isn't deflationary, because 2% of the total gold supply is increased every year through mining, it is recognized as the OG in terms of value. For many times in history, gold along with other precious metals were used as mediums of exchange. But as societies advanced, and needs changed, so did the currency. The problem with gold or anything physical as a medium of exchange is transporting it. You walk around your city in today's world with gold bars or coins hanging out of your pockets, there is no doubt you will have all eyes on you. You shouldn't have that much anxiety when you are just trying to pay somebody or simply go to the bank. So what was the solution? In the early 1900s we came up with fiat currency (us dollar). For a very long time it was backed by gold, or known as the gold standard. It actually was great, we had debt as a nation, but it was manageable. It also kept us somewhat limited to what we could do as a nation. Which can be argued as both good and bad. But at the end of the day, times were good in terms of finances. Well unfortunately, that was all taken away in the 70s. So what happens then? What gives our currency value? Some people argue our currency is a P.E.T.R.O dollar. A fiat currency that is backed by our oil reserves and the trading of oil reserves from other countries. It also carries the theory of military protection. That majority of countries need to transact with the US dollar being the global standard. In return, a partnership (alliance) is developed. And in the event of global conflict, the United States military will be there to help your country out. Ever wonder why the US is involved in almost ever single war? That in itself is an eye opening topic that we can cover for days. We will come back to that. So essentially the only thing that gives our current US dollar, which is the global leader in currency, is it is backed by the good faith of the people. That it is recognized as a standard across the globe for a medium of exchange. Okay, cool so we all agree that one green piece of paper with some faces, numbers, and symbols is what has value. But other than that, the dollar has zero value. Literally zero intrinsic value, it isn't backed by anything. Good luck going back to the gold standard now. That would be way too hard to try to accomplish. The gold standard was great, but it also had its flaws. One being that ones reserves could be stolen easily. Also a massive black market for illegal gold had a massive value, and unless you were an expert or had the tools up front to detect fake gold, it was very easy to pull a scam on someone. So the dollar did fix the problem of carrying heavy gold bars around, but you would have the problem of having huge wads of cash stuff in wallet. So what came out and solved this problem? The issuance of debt and credit cards. A way to have your bank account balance and purchase power, without having to have the physical cash on hand. So where does this leave us? Well clearly a new asset is needed.

Introduction : This data set is a masked data set which is similar to what data analysts at Uber handle. Solving this assignment will give you an idea about how problems are systematically solved using EDA and data visualisation. Business Understanding : You may have some experience of travelling to and from the airport. Have you ever used Uber or any other cab service for this travel? Did you at any time face the problem of cancellation by the driver or non-availability of cars? Well, if these are the problems faced by customers, these very issues also impact the business of Uber. If drivers cancel the request of riders or if cars are unavailable, Uber loses out on its revenue. As an analyst, you decide to address the problem Uber is facing - driver cancellation and non-availability of cars leading to loss of potential revenue. Business Objectives : The aim of analysis is to identify the root cause of the problem (i.e. cancellation and non-availability of cars) and recommend ways to improve the situation. As a result of your analysis, you should be able to present to the client the root cause(s) and possible hypotheses of the problem(s) and recommend ways to improve them. There are six attributes associated with each request made by a customer: 1. Request id: A unique identifier of the request 2. Time of request: The date and time at which the customer made the trip request 3. Drop-off time: The drop-off date and time, in case the trip was completed 4. Pick-up point: The point from which the request was made 5. Driver id: The unique identification number of the driver 6. Status of the request: The final status of the trip, that can be either completed, cancelled by the driver or no cars available Note: For this assignment, only the trips to and from the airport are being considered. Results Expected : 1. Visually identify the most pressing problems for Uber. Hint: Create plots to visualise the frequency of requests that get cancelled or show 'no cars available'; identify the most problematic types of requests (city to airport / airport to city etc.) and the time slots (early mornings, late evenings etc.) using plots. 2. Find out the gap between supply and demand and show the same using plots. a. Find the time slots when the highest gap exists b. Find the types of requests (city-airport or airport-city) for which the gap is the most severe in the identified time slots 3. What do you think is the reason for this issue for the supply-demand gap? Write the answer in less than 100 words. You may accompany the write-up with plot(s). 4. Recommend some ways to resolve the supply-demand gap. IDE : jupyter notebook Language : Python Libraries : Numpy, Pandas, Matplotlib, Seaborn Please do explore the dataset further to your own and see what kind of other insights you can get across various other columns.

Test Assignment - Project Sports Poll Overview The "Sports Poll" app is a dead simple poll system around some sports events which can be fetched from this JSON file It allows users to vote on each event and then shows another random event to vote on. There should be one poll, that displays one (random) category at a time. E.g. load Football category with poll options to vote on from DB, and only display those at a time, next browser reload would maybe display Tennis. The polling options should be what team will win or if it will be a draw, e.g. ● Home Team win (Team A) ● Draw ● Away Team win (Team B) Delivery When you have completed the task, we’d like you to deliver the following: ● A description of what you have done and how far you got in time allotted for the work on the project. ● Which development tools you used and your general progression on the key issues, what you got stuck on, what you did or didn’t solve etc. ● A step by step instruction to how to run the project. ● Share the source code in a private code hosting on Bitbucket or Github (Bitbucket has free private repositories). ○ For Bitbucket - Share that repository giving admin permissions to bojan.zrnic@itengine.rs and GLOMOadmin and send the URL in an email to dev@glomo.se. ○ For Github - Share that repository giving admin permissions to zrnicbojan and adminglomo and send the URL in an email to dev@glomo.se. Tasks and deliverables per job position Junior Frontend Developer This exercise is expected to take 3 to 6 hours to complete. 1. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 2. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 3. It’s not allowed to use any CSS framework like Bootstrap or similar. 4. The JSON file with the events can be accessed directly from the frontend or hardcoded in the website. 5. The odds can be generated randomly. There is no need to keep track of votes across page reloads. Senior Frontend Developer This exercise is expected to take 4 to 8 hours to complete. 1. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 2. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 3. It’s not allowed to use any CSS framework like Bootstrap or similar. 4. The JSON file with the events can be accessed directly from the frontend or hardcoded in the website. 5. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 6. Keep event votes stored in a browser local storage so they can persist across page reloads. 7. Add different kind of visualisations based on event attributes (country, state, sport and so on). It is up to you to decide how to best represent the data. 8. Add a couple of automated tests. Fullstack Developer This exercise is expected to take 5 to 10 hours to complete. 1. Create a backend for Sports Poll. The backend should be created using Node.js. Whichever Node.js framework you select will not impact the way we assess your test. 2. At start, fetch the events from the JSON file and store them in a local database of your choice. 3. Create a backend API to read events. 4. Create a backend API for voting for events (home win, draw, away win). 5. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 6. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 7. 8. It’s not allowed to use any CSS framework like Bootstrap or similar. 9. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 10. Add a couple of automated tests. Senior Fullstack Developer This exercise is expected to take 7 to 15 hours to complete. 1. Create a backend for Sports Poll. The backend should be created using Node.js. Whichever Node.js framework you select will not impact the way we assess your test. 2. At start, fetch the events from the JSON file and store them in a local database of your choice. 3. Create a backend API to read events. 4. Create registration/login for the Sports Poll. It could be either with regular email address or Facebook login. 5. Create a backend API for voting for events (home win, draw, away win), keep track of the votes. Only allow logged users to vote and don’t allow more than one vote per user for each event. 6. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 7. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 8. It’s not allowed to use any CSS framework like Bootstrap or similar. 9. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 10. Add a couple of automated tests.

Key#1: Understand the regulations that pertain to your industry and your business throughout each level and function of your organization This is more difficult than it appears because Federal Regulations are simply not prescriptive and that is by design. 21CFR 820 Medical Device QSR for example, must be applicable to both manufacturers of small surgical instruments as well as manufacturers of MRI devices requiring that the regulations be sufficiently vague and flexible to pertain to each product. At the end of the day, it is the responsibility of every regulated organization to interpret those governing regulations as they pertain to the company's unique product and processes and apply those interpretations throughout the organization. In most cases, this will require the assistance of outside industry and regulatory experts to make these interpretations and the case for the direction that the company chooses to go. Certainly the most simplistic solution to achieving compliance excellence is "to do the right things right!" But what does this really mean? I have distilled the "doing the right things right" solution into 7 separate individual keys or actions that will provide a solid foundation for the establishment of any compliance program. Key#2: Define your critical processes relative to the regulatory path that has been chosen. Many organizations do not adequately define their processes After choosing a regulatory path, complete and thorough process definitions that are foundational to the business must be developed and validated with linkage to the governing regulations. These process definitions are the first rung on the ladder, the "50,000 ft. view," the genesis of the operational and regulatory paradigms that will form the structure of how the business will be run in an efficient, effective, and compliant manner. Key#3: Develop sound regulatory documentation Documentation should not simply meet a regulatory requirement but be designed to effectively direct operations, be foundational to a comprehensive worker training approach, and serve as the basis for a sound continuous improvement process. Key#4: Harmonize your processes and procedures between plants Inconsistency between operations although not necessarily a problem are cause for concern when those inconsistencies are uncovered during an inspection or investigation. Best practices should be determined for "like" operations, equipment, processes, etc. and then implemented across all facilities and locations where those "like" operations exist. Key#5: Commit to and execute comprehensive technical training. Competence is the prerequisite to competition and compliance "Read and Understand" the most basic of approaches used to transfer "knowledge and skill" in the life sciences today simply does not work. If your goal is to just meet a regulatory requirement, this is as far as you need to go - buy an LMS, build the most basic of technical documentation, assign document readings, roll the regulatory inspection dice, and you are good to go. If your goal, on the other hand, is to create an organization that meets or exceeds your regulatory responsibilities, demonstrates operational excellence, develops and deploys superior competence, and truly demonstrates the attributes of a learning organization, you must invest in training infrastructure, organizationally support training, provide training a seat at the operations and regulatory tables and include the function in the decision-making and advisory processes, and consistently execute an effective training process for both new and existing human resources. Key#6: Institute a sound and effective complaint and investigations handling process : Looking at a history of 483 observations and warning letters will tell you that CAPA deficiencies uncovered during FDA investigations consistently rank in the top three of the reasons for triggering a 483 warning letter. It is essential that CAPA systems and processes be fully integrated with corporate strategies and policies and there be a commitment up and down the organizational structure to fully execute the process. Key#7: Manage performance up and down the line to the performance structure created. If it is not managed it will not be performed Junior level managers and supervisors and the workforce in-general for that matter, must never be given cause to think that circumventing or ignoring a process or a step to a procedure is acceptable behavior even if it impacts throughput, schedules, or the "bottom-line." The risks to patient and end-user health and safety are simply too great. Regulatory compliance must be sacrosanct and an enforceable component of the performance management system. That message must be sent and received throughout the organization. The intent of this approach is to demonstrate linkage between each level beginning with the regulatory requirements themselves through regulatory documentation, through the training process, ending ultimately with the management of individual human performance.....https://www.complyarena.com/articledetails/39