W3C

The Web Applications Working Group has published Web Share API as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.

The Web Applications Working Group invites implementations of the following two updated Candidate Recommendation Snapshots:

• UI Events KeyboardEvent code Values defines the values for the KeyboardEvent.code attribute, which is defined as part of the UI Events Specification [UIEvents]. The code value contains information about the key event that can be used to identify the physical key being pressed by the user.
• UI Events KeyboardEvent key Values defines the key attribute values that must be used for KeyboardEvent‘s key attribute, which is defined as part of the UI Events Specification [UIEvents].

The Verifiable Credentials Working Group has published a First Public Working Draft of Verifiable Credentials JSON Schema Specification 2023. Among other things, the [VC-DATA-MODEL-2] specifies the models used for Verifiable Credentials, Verifiable Presentations, and explains the relationships between three parties: issuers, holders, and verifiers. Critical pieces of functionality referenced throughout the [VC-DATA-MODEL-2] are the that of verifiability, extensibility, and semantic interoperability. This specification provides a mechanism to make use of a Credential Schema in Verifiable Credential, leveraging the existing Data Schemas concept.

The Verifiable Credentials Working Group has published a First Public Working Draft of BBS Cryptosuite v2023. This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures.

The RDF-star Working Group has published the following 16 First Public Working Drafts, which represent the first milestone in the update of the RDF and SPARQL families of specification towards version 1.2:

1. RDF 1.2 Concepts and Abstract Syntax defines an abstract syntax (a data model) for the Resource Description Framework (RDF), which serves to link all RDF-based languages and specifications.
2. RDF 1.2 XML Syntax defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base.
3. RDF 1.2 Turtle defines a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes.
4. RDF 1.2 N-Triples defines a line-based, plain text format for encoding an RDF graph.
5. RDF 1.2 N-Quads defines is a line-based, plain text format for encoding an RDF dataset.
6. RDF 1.2 TriG defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle format.
7. RDF 1.2 Schema defines a data-modelling vocabulary for RDF data. RDF Schema is an extension of the basic RDF vocabulary.
8. SPARQL 1.2 Query Language defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware.
9. SPARQL 1.2 Update describes SPARQL 1.2 Update, an update language for RDF graphs. It uses a syntax derived from the SPARQL Query Language for RDF.
10. SPARQL 1.2 Protocol specifies the SPARQL Protocol; it describes a means for conveying SPARQL queries and updates to a SPARQL processing service and returning the results via HTTP to the entity that requested them.
11. SPARQL 1.2 Query Results XML Format describes an XML format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.
12. SPARQL 1.2 Query Results JSON Format describes the representation of SELECT and ASK query results using JSON.
13. SPARQL 1.2 Query Results CSV and TSV Formats describes the use of the formats CSV [RFC4180] (comma separated values) and TSV [IANA-TSV] (tab separated values) for expressing SPARQL query results from SELECT queries.
14. SPARQL 1.2 Service Description describes SPARQL service description, a method for discovering, and vocabulary for describing SPARQL services made available via the SPARQL 1.2 Protocol.
15. SPARQL 1.2 Federated Query defines the syntax and semantics of SPARQL 1.1 Federated Query extension for executing queries distributed over different SPARQL endpoints.
16. SPARQL 1.2 Graph Store Protocol describes the use of HTTP operations for the purpose of managing a collection of RDF graphs. This interface is an alternative to SPARQL 1.2 Protocol.

The W3C Advisory Committee has nominated nine individuals, and is invited today to vote until 1 June 2023 for six seats in the W3C Advisory Board (AB) election. Please, read the statements of the nominees.

Created in March 1998, the Advisory Board provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution. The Advisory Board also serves the W3C Members by tracking issues raised between Advisory Committee meetings, soliciting Member comments on such issues, and proposing actions to resolve these issues. The Advisory Board manages the evolution of the Process Document. The Advisory Board hears appeals of Member Submission requests that are rejected for reasons unrelated to Web architecture. For several years, the AB has conducted its work in a public wiki.

The elected Members of the Advisory Board participate as individual contributors and not representatives of their organizations. Advisory Board participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user.

The World Wide Web Consortium (W3C) is working with leading international executive search firm Perrett Laver to find qualified candidates from around the world to be our CEO.

W3C began 2023 by forming a new public-interest incorporated not-for-profit organization. We are now seeking our next leader at this exciting time in our evolution.

The new organization preserves the core process and mission of the Web Consortium to shepherd the Web, by developing open web standards as a single global organization with contributions from W3C Members, staff, and the international community. The new W3C entity preserves our member-driven approach and existing worldwide outreach and cooperation.

W3C is a unique organization at a crucial transition point in its existence. Reporting to the newly formed Board of Directors, the CEO will be responsible for the success of W3C in line with our mission. The CEO must be an experienced and collaborative leader who appreciates the strong assets of W3C —its expert staff, engaged members, committed Board and fantastic reputation— and has the capacity to effectively leverage these to transform the organization and ensure a bright future and further impact.

The next CEO of W3C will be a strategic, collaborative, and motivating leader. They will have a global mindset and the ability to effectively engage with a diverse range of stakeholders. They will be a person of integrity who is forward thinking and supportive of staff. Most importantly, they will have an affinity for, and understanding of, the work, mission, and values of W3C.

W3C invites applications from qualified CEO candidates from across several continents. Please refer to the Perrett Laver site. You may read more in our Press Release. The deadline for applications is Friday, May 12th, 2023.

W3C invites public feedback on a beta release of the W3C website redesign. The new site features a cleaner and more modern look, a simplified information architecture, improved accessibility, and more integration throughout the site. Once the beta of the English site has concluded, we will offer sites in Japanese and Chinese.

The scope of the redesign is limited to most of our public pages, but we will gradually work to include the rest of the site.

You can read a bit more on the beta and its context in the W3C blog post, and about the redesign work and process in Studio 24’s blog post. We look forward to your feedback.