Skip to toolbar

Community & Business Groups

  • Algorithmic Modelling Community Group

    The mission of this group is to propose foundational specifications relating to "algorithmic modelling": a "model", in this context, being a description of the composition and relative dynamic behaviour of the sub-parts of a system, as exemplified by the Object Management Group's Model Driven Architecture. The output of this group may then act as a reference point for groups requiring the use of specific types of models, conceptual and computational being two such.

    Final reports / licensing info

    date name commitments
    Algorithmic Modelling Reference Model Licensing commitments
    Read more
  • Automotive and Web Platform Business Group

    The mission of the Automotive and Web Platform Business Group is to act as an incubator of ideas for standardization for connected vehicles. It had produced some early draft specifications for making vehicle signals available in a browser runtime as a first class object. Those specifications were the basis for launching the W3C Automotive Working Group in order to bring them through the W3C Recommendation Process. The Auto Working Group has since changed to service specifications to expose signals in a broader range of environments, HTML5, Qt and headless applications in any programming language running on vehicle head units.

    Currently we have task forces on:

    • Privacy and Security
    • Media tuning
    • Location Based Services
    • Web Payments
    • Merging VW submission with Auto WG spec (RSI)

    Final reports / licensing info

    date name commitments
    Vehicle Information API Licensing commitments
    Vehicle Data Interfaces Licensing commitments
    Read more
  • Best Practices for Multilingual Linked Open Data Community Group

    The target for this group is to crowd-source ideas from the community regarding best practises for producing multilingual linked open data. The topics for discussion are mainly focused on naming, labelling, interlinking, and quality of multilingual linked data, among others. Use cases will be identified to motivate discussions. Participation both from academia and industry is expected. The main outcome of the group will be the documentation of patterns and best practices for the creation, linking, and use of multilingual linked data. This group will not create specifications.

    Final reports / licensing info

    date name commitments
    Guidelines for Linguistic Linked Data Generation: Multilingual Dictionaries (BabelNet) Licensing commitments
    Guidelines for Linguistic Linked Data Generation: Bilingual Dictionaries Licensing commitments
    Guidelines for Linguistic Linked Data Generation: Multilingual Terminologies (TBX) Licensing commitments
    Guidelines for developing NIF-based NLP Web Services Licensing commitments
    Guidelines for LLD Exploitation Licensing commitments

    Drafts / licensing info

    name
    Guidelines for Linguistic Linked Data Generation: WordNets
    Guidelines for Linked Data corpus creation using NIF
    Guidelines for LLOD aware services
    Read more
  • Cloud Computing Community Group

    The group will examine and create specifications related to distributed computation and storage, with an XML network transport layer and possible mapping to RDF.

    Final reports / licensing info

    date name commitments
    Use Cases and Requirements Licensing commitments
    Cloud Provider Service Engagement Licensing commitments
    Cloud Processing Model Licensing commitments
    Storage Mapping Licensing commitments
    Cloud API Licensing commitments
    Cloud Processing in RDF Licensing commitments
    Cloud Visualisation Licensing commitments
    Read more
  • Credentials Community Group

    The mission of the W3C Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.

    Final reports / licensing info

    date name commitments
    Verifiable Claims Use Cases 1.0 Licensing commitments
    Verifiable Claims Data Model and Representations 1.0 Licensing commitments
    Read more
  • Customer Experience Digital Data Community Group

    The Customer Experience Digital Data Community Group will work on reviewing and upgrading the W3C Member Submission in Customer Experience Digital Data, starting with the Customer Experience Digital Data Acquisition submission linked here (http://www.w3.org/Submission/2012/04/). The group will also focus on developing connectivity between the specification and the Data Privacy efforts in the industry, including the W3C Tracking Protection workgroup. The goal is to upgrade the Member Submission specification via this Community Group and issue a Community Group Final Specification.

    Final reports / licensing info

    date name commitments
    Customer Experience Digital Data Layer Licensing commitments

    Drafts / licensing info

    name
    Customer Experience Digital Data Acquisition
    Read more
  • Distributed Trace Context Community Group

    The mission of this group is to define the standard for distributed trace context propagation. Distributed trace context is used to enable monitoring and diagnostics scenarios in micro-services environment. It consists of request identifiers and key properties that needs to be propagated from one micro-service to another. These identifiers and properties are used to analyze an end-to-end distributed traces.

    The group primary objective is to publish a specification for the protocols to use for distributed trace context propagation. Protocol includes wire format and recommended scenarios to use these protocols in applications, web servers, libraries, and platforms. The group also targets to produce reference implementation for some languages.

    Standardized and universally used trace context propagation protocols enable monitoring and diagnostics scenarios that are hard to achieve otherwise. Authors of libraries, web servers, and application performance management (APM) vendors who are interested to improve micro-services monitoring and diagnostics story are encouraged to participate in this group.

    Drafts / licensing info

    name
    trace context
    Read more
  • HTML Editing APIs Community Group

    A group to work on APIs and other functionality related to rich-text HTML editing, such as (1) the contenteditable and designMode attributes (2)The execCommand(), queryCommandEnabled(), queryCommandIndeterm(), queryCommandState(), queryCommandSupported(), and queryCommandValue() methods on the Document interface (3) what exact effect user actions (such as typing text or hitting Enter) should have on rich-text editable regions (4) the Selection interface (5) spellcheck for rich-text editable regions, and (6) other functionality related to the foregoing. The group is expected to work on writing high-quality, detailed technical specifications suited for implementation by major browsers. It will start work with the preliminary specification hosted at http://aryeh.name/spec/editing/editing.html, and later add the Selection part of http://html5.org/specs/dom-range.html, both of which are currently developed entirely outside the W3C and are not close to interoperable implementation. The group's deliverables are expected to be submitted to the Recommendation track in the WebApps WG after they mature sufficiently.

    Drafts / licensing info

    name
    HTML Editing APIs
    Read more
  • Hydra Community Group

    Building Web APIs seems still more an art than a science. How can we build APIs such that generic clients can easily use them? And how do we build those clients? Current APIs heavily rely on out-of-band information such as human-readable documentation and API-specific SDKs. However, this only allows for very simple and brittle clients that are hardcoded against specific APIs. Hydra, in contrast, is a set of technologies that allow to design APIs in a different manner, in a way that enables smarter clients. The foundation is laid by the Hydra Core Vocabulary. It defines a number of fundamental concepts, such as hypermedia controls and collections, which allow machines to understand how to interact with an API. Since all information about the API is available in a machine-readable form, completely generic clients become possible. The Core Vocabulary is complemented by Linked Data Fragments, a set of specifications that enable advanced yet efficient client-side querying of Web APIs. More information about these technologies can be found on our homepage: http://www.hydra-cg.com/

    Drafts / licensing info

    name
    Hydra Core Vocabulary
    Read more
  • JSON for Linking Data Community Group

    JSON-LD (JavaScript Object Notation for Linking Data) is a lightweight Linked Data format that gives your data context. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. If you are already familiar with JSON, writing JSON-LD is very easy. These properties make JSON-LD an ideal Linked Data interchange language for JavaScript environments, Web service, and unstructured databases such as CouchDB and MongoDB.

    Final reports / licensing info

    date name commitments
    JSON-LD Syntax 1.0 Licensing commitments
    JSON-LD API 1.0 Licensing commitments
    JSON-LD 1.0 Licensing commitments
    JSON-LD 1.0 Licensing commitments
    JSON-LD 1.0 Processing Algorithms and API Licensing commitments

    Drafts / licensing info

    name
    JSON-LD Framing API 1.0
    RDF Universal Graph Normalization 2011
    Read more
  • Machine Learning Schema Community Group

    This group represents a collaborative, community effort with a mission to develop, maintain, and promote standard schemas for data mining and machine learning algorithms, datasets, and experiments. Our target is a community agreed schema as a basis for ontology development projects, markup languages and data exchange standards; and an extension model for the schema in the area of data mining and machine learning. The goals of this group are: To define a simple shared schema of data mining/ machine learning (DM/ML) algorithms, datasets, and experiments that may be used in many different formats: XML, RDF, OWL, spreadsheet tables. Collect use cases from the academic community and industry Use this schema as a basis to align existing DM/ML ontologies and develop more specific ontologies with specific purposes/applications Prevent a proliferation of incompatible DM/ML ontologies Turn machine learning algorithms and results into linked open data Promote the use of this schema, including involving stakeholders like ML tool developers Apply for funding (e.g. EU COST, UK Research Councils, Horizon2020 Coordination and Support Actions) to organize workshops, and for dissemination

    Drafts / licensing info

    name
    ML Schema Core Specification
    Read more
  • MicroXML Community Group

    MicroXML is a subset of XML intended for use in contexts where full XML is, or is perceived to be, too large and complex. MicroXML provides a set of rules for defining markup languages intended for use in encoding data objects, and specifies behavior for certain software modules that access them.

    Drafts / licensing info

    name
    MicroXML
    Read more
  • Multi-device Timing Community Group

    Timing mechanisms allow operations to be executed at the correct time. The Web already has several mechanisms supporting timed operations, including setTimeout and setInterval, as well as controllers for media frameworks and animations. However, the Web lacks support for multi-device timing. A multi-device timing mechanism would allow timed operations across Web pages hosted by different devices. Multi-device timing is particularly important for the broadcasting industry, as it is the key enabler for web-based secondary device offerings. More generally, multi-device timing has wide utility in communication, collaboration and multi-screen presentation. This Community Group aims to define a common, multi-device, timing mechanism and a practical programming model. This will improve the Web as a platform for time-sensitive, multi-device Web applications. Charter : http://webtiming.github.io

    Drafts / licensing info

    name
    Timing Object Draft Specification
    Read more
  • Music Notation 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.

    Final reports / licensing info

    date name commitments
    MusicXML Version 3.1 Licensing commitments
    Read more
  • ODRL Community Group

    The ODRL Community Group supports the promotion and future development of the W3C ODRL recommendations:

    Specifically, the ODRL CG will:

    • Promote ODRL V2.2 to existing and new sectors/industries
    • Nurture an ODRL implementors community
    • Publish reports related to ODRL usage
    • Support development of ODRL Profiles (and host for smaller communities)
    • Register ODRL Profiles
    • Collaborate with W3C on ODRL errata maintenance
    • Plan for future major enhancements to ODRL (V3.0)

    Final reports / licensing info

    date name commitments
    ODRL Version 2.0 Core Model Licensing commitments
    ODRL Version 2.0 Common Vocabulary Licensing commitments
    ODRL Version 2.0 XML Encoding Licensing commitments
    ODRL Version 2.1 Core Model Licensing commitments
    ODRL Version 2.1 XML Encoding Licensing commitments
    ODRL Version 2.1 Common Vocabulary Licensing commitments
    ODRL Version 2.1 JSON Encoding Licensing commitments
    ODRL Version 2.1 Ontology Licensing commitments
    W3C ODRL Information Model Version 2.2 Licensing commitments
    W3C ODRL Vocabulary & Expression Version 2.2 Licensing commitments

    Drafts / licensing info

    name
    ODRL 2.1 / Creative Commons Profile
    ODRL Best Practices
    Read more
  • Ontology-Lexica Community Group

    The mission of the Ontology-Lexicon community group is to: (1) Develop models for the representation of lexica (and machine readable dictionaries) relative to ontologies. These lexicon models are intended to represent lexical entries containing information about how ontology elements (classes, properties, individuals etc.) are realized in multiple languages. In addition, the lexical entries contain appropriate linguistic (syntactic, morphological, semantic and pragmatic) information that constrains the usage of the entry. (2) Demonstrate the added value of representing lexica on the Semantic Web, in particularly focusing on how the use of linked data principles can allow for the re-use of existing linguistic information from resource such as WordNet. (3) Provide best practices for the use of linguistic data categories in combination with lexica. (4) Demonstrate that the creation of such lexica in combination with the semantics contained in ontologies can improve the performance of NLP tools. (5) Bring together people working on standards for representing linguistic information (syntactic, morphological, semantic and pragmatic) building on existing initiatives, and identifying collaboration tracks for the future. (6) Cater for interoperability among existing models to represent and structure linguistic information. (7) Demonstrate the added value of applications relying on the use of the combination of lexica and ontologies.

    Final reports / licensing info

    date name commitments
    Lexicon Model for Ontologies Licensing commitments
    Read more
  • Open Annotation Community Group

    The purpose of the Open Annotation Community Group is to work towards a common, RDF-based, specification for annotating digital resources. The effort will start by working towards a reconciliation of two proposals that have emerged over the past two years: the Annotation Ontology [1] and the Open Annotation Model [2]. Initially, editors of these proposals will closely collaborate to devise a common draft specification that addresses requirements and use cases that were identified in the course of their respective efforts. The goal is to make this draft available for public feedback and experimentation in the second quarter of 2012. The final deliverable of the Open Annotation Community Group will be a specification, published under an appropriate open license, that is informed by the existing proposals, the common draft specification, and the community feedback. [1] http://code.google.com/p/annotation-ontology/ [2] http://www.openannotation.org/spec/beta/

    Drafts / licensing info

    name
    Core Open Annotation Specification (Community Draft 1)
    Open Annotation Extension Specification (Community Draft 1)
    Open Annotation Specification (Community Draft 2)
    Read more
  • Open Data Nepal Community Group

    A forum for the open network of open data enthusiasts, government officers, students, researchers, and a non-profit leader who are working to improve the condition of open data in Nepal. This space will help individual volunteers, groups, students to collaborate and discuss how one can help to boost the open data momentum in Nepal. This group will not have any criteria and specification, anyone can join and may reuse the group works. This group will not publish Specifications.

    Drafts / licensing info

    name
    Beta Version of Open Data Nepal – A Portal to Make Nepal’s Data Accessible Online
    Read more
  • Open knowledge-driven service-oriented system architectures and APIs (KiSS) Community Group

    W3C provide a great variety of standards that can be used to build applications that use the Internet as a platform for communication and integration. The open Knowledge-driven Service-oriented System architectures and APIs (KiSS) community group is created for sharing, elaborating and evolving knowledge-driven approaches for system integration. The KiSS community group takes service-oriented architecture as a main paradigm for application creation. However, it is not enough to say that there is a set of some services that can be integrated according to the application needs. The integration is facilitated with semantic descriptions of the services. Furthermore, the special support components are required at system run time in order to allow dynamic composition of the services accordingly semantic representation of adjusted or new system goals. Thus, the community aims to categorise different possible architectures to allow knowledge-driven approach for system integration; it provides reference architectures that also point out possible technologies for the solution implementation. The community targets different application domains and industries in order to benefit from cross-domain vision on development of knowledge-driven systems. The abbreviation of the community group highlights the integrative nature of the group (small i among K (knowledge), S (service) and S (system)). The group is managed by 6 re-electable chairs. The roles and responsibilities of the chairs go as follows:

    • General chair: Ideologist. Overall synchronization between different pillars of the KiSS. PR with other groups and external stakeholders. Member attraction, community group development.
    • Chair for integration: Integration technologies, web service composition.
    • Chair for knowledge: Knowledge representation and reasoning standards and methodologies.
    • Chair for devices: Embedded devices, their adoption for KiSS.
    • Chair for services: Web services, standards, methodologies for service definition.
    • Chair for application domains: KiSS in different application domains. Cross-domain learning and development. Benchmarking.

    Drafts / licensing info

    name
    Recipes for building service-oriented knowledge-driven systems
    Read more
  • OpenActive Community Group

    This community group is part of the OpenActive initiative. Our goal is to develop technical specifications and best practices that will support the use of open and shared data relating to sports and physical activities.

    Our primary focus is on standardising how to publish data about opportunities to be physically activity, defining best practices and APIs to enable booking of events and facilities, and improving interoperability of data across the sector.

    To ensure that our specifications will support a variety of use cases, we welcome contributions from a range of organisations, including existing platforms and new startups.

    While our work is technical, you don’t have to be a developer to contribute to our standards group. We are looking for input from product and service managers whose domain knowledge can help us to create better outputs.

    Final reports / licensing info

    date name commitments
    Modelling Opportunity Data Licensing commitments
    Realtime Paged Data Exchange Licensing commitments

    Drafts / licensing info

    name
    OpenActive Vocabulary
    Publishing opportunity data: a primer
    OpenActive Activity List
    Read more
  • Quick-fix support for XML Community Group

    Sometimes an error reported against an XML document can be fixed automatically, for example if the error refers to an unexpected attribute then an automatic fix will be to delete that unexpected attribute. We want to explore the issues related to applying quick fixes (like preserving DOCTYPE declarations, entities, etc.) and determine what actions will be needed be able to apply quick fixes on a document as well as a representation language to describe these actions. Quick fixes are especially interesting when we use Schematron for XML validation, as in this case the quick-fix should be specified by the schema author, so we have user-defined quick fixes. Imagine for example a business rule implemented in Schematron that says that a list should contain between 4 and 8 items. If we determine that there are two items then a quick fix will propose to add automatically two more items to the list or if the list has 10 items then a quick fix may propose to delete two items or to split the list in two lists, etc.

    Drafts / licensing info

    name
    Schematron Quick Fixes Specification
    Read more
  • RDF Stream Processing Community Group

    The mission of the RDF Stream Processing Community Group (RSP) is to define a common model for producing, transmitting and continuously querying RDF Streams. This includes extensions to both RDF and SPARQL for representing streaming data, as well as their semantics. Moreover this work envisions an ecosystem of streaming and static RDF data sources whose data can be combined through standard models, languages and protocols. Complementary to related work in the area of databases, this Community Group looks at the dynamic properties of graph-based data, i.e., graphs that are produced over time and which may change their shape and data over time.

    Drafts / licensing info

    name
    RDF Stream Processing: Requirements and Design Principles
    Read more
  • SVG Streaming Community Group

    This group will work on developing guidelines and possible extensions to the SVG language enabling the authoring of streamable SVG content, in particular for the creation of streamable cartoon animations, synchronized graphically-rich karaoke, or synchronized graphical overlays on top of video streams.

    Drafts / licensing info

    name
    SVG Streaming
    Read more
  • Second Screen Community Group

    The Second Screen Community Group (CG) explores the use of secondary screens from Web pages. This Community Group incubates and develops specifications of network protocols that implement the Presentation API and the Remote Playback API.

    This work has three primary purposes:

    • Enable interoperability among implementations of the Presentation API.
    • Encourage implementation of the Presentation API by browser vendors.
    • Establish complementary specifications for the Presentation API.

    The scope of work proposed here goes beyond the current scope of the Second Screen Working Group (WG). Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate standards track, for example the IETF Standards Track or a W3C Working Group, for further contributions and formal standardization.

    See the CG charter for more information.

    Final reports / licensing info

    date name commitments
    Presentation API Licensing commitments
    Presentation API Licensing commitments

    Drafts / licensing info

    name
    Presentation API
    Read more
  • Semantic Statistics Community Group

    This community group aims to be a forum for the statistics community and the Linked Data community to examine issues arising from applying semantic technologies in the statistical production process and to report on best practises in the use of statistics on the Web of data. In particular the group will discuss use cases of the application of the Data Cube vocabulary in the production of official statistics and establish if there is a need for more standardisation of vocabularies to ensure comparability of statistics data on the Web of Data. Potential participants in this group are members of official statistics agencies and other government bodies that produce data (e.g. administrative, geospatial, government funded research results), statisticians, researchers and anyone in the Web of Data community who is interested in the publication of statistical data that can lead to statistical analysis of the maximum rigour. The group will coordinate as appropriate with the Government Linked Data WG and other relevant groups within the W3C Data Activity Coordination Group. This group will not publish specifications.

    Drafts / licensing info

    name
    SDMX Metadata
    Read more
  • Shape Expressions Community Group

    This group serves to promote and expand ShEx – Shape Expressions. ShEx is an alternative to SHACL which uses a syntactic representation to describe the shape of an RDF graph. The Shape Expressions (ShEx) language describes RDF nodes and graph structures. A node constraint describes an RDF node (IRI, blank node or literal) and a shape describes the triples touching nodes in RDF graphs. These descriptions identify predicates and their associated cardinalities and datatypes. ShEx shapes can be used to communicate data structures associated with some process or interface, generate or validate data, or drive user interfaces. Spec at https://shexspec.github.io/spec/

    Drafts / licensing info

    name
    Shape Expressions (ShEx) Primer
    Shape Expressions Language 2.0
    ShapeMap Structure and Language
    Read more
  • Speech API Community Group

    The goal and scope of this Community Group is to produce a JavaScript Speech API that supports the majority of use-cases in the the Speech Incubator Group's Final Report [1], but is a simplified subset API, such as this proposal [2]. For this initial specification, we believe that a simplified subset API will accelerate implementation, interoperability testing, standardization and ultimately developer adoption. This JavaScript Speech API will enable web developers to incorporate scripts into their web pages that can generate text-to-speech output and can use speech recognition as an input for forms, continuous dictation and control. Specification of HTML markup and a network speech protocol are out-of-scope of this Community Group. [1] http://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech/ [2] http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/att-1696/speechapi.html

    Final reports / licensing info

    date name commitments
    Web Speech API Licensing commitments
    Read more
  • TV Control API Community Group

    The convergence of Internet-based IPTV, Video-on-Demand (VoD), Personal Video, IP multicasting video, cellular multicasting video etc. with traditional broadcasting video, satellite video and cable video is emerging on market. The technology gap between web apps and native apps is rapidly narrowing. Thus a web-based application controlling various TV channels with detailed information regarding TV programs is becoming a more and more main stream TV control application for the integrated video service. Furthermore, in many regions TV broadcasters are developing web applications that can overlay their channel in a hybrid broadcast/broadband environment. Scope of Work The W3C TV Control API Community Group is to define an API layer that is agnostic of any underlying video sourcing technologies to enable a web-based application to: - provide EPG information, including the list of TV programs and related information such as channel number, producers, directors, actors, synopsis, rating etc., - control and switch the TV sourcing based on channel identifier from EPG data - interact with TV platform for presenting the TV program appropriately - interact with TV platform for presenting other supplemental content appropriately The underlying video sourcing method and technologies, the presentation technology and/or presentation application of TV program and supplemental content are all out of scope. Operating Guidelines This group operates under the rules of the Community and Business Group Process. All matters relating to intellectual property are governed by the Community Contributor License Agreement (CLA). All participants within this group agree that their discussions will follow the General Communications Policies.

    Final reports / licensing info

    date name commitments
    TV Control API Specification v1.0 Licensing commitments

    Drafts / licensing info

    name
    TV Control API Specification (Draft Candidate)
    Read more
  • Universal Images Community Group

    Our goal is to provide tools and specifications for creatives and agencies to create and distribute multi-format images. These are images which contain metadata that lets them adjust to different sizes, depending of the format of the output device or the layout of the website it is used in. These images can be used to have a web-server automatically create the alternative versions needed for a responsive website.

    Drafts / licensing info

    name
    Responsive Metadata XMP Standard
    Read more
  • Web Media API Community Group

    Media web application developers want to deploy their content on a wide and heterogeneous range of devices and platforms, e.g. televisions, set-top boxes, and mobile devices. To ensure a smooth user experience across devices, these user agents need to support a minimum set of Web technologies that developers can rely on being supported. This Community Group plans to specify such a set of Web technologies and additionally plans to provide guidance for developers and implementers e.g. on performance constraints and portability issues.

    See the CG charter for more information.

    Final reports / licensing info

    date name commitments
    Web Media API Snapshot 2017 Licensing commitments
    Read more
  • Web Media Text Tracks Community Group

    This group will work on text tracks for video on the Web, applied to captioning, subtitling and other purposes. This group plans to work initially on: 1) Documenting a semantic model underlying the caption formats in use, notably TTML, CEA 608/708, EBU STL, and WebVTT. 2) Creating a community specification for WebVTT. 3) Defining the mappings between WebVTT and some selected formats, including at least TTML (W3C/SMPTE), and CEA 608/708. 4) Creating web developer reference and tutorial material, including worked examples. 5) Creating a test suite and/or tools. A possible transition to REC-track for some of these document(s) is envisaged and that possibility will be used to guide the work and procedures. The group may produce recommendations for work in other groups, such as CSS, HTML5, and TTWG.

    Final reports / licensing info

    date name commitments
    WebVTT Licensing commitments

    Drafts / licensing info

    name
    WebVTT
    Conversion of 608/708 captions to WebVTT
    Read more
  • Web NFC Community Group

    The Web NFC Community Group will create a Near Field Communication API that is browser-friendly and adheres to the Web's security model. We believe that means the API will not expose full, low level NFC functionality, but rather a higher level subset that is safe for Web pages, protects user privacy, and does not annoy users with unnecessary or complex permission requests. See the Web NFC Community Group Charter and the Web NFC specification for more information.

    Drafts / licensing info

    name
    Web NFC API
    Read more
  • Web Payments Community Group

    The purpose of the Web Payments Community Group is to discuss, research, prototype, and create working systems that enable Universal Payment for the Web. The goal is to create a safe, decentralized system and a set of open, patent and royalty-free specifications that allow people on the Web to send each other money as easily as they exchange instant messages and e-mail today. The group will focus on transforming the way we reward each other on the Web as well as how we organize financial resources to enhance our personal lives and pursue endeavors that improve upon the human condition.

    Final reports / licensing info

    date name commitments
    Web Payments CG Use Cases 1.0 Licensing commitments

    Drafts / licensing info

    name
    Web Payments Design Principles 1.0
    Web Payments CG Roadmap 1.0
    Web Payments CG Commerce 1.0
    Web Payments CG Web Commerce API 1.0
    Web Payments CG Commerce Vocabulary 1.0
    Web Payments CG Web Payments Vocabulary 1.0
    Web Payments CG HTTP Signatures 1.0
    Web Payments CG Secure Messaging 1.0
    Web Payments CG Security Vocabulary 1.0
    Read more
  • Web and Broadcasting Business Group

    The aim of the Web and Broadcasting Business Group is to study and clarify the influence of Open Web Platform on the professional world of broadcasting, and to help stakeholders within the broadcasting industry to build good and practical understanding on the standardization processes in W3C with the chair-to-chair communication mechanism built into business groups. The business group will create monthly or bi-monthly report to summarize their study on the influence and share the reports internally. Detailed discussion and analysis on the use cases in this area should be done in the Web and TV Interest Group, so the business group will not deal with those items to avoid scope overlap. However, fruitful collaborative works may happen as a result of the chair-to-chair communication between these two groups.

    Drafts / licensing info

    name
    Towards a Smarter Combination of Broadcasting and the Web
    Identity Technologies on the Web: A Primer
    Repository of Existing Business-Level Use Cases for TVs In Tandem With Other Screens that Enrich Programs and Commercials via the Web
    Read more
  • Web-based Signage Business Group

    The Web-based Signage Business Group is aimed at companies and organizations interested in the standardization of Web based digital signage. The goal of the group is to identify use cases and system image/model for expansion of web browser based digital signage and smarter integration of existing Web standards.

    Drafts / licensing info

    name
    Web-based Signage Use cases and Requirements
    Architecture and Requirements for Web-based Signage Player - Core Profile
    Architecture and Requirements for Web-based Signage Player - Basic Media Profile
    Architecture and Requirements for Web-based Signage Player - Storage Profile
    Read more
  • WebAPI Discovery Community Group

    A group to develop a mechanism for the automatic discovery of WebAPIs, by extending the schema.org vocabulary. Increasingly, large online platforms and services provide one or more Web APIs for third-party developers. Moreover, many companies build WebAPIs as their primary product (Email API, SMS API, etc.). This has resulted in an explosion of the number of WebAPIs in recent years. Developers spend a significant amount of time searching for suitable WebAPIs to meet their needs. Our intention is to work closely with Schema.org to define a WebAPI-specific extension and promote usage of this extension among API owners. In the long run, our aim is to contribute this extension into the core Schema.org vocabulary. To achieve these goals we are seeking feedback and collaboration from API owners, DX specialists, API description language experts and maintainers of various API catalogs.

    Drafts / licensing info

    name
    WADG0001 WebAPI type extension
    Read more