Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/liaisons/ below:

Liaisons | W3C

Many organizations in addition to W3C develop standards for the Internet or the Web. In order to coordinate the development of the Web, W3C engages in liaisons with numerous organizations after careful consideration of the costs and benefits.

As defined in the W3C Process Document, the term "liaison" is used to refer to coordination of activities with a variety of organizations, through a number of mechanisms ranging from very informal to mutual membership, or even more formal agreements. Liaisons are not meant to substitute for W3C membership.

W3C is a broad community which covers standardization work in W3C Working Groups and incubation work in W3C Community Groups (CGs). Listing a formal liaison with W3C on behalf of a CG on this page is generally discouraged because CG output does not represent the consensus of the W3C Community (of course informal liaison is always encouraged). If an external group outside of W3C would like a Liaison with a CG, they must write up their rationale and be explicit that they understand that the CG work is not normative. If there is such a request, it should be sent to team-liaisons@w3.org for approval.

While this page is public, some links may be W3C member-only.

Contact W3C about a new or existing liaison.

Liaison index:            
3 • A • B • C • D • E • F • G • H • I • J • K • L  • M • N • O • P • S • T • U • V • W

European Commission            
DG CONNECT

DG DIGIT

DG Enterprise

Multistakeholder Platform

DG JRC

Margot Dor,

Xavier Piednoir,

Mike Pluke, and Mathias Schneider for M376

ICANN

(through Technical Liaison Group)

Security, Privacy, WebRTC, Web of Things.

Generic Liaisons

Misha Wolf

Michael Steidl

ISO JTC1/SC2 and its WG2

(Class C Liaison)

ISO JTC1/SC 29/WG1 (JPEG)

(Class C Liaison)

David Singer

Ms. Mayumi Koike

ISO JTC1/SC 29/WG3 (MPEG Systems)

(Class C Liaison)

Atsushi Shimono (Timed Text)
Chris Lilley (Fonts)

Kazuyuki Ashimura (Media and Entertainment)

Dr. Jean-Claude Dufourd

See the XG liaison statement

Ms. Mayumi Koike

Secretary, SC 29

Vladimir Levantovsky

ISO TC 68/ WG 4

(Class D Liaison)

ISO 20022 Registration Management Group.

(Class D Liaison)

Organization for the Advancement of Structured Information Standards (OASIS)

(W3C Member)

Kieran McAleese

Kimmo Halonen

Mobile Web Initiative: Jari Alvinen

Federated Social Web: Goix Laurent Walter

Victoria Gray.

Web3D Consortium

(W3C Member)

W3C is determined to improve W3C's liaisons with international organizations in the areas of policy and standardization and to reinforce W3C's commitment to developing one Web for all.

International Relations focuses on spreading W3C's messages and technologies beyond the Consortium's usual geographical and Web community frontiers. We pursue the vision and plan outlined in the white paper Worldwide Participation in the World Wide Web Consortium with the goal of making it easier for new stakeholders to discover and participate in W3C's work and values.

To inquire about W3C liaisons and partnerships, or to ask for review of documents in case of existing liaisons, please send email to team-liaisons@w3.org which will reach various W3C staff members active in the liaisons area and end up in the right technical staff. Please see the public International Relations page for background. We have additional specific information about participation in W3C by EU-funded projects.

For relationships between W3C and government driven organizations like ISO, ITU, EU normalization (ETSI, CEN), UN efforts like IGF/WSIS, national bodies (ANSI, AFNOR, etc.), and for Internet Governance liaison activities with other Internet organizations like IETF, ICANN, ISOC, also use team-liaisons@w3.org.

Each entry in the table above includes:

• the name of the organization, linked to its homepage. In addition, formal agreements, like MoU, should be listed here
• the W3C activities or technologies affected by the liaison
• one or several contact names within W3C
• one or several liaison contact names (preferably using an http URL, rather than a mailto)

For more information about a particular liaison, please refer to the contact page for the listed individual(s).

When an external organization wants to send an ingoing liaison statement to W3C, it should send it to team-liaisons@w3.org, CCing the W3C staff in contact indicated the table above, and assume that this statement will potentially be shared with the entire W3C membership.

When an internal W3C group (usually via its Chair) wants to send an outgoing liaison statement from W3C, it should CC it to team-liaisons@w3.org and to the W3C staff contact for the group, and assume that this statement will potentially be shared with the entire W3C membership.

W3C finds its liaisons fall into two categories:

• simple liaisons
• formal agreements for joint work, involving a Memorandum of Understanding (MoU), signed on paper and reviewed by W3C legal, and the Advisory Committee, per process requirement.

We list both types of liaisons in the table above. Per the W3C Process Document, all liaisons, of any kind, must be coordinated by the W3C Team due to requirements for public communication, IPR or confidentiality policies. Mutual membership agreements are also possible.

W3C may choose not to pursue a liaison with an organization that has selective or arbitrary membership policies that serve only to benefit pre-existing or dominant members.

In general, the goal of a simple liaison is for both parties to gain a better understanding of their respective activities and look for opportunities to work together. For example, W3C appreciates understanding how other organizations use W3C technology, whether they require extensions, the proper way to manage those extensions, how to bring extensions back into W3C, and so on. Other organizations may find a simple liaison valuable for soliciting W3C input on a web-related question.

Most often, W3C establishes simple liaisons with peer organizations, other standards bodies, or any other non-profit entity that may wish to build consensus around an emerging web technology. Simple liaisons are active as soon as both partie agree to make the information public in this page. Note that being in simple liaison with W3C on a given topic doesn't mean that W3C endorses or agrees to the other party work in any way.

In some cases, W3C is asked to establish a formal liaison that has a contractual framework, either because there are joint deliverables, or an agreed share of technical responsibilities with coordination, with considerations for confidentiality, shared press coverage, or IPR.

While W3C supports all liaisons with other groups, the organization and development of these formal liaisons requires time and resources, and the agreement of the W3C membership at large. W3C's decision to pursue a liaison with a Partner is ultimately based on the perceived costs and benefits.

For a historical record of how Formal Liaisons are created, please see the 2003 Process Document, which used to described the details (no longer the case in the current Process).

This section describes some of W3C's relationships with de jure bodies such as ISO, in addition to the direct technical activity liaisons mentioned above.

At the end of October 2010, W3C was approved as a JTC 1 Recognized PAS Submitter for an overall scope defined as "any stable core web technologies produced by W3C that are also in scope of JTC 1". The PAS process is standard transposition procedure whereby organizations accredited as valid PAS Submitters can send their specifications directly for country voting, to become ISO/IEC standards. See the W3C PAS Submission FAQ.

In January 2007, W3C became an Approved RS Originator Organization (ARO) for ISO/JTC1. This means that ISO/JTC1 standards may refer to W3C Recommendations "as-is." That process is described in the Letter Ballot on the JTC 1 Standing Document on Normative References.

The Reform of the European standardisation system by the Council of the European Union (2012) allows civil servants to use and refer to specifications from open standardization fora and consortia such as W3C, in situations involving public funds. The Multistakeholder Platform (MSP) was set up as part of the reform to advise the Commission on its ICT Standardization work program, and W3C is part of it.

For more information about W3C's ARO or PAS status, please contact  team-liaisons@w3.org.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3