socialwg3-summary
type: Article
has reply: testlink2.html
has reply: testlink3.html
has reply: https://twitter.com/transformap/status/599195157636984833
tmpcontent: # Social Web WG 3rd face-to-face summary *This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG!* **tl;dr:** There is increased understanding and expectation of convergence between Micropub, ActivityPump and SoLiD. We're all excited about working towards this convergence. There is increased agreement and understanding about similarities and differences between protocols, and where strong points of one protocol could plug weak points in another. More people are excited about implementing experiments to really figure out what works and what doesn't. See also [day 1 minutes](https://www.w3.org/wiki/Socialwg/2015-05-04-minutes) and [day 2 minutes](https://www.w3.org/wiki/Socialwg/2015-05-05-minutes) and [self-critique whiteboard](http://aaronparecki.com/uploads/whiteboard-20150505-161540.jpg). What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. ## Issues in the tracker Closed a bunch of ActivityStreams2.0 issues with the general conclusion that issues raised in future should be more specific and actionable, rather than vague problems. An alternative for reporting this kind of issue wasn't mentioned specifically, but vague problems can probably go in brainstorming sections on the wiki somewhere (indieweb style) or into github issues. A note that we can always re-open issues if they turn out to be a problem in the future, but we shouldn't *keep* them open just in case they might be. ## Awesome user-story protocol walkthroughs [Aaron](http://aaronpk.com), Jessica and Andrei and Henry walked us through exactly how some of the user stories would be carried out according to the protocols [Micropub](https://github.com/aaronpk/Micropub/blob/master/user-stories/), [ActivityPump](https://github.com/w3c-social/activitypump/tree/master/userstories) and [SoLiD](https://github.com/linkeddata/SoLiD/blob/master/UserStories/) respectively. This was *super* use…
actor: me
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! tl;dr: There is increased understanding and expectation of convergence between Micropub, ActivityPump and SoLiD. We're all excited about working towards this convergence. There is increased agreement and understanding about similarities and differences between protocols, and where strong points of one protocol could plug weak points in another. More people are excited about implementing experiments to really figure out what works and what doesn't. See also day 1 minutes and day 2 minutes and self-critique whiteboard. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. Issues in the tracker Closed a bunch of ActivityStreams2.0 issues with the general conclusion that issues raised in future should be more specific and actionable, rather than vague problems. An alternative for reporting this kind of issue wasn't mentioned specifically, but vague problems can probably go in brainstorming sections on the wiki somewhere (indieweb style) or into github issues. A note that we can always re-open issues if they turn out to be a problem in the future, but we shouldn't keep them open just in case they might be. Awesome user-story protocol walkthroughs Aaron, Jessica and Andrei and Henry walked us through exactly how some of the user stories would be carried out according to the protocols Micropub, ActivityPump and SoLiD respectively. This was super useful, and if you weren't there you need to read the accompanying documents (linked just prior) and minutes (linked at the top of this post). Results of this were: Proponants of each protocol started to really understand how the other protocols worked, in a way that just reading all the specs couldn't do. Everyone really started to see where some protocols were strong and where their own weak points or gaps were. Everybody started to express that their…
name: Social Web WG 3rd face-to-face summary
published: 2015-05-09T23:45:00+0200
tag: doing
tag: Doing
tag: meeting
tag: social+web
tag: socialwg
tag: w3c

todays-socialwg
type: Note
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/605785189474639873/630517931
tmpcontent: Today's SocialWG telecon location: ![best office](https://rhiaro.co.uk/photos/1505portoroz/socialwgsea.jpg) And the SIP connection is better here than in my office, which seems like a perfectly reasonable justification for staying here always.
actor: me
content: Today's SocialWG telecon location: And the SIP connection is better here than in my office, which seems like a perfectly reasonable justification for staying here always.
latitude: 45.51727
longitude: 13.56933
published: 2015-06-02T18:14:20+0100
summary: Amy wrote about travel, socialwg, beach, meeting, & sea
tag: beach
tag: meeting
tag: sea
tag: socialwg
tag: travel

