DRAFT Exploration Interest Group Charter

The mission of the Exploration Interest Group is to help the W3C community exploring emerging web-related technology trends and consider how the community could collaborate to shape those trends for the benefit of web users.

Join the Exploration Interest Group.

This draft charter is available on GitHub. Feel free to raise issues.

Charter Status	See the group status page and detailed change history.
Start date	[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)
End date	[dd monthname yyyy] (Start date + 2 years)
Chairs	[chair name] (affiliation)
Team Contacts	[team contact name] (0.1 FTE)
Meeting Schedule	Teleconferences: topic-specific calls may be held or something else Face-to-face: we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.

Motivation and Background

The goal of Exploration Interest Group provides a platform to help W3C community investigating emerging technology trends, analyzing their impacts on the evolution of Web technologies, and proposing ways for W3C to collaborate shaping the trends for the benefit of the Web users. The ways include organizing Workshops, publishing Reports and creating topic oriented Task Forces etc., assisting the Web community seeking innovative responses to continually strengthen the innovation of W3C and the creativity of Web technologies.

Scope

Monitor industry and technology trends that might impact the web;
Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, Workshops, Liaison Reports), and Open Source communities on those trends. Work with W3C Team to invite W3C Liaisons to SDOs or other insightful SDOs experts, reporting back on potential areas of investigations;
Prioritize the trends and propose organizing Workshops, publishing Reports or creating topic oriented Task Forces, for further elaboration;
Propose chartering potential topics to the Strategy Funnel at the stage of incubation;
Discuss how to continue improving the exploration and investigation process, proposing improvements to the W3C members and the W3C Team.

Deliverables

Updated document status is available on the group publication status page. [or link to a page this group prefers to use]

Workshops Proposal: propose to organize discussion on relevant topics that need alignment around the next steps for W3C, e.g., "generative AI", "Digital Identity on the Web";
Reports: Create public analyses of trends that affect the Web, seeking rough consensus or presentation of competing perspectives for a report. The analyses would summarize the trending topic, outline the promise and pitfalls that are being discussed, point to relevant W3C efforts, and indicate the degree of consensus in the group on the value of the topic for the Web;
Task Forces: Creation of Task Forces as W3C sub-community with the contacts, forums, procedures, and skills needed to dig into specific topics as they come up and build consensus analyses of their implications for W3C.

Success Criteria

W3C Members and the Team finds the Workshop, Reports and the deliverable of the created Task Forces are valuable in defining, prioritizing, and organizing other W3C outcomes such as position papers and charters, etc.

Coordination

This Group is expected to coordinate with any relevant group...

W3C Groups

[other name] Working Group: [specific nature of liaison]

Note: Do not list horizontal groups here, only specific WGs relevant to your work.

Note: Do not bury normative text inside the liaison section. Instead, put it in the scope section.

External Organizations

[other name] Working Group: [specific nature of liaison]

Participation

To be successful, this Interest Group is expected to have 6 or more active participants for its duration. The Chairs are expected to contribute a quarter of a working day per week towards the Interest Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.

The group also welcomes non-Members to contribute through its public communication channels.

Participants in the group are required (by the W3C Process) to follow the W3C Code of Conduct.

Communication

Technical discussions for this Interest Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. (Does the IG plan to write EDs and WDs?) The meetings themselves are not open to public participation, however.

Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Exploration Interest Group home page.

Most Exploration Interest Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.

This group primarily conducts its technical work pick one, or both, as appropriate: on the public mailing list public-[email-list]@w3.org (archive) or on GitHub issues. The public is invited to review, discuss and contribute to this work.

The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from [pick a duration within:] one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Interest Group.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs.

This charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document requires.

Patent Disclosures

The Interest Group provides an opportunity to share perspectives on the topic addressed by this charter. W3C reminds Interest Group participants of their obligation to comply with patent disclosure obligations as set out in Section 6 of the W3C Patent Policy. While the Interest Group does not produce Recommendation-track documents, when Interest Group participants review Recommendation-track specifications from Working Groups, the patent disclosure obligations do apply. For more information about disclosure obligations for this group, please see the licensing information.

Licensing

This Interest Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 3.4 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

Note:Display this table and update it when appropriate. Requirements for charter extension history are documented in the Charter Guidebook (section 4).

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter):

Charter Period	Start Date	End Date	Changes
Initial Charter	[dd monthname yyyy]	[dd monthname yyyy]	none

Change log

Changes to this document are documented in this section.