Socialwg

From W3C Wiki
Jump to: navigation, search

Welcome to the Social Web Working Group (SocialWG) home page (https://www.w3.org/Social/WG)!

Social Web Working Group

2016-09-23-socialwg-group-animated.gif
Photo of the W3C Social Web Working Group taken at Face to Face Meeting, 2016-09-23 at TPAC in Lisbon, Portugal.
Chairs
Tantek Çelik (Mozilla)
Evan Prodromou (e14N)
Arnaud Le Hors (IBM) (through 2016-09-23)
Staff Contacts
Amy Guy (W3C/University of Edinburgh) (since July 2016)
Sandro Hawke (W3C/MIT)
Harry Halpin (W3C/MIT) (until Fall 2015)

Specifications

Specifications that the Social Web WG has produced and is working on.

Recommendations

Proposed Recommendations

  • none currently

Candidate Recommendations

Working Drafts

Overview:

Iterating as working drafts:

Editors Drafts

  • no more REC-track documents planned for current charter.

Specification Related

  • List of github aliases of Social Web WG contributors: Socialwg/Github
  • Resolutions - e.g. to accept & publish drafts, for controversial issues, etc.

Proposals

Proposed documents to the working groups (as of 2016-09-23 only accepting documents proposed as Notes)

  • ...

Participation

Members

How to participate

To join this group

If you are officially added to the group, you will automatically receive group email and your w3.org login and password will work on this wiki.

Discussion

We currently use IRC, email, telcons, and face-to-face meetings for discussion:

IRC

The working group uses IRC nearly daily, and very actively during and after the telcons.

The IRC channel is logged on the publicly-visible URL above. You can bookmark the URL and it will redirect to the current day.

You can get your photo to appear next to your name in the logs by:

Email

We have two mailing lists for informal discussions for those that like email. You don't have to use them to participate in the working group.

 
Dedicated to Social Web Working Group discussions. See public-socialweb archive. Read-write for WG members. Read-only for non-members.
 
For Social Web public discussions. See public-socialweb-comments archive. Read-write for all, WG members and non-members alike.

Meetings

Weekly telecons take place on Tuesdays at 11:00 US/Eastern (08:00 US/Pacific, 17:00 Paris, etc), as determined by proposal to for a better time for Asia and informal consensus without objections.

Our two chairs -- Tantek and Evan -- alternate chairing the telecons but both are expected to attend (and chair if necessary). Agenda items for a telecon should be posted to its wiki page by the Friday before, no guarantee of getting to anything posted after that.

Telecon Information

IRC is a key element of how W3C teleconferences are run, please join the IRC channel (#social) before dialing in!

  • Join IRC (#social) before dialing in
  • Join WebEx by following the instructions at https://www.w3.org/2015/10/social-wg-telecon. (Please keep those instructions secret.) If that link doesn't work for you, contact sandro@w3.org.

Once you are connected to WebEx, select "Call Using Computer" (large 'button' on left), to have WebEx make the audio connection to you

  • Choices: WebEx can call you, or you can call in.
  • (Note: when using "Test Audio Connection", you will be muted).


If you cannot use WebEx, the host can initiate a call to you.

  1. The W3C Contacts have a "host key". When one of them starts the WebEx session, they should enter that number, to be identified as the host.
    1. If anyone else is chairing, get host key from Amy or Sandro
    2. In "Participant" menu (top left), choose "Reclaim host role"
  2. Once you are the host, the "Invite and Remind" button becomes available (in middle of WebEx session screen)
  3. In the "Invite and Remind" window, select the tab for "Phone"
  4. Enter the person's name and phone number, and click "Call"
  5. That person will be called, and needs to follow the prompt ("press 1") to enter the meeting

Note we are no longer using Zakim for dialing-in, but we are still using IRC for meetings.

Next Meeting

telcon: Social Web WG telcon:

Future Meetings

  • 2017-02-14 Telecon
  • 2017-03 Telecon (date TBD at 2017-02-14 Telecon)
  • 2017-03-20…24 Possible 2-3 day f2f at MIT if we're ready for a CR to PR push for specs (note: week before Libreplanet, also at MIT)
  • 2017-04 Telecon (date TBD)
  • 2017-04 Possible 2-3 day f2f at West Coast or East Coast if we're ready for a CR to PR push for specs
  • 2017-05 Telecon (date TBD)
  • 2017-06 Telecon (date TBD, last telcon)
  • 2017-06-30 charter extension period ends.

Additional social web related future events:

Regrets

In case you can not participate in next meeting, please add your name to Regrets section on Agenda page of next telecon. If you sending last minute regrets and don't have possibility to edit wiki page, please say so on #IRC. If you are both unable to edit the wiki and use IRC you may send mailto:public-socialweb@w3.org with your regrets.

Identifying yourself

For record keeping it is important that everyone attending our teleconference is identified. W3C's IRC bot, Zakim, which helps facilitate meetings using IRC in conjunction with the W3C's audio teleconference bridge, can help identify you but there are cases when Zakim needs your input. It is therefore important that before you call in, you first join the IRC channel (#social) and monitor it. For more info on this refer to Zakim's page.

Past Meetings

Scribes

As a scribe, after you're done minuting into IRC for a given date, e.g. 2014-10-14:

  1. Get the source of http://www.w3.org/2014/10/14-social-minutes.html (should have been generated by RRSAgent after chair asked for "trackbot, end meeting" in IRC)
  2. Convert from HTML to Mediawiki syntax, either:
    • Locally run it through pandoc with command: pandoc -f html -t mediawiki -o output-minutes.wiki input-minutes.html
    • or try this online converter (experimental! Comments/bug reports to rhiaro).
  3. Use Socialwg/2014-10-07-minutes as a template to create Socialwg/2014-10-14-minutes
  4. Add any resolutions from the meeting to Socialwg/resolutions

Documentation

To document proposals, ideas, even specifications that are social web related, please create pages for them on this wiki and add a link to them from here.

Naming

You may preface your page names with "socialwg/" if you pick a particularly generic name and/or wish to indicate the scope in the name.

Glossary

Social Web Glossary - precise definitions for terms we use in specs and documentation

Use Cases

So far WG adopted only one use case from previous work in this field: SWAT0

Old:

Social Data Syntax

Social Vocabulary

Main effort moved to Task Force in Interest Group - Socialig/Vocabulary_TF

Social API

API research

API candidates

Federation

Federation candidates

Inputs Into SocialWG

Inputs into SocialWG, including specs from External Groups explicitly listed in the Charter.

Activity Streams

Main article: Activity Streams

See #Specifications at the top of this page for Activity Streams editor's drafts, issues, and github repo links.

IndieWeb

Adopted into the group (see [#Specifications]] at the top of this page)

Normatively referenced:

Informatively referenced:

Additional:

Dependent Work

Work we don't expect to accomplish as part of this charter but which we need to keep in mind while making decisions about the architecture. This includes both work that is already partly defined, and work that isn't but falls outside of our charter.

Hypotheticals

Documentation which is abstract (i.e. lacking documented real world use-cases).

There are likely additional documents above that need to be moved here.

Implementations

Process

Workmode

The Social Web Working Group workmode is roughly as follows, and may be iterated based on group experience:

  • GitHub - for all specifications and technical issues
  • #Discussion - use IRC, telcons, email for discussion only
  • #Documentation - capture proposals and conclusions here on the wiki

Tracker

Issues for each specification are managed in the GitHub repo for each specification. See top of page for those links.

Issues and Actions for the working group overall were managed via the W3C Tracker. See Social Web WG Tracker.

Resolutions

resolutions will be highlighted in minutes, and people not at meeting can bring up their concerns within the following week

sched

A rough schedule for the work of the WG, originally based on Social Web WG Charter Milestones.

Social data syntax

  • Review: Jul-Sep 2014
  • Commit: Oct 2014
  • First public working drafts: AS2 Oct 2014 (and PTD Jul 2016)
  • LC: likely late 2015/early 2016 (charter v1 said Q3 2015)
  • CR: Q3 2016 (charter v1 said Q4 2015)
  • Test Suite Feature Complete:
  • PR: likely Feb 2017 (charter v1 said Q2 2016)
  • REC: possibly Mar 2017 (charter v1 said Q3 2016)
  • 2016-12-31 Charter period ends (proposing extension til 2017-06-30)

Social API

  • Review: Nov 2014 - ongoing (original review end date was Mar 2015)
  • Commit: Dec 2015 decided to develop both Micropub and ActivityPub as Working Drafts
  • First public working drafts: Jan 2016 (charter v1 said Q3 2014)
  • LC: Q2/Q3 2016 (charter v1 said Q3 2015)
  • CR: Q3/Q4 2016 (charter v1 said Q4 2015)
  • Test Suite Feature Complete:
  • PR: likely Jan/Feb 2017 (charter v1 said Q2 2016)
  • REC: likely Feb/Mar 2017 (charter v1 said Q3 2016)
  • 2016-12-31 Charter period ends (proposing extension til 2017-06-30)

Federation protocol

  • Review: completed with three approaches
  • Commit: Webmention, ActivityPub server to server (see above for links), LDN
    • Dec 2015 decided to start with Webmention
  • First public working draft: Jan, Jul, Oct 2016 (charter v1 was Q4 2014, then Aug 2015)
  • LC: Q2 2016 (charter v1 said Q4 2015)
  • CR: Q2&Q4 2016 (charter v1 said Q2 2016)
  • Test Suite Feature Complete:
  • PR: Q4 2016 (charter v1 said Q3 2016)
  • REC: likely Q4 2016 (charter v1 said Q4 2016)
  • 2016-12-31 Charter period ends.

Media

Related Organizations

The Social Web Working Group actively coordinates with several other groups, organizations, and communities.

per our charter:

Dependencies

External Groups

Additional Active Coordination

In addition to the above, the working group has been actively coordinating with:

Closed

and previously (2014?) Socialig/Liaison_TF did some early coordination.

All Social Web Related CGs

Current incubation CG:

The following CGs either incubated drafts which the working group took on, previously worked on or otherwise contributed in-charter-scope materials/ideas to the working group, and are planned for closure and incorporation into SWICG.

Other Misc Groups

Other groups that were previously listed here but either nothing that was incoporated into anything in the working group, or orthogonal building blocks (could likely trim this section or move to a separate page)

Applied for Membership

Tantek Çelik has encouraged people who have applied for invited expert membership to list themselves here, but there is no requirement to do so.

https://www.w3.org/wiki/Socialwg/invited-experts

Include the date you submitted the form.

  • Michael Vogel Friendica maintainer github No Application Received. After applying, put the date here.

Invited Expert Approval

To be approved as an invited expert, one or more of the chairs and/or W3C staff contact and/or their management have to vouch for you. They likely have different criteria for vouching, and may or may not document (all of) their criteria publicly. E.g. chairs & staff contacts:

Tantek

Tantek Çelik:

  • For me, an expert on the social web MUST be actively publishing social content on their own website. Merely sharecropping on silos or contributing to open source projects only makes you a hobbyist, not an "expert". -Tantek

Evan

Evan Prodromou

  • For me, an invited expert should be implementing social software, or represent a company implementing social software.

Arnaud

Arnaud Le Hors

  • Given the applicability of this technology behind the firewall of an enterprise, I don't share Tantek's view on what constitutes an expert in the matter.
  • In keeping with the W3C Process I will consider applications for Invited Expert status on a case by case basis. It's fair to say that I'm rather conservative in that matter, which means that by default requests will be declined. Invited Experts are typically well known to the community through participation in different forums, conferences, etc. When that's not the case, applicants have the burden of convincing the chairs and Team that they should still be granted this status by explaining why. Invited Expert status is a privilege, not a right.

FAQ

Please add questions which have been answered in IRC by the chairs here:

  • ...

Am I Relevant To This WG

Q: Am I important or relevant to this working group?

A: Do you:

  • implement social web technologies?
  • or publish social content on a website you control? (social content, from you to others, regarding yourself and/or others, blogrolls (e.g. using XFN for social relationships, e.g. http://schepers.cc/ )

Or both? In either case, the working group can use your input relating to your personal experience with doing so.

Teleconferences

Q: Will the teleconference call audio be made public after the meeting?

A: No. However, they will be annotated by a scribe and minutes will be made publicly available shortly after a working group meeting. For example socialwg/2014-09-02-minutes.

What is the role of the WG IG CG

Note: Social IG has been closed. Federated Social Web CG is being transitioned to Social Web Incubator CG.

Q: We should clarifiy the role of Social Web WG & IG and Federated Social Web CG?

A: Community groups are free form, can produce documents but binding only to members of that community group. Working groups are in charge of producing actual specifications and have set time to deliver.[1] The Social Web Working Group (WG) has a charter with fairly specific deliverables (syntax, API, protocol) that it is focusing on. The Social Web Interest Group also had a charter which is focused on the research and documentation of social web use-cases.

Past

Some background and past of the working group.

Previous W3C Groups

2012

2013

2014

2015 unofficial social media

Unofficial social media created by former working group participants:

Facebook group
https://www.facebook.com/social.w3.org (UNOFFICIAL, run by WG participant elf Pavlik)
Twitter account
https://twitter.com/SocialWebWG (UNOFFICIAL, was run by Erik Wilde, WG participant til 2015-07-07)
  • Anyone have contact info for Erik? Can you get the keys to @SocialWebWG and send them to to chairs? - Tantek Çelik (talk)

Past Work Items

Past work items that the working group has dropped:

Home Page To Do

To Do for our group home page in particular.

Problem: "It's kind of overwhelming" (aaronpk, IRC 2016-04-19)

Goal: smaller, simpler, shorter page that you could send to someone not in the group, to let them know what the group is doing

Some tasks:

  • "Documentation" section - most of that should be moved to a Socialwg/research page - it's background for work that we're doing
    • the red links in Documentation should just be deleted
    • some stuff like the Use Cases and Inputs Into SocialWG should be separated out
  • "Related Organizations" could be moved to a subpage
  • "Invited Expert Application" and "FAQ" could also be moved to subpages

See Also

Retrieved from "https://www.w3.org/wiki/index.php?title=Socialwg&oldid=101036"