sociam-hands
type: Event
tmpcontent: # SOCIAM all-hands
actor: me
end time: 2015-09-23T19:00:00+0100
in reply to: sociam.org
location: Oxford
name: SOCIAM all-hands
published: 2015-09-22T12:04:38+0100
start time: 2015-09-22T13:30:00+0100
tag: decentralised
tag: event
tag: meeting
tag: phd
tag: rsvp
tag: social+web
tag: sociam

socialwg4-summary
type: Article
tmpcontent: # Social Web WG 4th face-to-face summary *This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG!* See also [day 1 minutes](https://www.w3.org/wiki/Socialwg/2015-12-01-minutes) and [day 2 minutes](https://www.w3.org/wiki/Socialwg/2015-12-02-minutes). What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. ## tl;dr ## * Most AS2 issues are closed! CR-blocking issues are now due by 15th December. * We took a bunch of things to Editor's Draft and are pushing for FPWDs as soon as is viable. * Some of the drafts overlap but there's a general feeling that since there are keen editors we should work on everything and iron out issues and redundancies as we go, rather than holding out and waiting for clarity. * Go check out the specs and build bits of them and give the editors feedback! ## ActivityStreams 2 We steamrollared through AS2 issues, which included core simplifications, vocabulary changes and reductions and editorial clarifications. James made most edits during the meeting, so there's [a much updated working draft](http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/index.html) available now. You should read it and post any issues you see to be CR-blocking by the 15th of December. JSON-LD related stuff has been moved to its own section; since it is optional, having references sprinkled throughout was confusing for people who don't necessarily want to deal with it. [Chris](https://dustycloud.org) pointed out that even for extensions, if you know the extension you want to handle you can still do that in plain JSON. Still some consternation about which alternative syntax examples should be in the spec. Since they're non-normative/editorial anyway they're not a CR-blocker so left alone for the time being. We don't need a verison number in the URL because any future widely-deployed extensions that want to make it into the cor…
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. tl;dr Most AS2 issues are closed! CR-blocking issues are now due by 15th December. We took a bunch of things to Editor's Draft and are pushing for FPWDs as soon as is viable. Some of the drafts overlap but there's a general feeling that since there are keen editors we should work on everything and iron out issues and redundancies as we go, rather than holding out and waiting for clarity. Go check out the specs and build bits of them and give the editors feedback! ActivityStreams 2 We steamrollared through AS2 issues, which included core simplifications, vocabulary changes and reductions and editorial clarifications. James made most edits during the meeting, so there's a much updated working draft available now. You should read it and post any issues you see to be CR-blocking by the 15th of December. JSON-LD related stuff has been moved to its own section; since it is optional, having references sprinkled throughout was confusing for people who don't necessarily want to deal with it. Chris pointed out that even for extensions, if you know the extension you want to handle you can still do that in plain JSON. Still some consternation about which alternative syntax examples should be in the spec. Since they're non-normative/editorial anyway they're not a CR-blocker so left alone for the time being. We don't need a verison number in the URL because any future widely-deployed extensions that want to make it into the core will likely be incorporated as part of a full new version (ie. AS3). At some point we should start a registry for extensions; James is keeping track himself on github, we could move this to a wiki page and ultimately a CG when the WG wraps up. Lots of discussion about testing framew…
name: Social Web WG 4th face-to-face summary
published: 2015-12-07T23:59:00+0000
tag: activitypump
tag: activitystreams
tag: as2
tag: federation
tag: indieweb
tag: jf2
tag: meeting
tag: mf2
tag: microformats
tag: micropub
tag: phd
tag: social+protocols
tag: social+web
tag: socialapi
tag: socialwg
tag: standards
tag: w3c
tag: webmention

qcri-project
type: Travel
rsvp: yes
end time: 2016-03-23T17:00:00+03:00
in reply to: crosscloud.org
location: Doha
name: QCRI Project meeting
published: 2016-02-21T16:00:57-05:00
start time: 2016-03-20T09:00:00+03:00
summary: Amy planned a trip from to
tag: attendee
tag: crosscloud
tag: event
tag: meeting
tag: mit
tag: phd
tag: qcri
tag: rsvp
tag: social+web
tag: solid
tag: travel

