charter.md

charter.md

• W3C Social Web Working Group Charter Brainstorming

Welcome to the brainstorming page for collecting thoughts, methodologies, and opinions for chartering a new W3C Social Web Working Group.

Please adhere to the W3C code of conduct when making contributions and edits.

• Purpose

  This page is not a formal charter, either for a Community Group (CG) or Working Group (WG). Instead, it's a space for collecting diverse and broad input to consider for the creation of a working group charter.

• About Working Groups

  W3C typically forms working groups to facilitate collaboration among implementers in updating and creating specifications for greater interoperability. Chairs and spec editors, while often not implementers themselves, play a crucial role in moving specifications forward.

  In recent years, W3C working groups have coordinated with community groups to incubate new ideas. Once proof of concept and multi-implementer interest is established, these proposals are considered for standardization.

• Brainstorming Sections

  The brainstorming sections align with key areas in a formal charter:

• Scope: Provide general statements about scope, methodology, and reasoning.

• Deliverables: Describe tasks that a WG would complete.

• Liaisons: Document relationships with other groups.

• Scope

  In this section, provide high-level statements about the scope without referencing specific specifications. The "Deliverables" section is where specific specs are discussed.

• Deliverables

  This section outlines what tasks a working group would complete. Here is a simplified table format:

  Spec Name	Active Editor(s)	Editor(s) Interested in WG Participation?	W3C Status	Active Test Suite	Implementation Report	# of Implementations in Report	Estimated # Implementations in Wild	Scope Description
  ActivityPub	Evan Prodromou	y/n	Recommendation	n	Report	13	-	Errata modifications, clarify ambiguities in the spec
  rel=me	Tantek Çelik	-	External spec maintained by microformats	n	n/a	n/a	n/a	Codify rel=me into a full specification
  IndieAuth Ticket Auth	James willing to help, no official appointed editor	-	External draft spec maintained by the IndieWeb community	n	n/a	n/a	n/a	Work toward achieving multiple interoperable implementations of Ticket Auth, refine spec
  HTTP Message Signatures Profile for ActivityPub	-	-	No existing spec, existing implementations in AP S2S	n	-	-	-	Document a profile of HTTP Signatures for use in ActivityPub server-to-server
  OAuth Profile for ActivityPub clients	Evan Prodromou	-	Initial draft as FEP-d8c2	n	-	-	-	Document a profile of OAuth for use by ActivityPub clients

• Previous Social Web WG Specs and Notes

  Here are the specifications and notes published by the previous Social WG:

• Specs

• ActivityPub

• WebSub

• Activity Streams 2.0

• Activity Vocabulary

• Micropub

• Linked Data Notifications

• Webmention

• ... etc.

• Notes

• IndieAuth

• Post Type Discovery

• JF2

• Social Web Protocols

• Specs New to a WG

  List your ideas for new specifications below:

• rel=me

• ...

• Incubations for Consideration

  Incubations are early-stage ideas that may not be ready for drafting into a specification. These ideas will be discussed in the Community Group (CG). With sufficient interest and support, they may progress further.

  List ideas for incubations below:

• ...

• Liaisons

• Social Web Incubator Community Group: For incubating proposals for consideration for standardization. Guidelines for transitioning CG proposals into a WG are forthcoming.

• IETF groups

  • oauth: OAuth is used by many ActivityPub implementations.
  • httpbis: HTTP Signatures are used by most/all ActivityPub implementations.
  • ...

• Other W3C groups

  • ...

• Other communities

  • ActivityPub forums
  • Data Transfer Initiative: Discussing data portability and related moderation concerns.
  • ...