socialwg Teleconf 2014-10-07
Tuesdays at 10am US/Pacific, 1pm US/Eastern time for 60 minutes
- Check your timezone
- Dial-in +1-617-761-6200 , SIP Instructions, Zakim Code "SOCL"
- 1 Previous Meeting
- 2 Agenda
- 2.1 Preamble
- 2.2 Admin
- 2.3 Tracking of Actions and Issues
- 2.4 IndieWeb stack support of JSON (JSON-LD)
- 2.5 Activity Streams 2.0
- 2.6 Social API candidates
- 2.7 Social API requirements
- 2.8 Adjourn
- Chair: Evan Prodromou
- Scribe: or next available from Scribes list
Chair to start the meeting by typing on irc:
trackbot, start meeting
Trackbot should already be on the channel but if for some reason it is not call it with the following command:
Pick a scribe from the list or ask Zakim to pick one up with the following command:
Zakim, pick a victim
Unfortunately Zakim has no idea who's scribed before so you may have to ask several times before getting an acceptable answer...
For additional info, see the Zakim documentation page.
- Participation is limited to members
Approval of Minutes of 30 September 2014 Teleconf
Next week Teleconf
- IndieWebCamp Cambridge.
Tracking of Actions and Issues
- Tracker: http://www.w3.org/Social/track/
IndieWeb stack support of JSON (JSON-LD)
Group charter puts JSON serialization as requirement. We have submission of various technologies from IndieWebCamp community which currently may not support JSON
We may also face some tensions related to JSON-LD. While majority of group members express support for it, few people oppose and historically JSON-LD may have negative reception in IndieWebCamp circles
Activity Streams 2.0
Discussion of AS 2.0
We're reviewing AS 2.0 for 10/14. This is a good time for questions and comments. http://www.w3.org/2014/Process-20140801/#working-draft
ActivityStreams 2.0 compatibility with AS1.0 and JSON-LD
We have over due action to explain compatibility of AS2.0 with JSON-LD
elf Pavlik also requested list of design choices motivated by backward compatibility with AS1.0
we could do simple straw man pool just to clarify opinions present in the group, just as we already did once for JSON-LD
Possibly those two compatibility requirements don't align very well!
Social API candidates
- Per our Socialwg#sched Schedule we should be evaluating social API candidates and picking a direction this month.
Social API requirements
- Review Socialwg/API requirements
Chair to close the meeting with the following command:
trackbot, end meeting
If you forget, trackbot will close the meeting for you when the activity dies down.
back to socialwg