sociam-hands
type: Travel
rsvp: yes
end time: 2016-02-26T15:00:00+00:00
in reply to: sociam.org
location: Brockenhurst
name: SOCIAM All-hands
published: 2016-02-21T15:58:03-05:00
start time: 2016-02-24T10:00:00+00:00
summary: Amy planned a trip from to
tag: attendee
tag: event
tag: meeting
tag: phd
tag: rsvp
tag: social+machines
tag: sociam

socialwg5-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. We met in Boston on 16 and 17 March. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. ActivityStreams2 AS2 is inching closer to CR. Evan has made a validator at as2.rocks and done a lot of work on conformance criteria which we went through as a group and updated a little; mostly changing SHOULDs to MUSTs. Discussed and not necessarily resolved a few new open issues, including: considering dropping the Relationship object and reviving it as an extension if necessary; a proposal for a new property to say when something was deleted; weakening the SHOULD requirement on name; clarifying scope and context. Stay tuned for a new working draft sometime soon. SocialPub The most exciting thing I thought was agreeing on the potential for convergence between the create, update and delete parts of Activitypub and Micropub. Micropub started life as a super small and simple way for clients and servers to agree how to create content on a website by POSTing form encoded parameters to an endpoint. As a result of this simplicity, there are dozens of client and server implementations, allowing people to use each others posting clients to add posts to their site, from simple text-only posts to photos, events, RSVPs, likes, bookmarks, reposts. When Micropub needed update and delete, it grew beyond what form-encoded parameters could sensibly handle, and added in a JSON syntax which I think to date only the editor has implemented. Activitypub uses a JSON syntax (ActivityStreams2) from the outset for create, update and delete, and when you compare this with the Micropub JSON they look remarkably similar. My posting endpoint implements create the AP way, and endpoint discovery the MP way. It also catches Micropub form-encoded requests and translates them to AS2 JSON b…
name: 5th Social WG F2F Summary
published: 2016-03-29T10:43:39+01:00
tag: activitypub
tag: activitystreams
tag: as2
tag: meeting
tag: micropub
tag: phd
tag: social+web+protocols
tag: social+web
tag: socialpub
tag: socialwg
tag: standards
tag: w3c
tag: webmention

socialwg6-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. We met in Portland on 6th and 7th June. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. This doesn't cover everything we talked about in detail; as well as the following, we resolved (or at least discussed) issues on all of the specs, and took a few to new Working Draft status. Demos I demoed my ActivityPub implementations; clients Burrow for checkins, Obtainium for consumption/purchase logging, Replicator for food logging and Seeulator for journeys and events. These all do create only by sending either appropriate activities (including some extensions) to my activitypub endpoint (aka outbox, but not discoverable as such yet). Seeulator creates the right kind of activity based on what attributes are filled in or left blank, essentially doing post-type discovery - albeit my own algorithm rather than tantek's spec from the user input to generate the right as:Activity. The newer thing I worked on was a client that only does updates of existing AS2 data. I wanted this so I could add captions to all my photos at img.amy.gy, so Morph does just that. This also means it has to be able to read/consume the AS2 data published at img.amy.gy about as:Collections of photos. Aaron demoed the Webmention test suite at webmention.rocks and notes that there are Webmention Rocks stickers available for people submitting implementation reports.. Aaron also demoed a new feature in the Micropub spec which is the media endpoint. After some discussion recently it was established that all mainstream social APIs seem to post media (like images) that have been embedded in a post to a separate endpoint, then embed the returned URL in the post content, and MediaGoblin does this too. Aaron's implementation in Quill is really swish looking, uploading the file to the discov…
name: 6th Social WG F2F Summary
published: 2016-06-25T17:39:36+01:00
tag: activitypub
tag: activitystreams
tag: as2
tag: meeting
tag: micropub
tag: phd
tag: posttypediscovery
tag: protocols
tag: social
tag: socialwg
tag: standards
tag: w3c
tag: web
tag: webmention

socialwg8
type: Accept
content: Our final spec party.
generator: sloph
object: https://www.w3.org/wiki/Socialwg/2016-11-17
published: 2016-11-09T04:46:00+09:00
summary: Amy RSVP'd to https://www.w3.org/wiki/Socialwg/2016-11-17
tag: meeting
tag: phd
tag: socialwg

week-review-2nd--
type: Article
content: Ran to Seafields. Attended the DID Working Group not-face-to-face meetings (a good time!). Fell ever further behind on nanowrimo, but kept plugging away. Invested in a bike helmet and lock... ...went cycling! With some random friendly locals, during a torrential downpour (not really random, it was a Greener Kirkcaldy community bike ride, but I was the only one who showed up). Attended a Social Web Incubator CG meeting and got some stuff done for a vocab collaboration with the DID WG.
generator: no-ceremonies-are-necessary
name: Week in review: 2nd - 8th Nov
published: 2020-11-08T23:59:59+00:00
tag: life
tag: week+in+review
tag: socialwg
tag: decentralisation
tag: didwg
tag: w3c
tag: event
tag: meeting
tag: nanowrimo
tag: cycling

early-starts-late
type: Note
content: The early starts and late finishes and squeezing the day job into the gap in the middle were a lot, but I really enjoyed this week's virtual TAG face-to-face. Productive, and fun! Can't wait til we can do it in three dimensions though.
generator: no-ceremonies-are-necessary
published: 2021-05-14T09:30:05+01:00
tag: w3c
tag: w3ctag
tag: web+standards
tag: meeting

week-review-21st-
type: Article
content: Went to London. Got total culture shock. Too many people in too small spaces. No stars. so loud. Started The Lefthanded Booksellers of London (though I haven't finished The Overstory but the former was lighter for taking on a trip. Also thematically appropriate.) Recorded a podcast?! (as a guest). Had IRL TAG meetings! Did IRL Co-op coworking! Saw IRL friends I haven't seen for years! Returned from London. Two-day long migraine immediately went.
generator: no-ceremonies-are-necessary
name: Week in review: 21st - 27th March
published: 2022-03-27T21:49:27+01:00
tag: travel
tag: food
tag: vegan
tag: week+in+review
tag: cooplife
tag: ods
tag: w3ctag
tag: tag
tag: w3c
tag: standards
tag: london
tag: meeting

dysart-edinburgh
type: Travel
content: Co-op governance coworking.
end time: 2022-06-24T09:13:00+01:00
name: Dysart to Edinburgh
origin: kirkcaldy-fife
published: 2022-06-24T06:18:12+01:00
start time: 2022-06-24T07:50:00+01:00
summary: Bus from Dysart to Edinburgh
tag: travel
tag: transit
tag: bus
tag: coop
tag: odsc
tag: work
tag: meeting
target: edinburgh

edinburgh-dysart
type: Travel
content: Return from Co-op coworking.
end time: 2022-06-24T21:43:00+01:00
name: Edinburgh to Dysart
origin: edinburgh
published: 2022-06-24T19:19:04+01:00
start time: 2022-06-24T20:30:00+01:00
summary: Bus from Edinburgh to Dysart
tag: travel
tag: transit
tag: bus
tag: odsc
tag: coop
tag: work
tag: meeting
target: kirkcaldy-fife

https://rhiaro.co.uk/2022/07/62a5905a17886
type: Acquire
type: Activity
amount gbp: 50.4
cost: 50.40gbp
expensed to: digitalbazaar.com
content: Train from Edinburgh to London
generator: latinum
published: 2022-07-24T08:04:54+01:00
tag: tag
tag: w3c
tag: meeting
tag: w3ctag
tag: train
tag: travel
tag: transport
tag: transit

meeting
type: Collection
total items: 31

https://rhiaro.co.uk/tags/meeting
type: CollectionPage
items: https://rhiaro.co.uk/2022/07/62a5905a17886
items: edinburgh-dysart
items: dysart-edinburgh
items: week-review-21st-
items: early-starts-late
items: week-review-2nd--
items: socialwg8
items: socialwg6-summary
items: socialwg5-summary
items: qcri-project
items: sociam-hands
items: socialwg4-summary
items: todays-socialwg
items: socialwg3-summary
name: meeting
next: https://rhiaro.co.uk/tags/meeting
part of: meeting