{"@context":{"rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#","rdfs":"http://www.w3.org/2000/01/rdf-schema#","owl":"http://www.w3.org/2002/07/owl#","foaf":"http://xmlns.com/foaf/0.1/","dc":"http://purl.org/dc/elements/1.1/","dct":"http://purl.org/dc/terms/","sioc":"http://rdfs.org/sioc/types#","blog":"http://vocab.amy.so/blog#","as":"https://www.w3.org/ns/activitystreams#","mf2":"http://microformats.org/profile/","ldp":"http://www.w3.org/ns/ldp#","solid":"http://www.w3.org/ns/solid#","view":"https://terms.rhiaro.co.uk/view#","asext":"https://terms.rhiaro.co.uk/as#","dbp":"http://dbpedia.org/property/","geo":"http://www.w3.org/2003/01/geo/wgs84_pos#","doap":"http://usefulinc.com/ns/doap#","time":"http://www.w3.org/2006/time#"},"@graph":[{"@id":"https://rhiaro.co.uk/2015/10/1445051305","@type":"as:Announce","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:object":{"@id":"https://twitter.com/veganstraightedge/status/655218568024498176"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-10-17T04:08:25+0100"},"as:summary":"Amy shared https://twitter.com/veganstraightedge/status/655218568024498176","as:tag":[{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/vegan"}]},{"@id":"https://rhiaro.co.uk/2015/10/1446071359","@type":"as:Announce","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"","as:object":{"@id":"https://twitter.com/benwerd/status/659393035109724160"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-10-28T22:29:19+0000"},"as:summary":"Amy shared https://twitter.com/benwerd/status/659393035109724160","as:tag":[{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/socialwg"}]},{"@id":"https://rhiaro.co.uk/2015/10/suddenly-meet","@type":"as:Article","sioc:has_reply":[{"@id":"https://brid-gy.appspot.com/like/twitter/rhiaro/655205448849690624/52332354"},{"@id":"https://twitter.com/natematias/status/655206160845426688"},{"@id":"https://twitter.com/natematias/status/655206300171784192"},{"@id":"https://twitter.com/rhiaro/status/655207641124372480"},{"@id":"https://twitter.com/veganstraightedge/status/655218568024498176"}],"blog:tmpcontent":"# In which I suddenly meet people from the internet\r\n\r\nToday set out to be a quiet day of working/procrastinating from home, then a flurry of last minute plans and serendipity meant I got to meet people I previously only knew of online, and have some good conversations that will lead to future exciting work and travel related things. Sweet!\r\n\r\nAt short notice, [my roommate Liz](https://twitter.com/lizpowersss) invited me sailing on the Charles. When we got there there were no boats available, but some friendly strangers had space in theirs and picked us up. One of those strangers happened to be [Nate](http://natematias.com), whose Microsoft Research blog posts I'd read this summer and who had been twitter-introduced to me a couple of months ago by our mutual friend [Doc](http://jamesdoc.com). I'd been meaning to follow up and find time to meet up with him. After about 15 minutes of chatting with him and his friends in their boat, I realised who I was talking to. What are the odds?! Nate's research is relevant to mine, and he recommended a seminar group I should attend; bumping into him this way was an incredible stroke of luck!\r\n\r\n![MIT sail](https://rhiaro.co.uk/photos/15boston/151016_sailing1.jpg)\r\n\r\n![Sailing on the Charles](https://rhiaro.co.uk/photos/15boston/151016_sailing2.jpg)\r\n\r\n![Amy & Nate](https://rhiaro.co.uk/photos/15boston/151016_amynate.jpg)\r\n\r\nEarlier today I learned that [Shane](http://veganstraightedge.com) is in town for a couple of days as part of a roadtrip around the US, so I met him and [Morgan](https://twitter.com/mofo37) for dinner, and we talked [indieweb](https://indiewebcamp.com), travel and vegan food for a few hours. And I *might* now have exciting and exotic christmas plans as a result.\r\n\r\n![Amy & Shane](https://rhiaro.co.uk/photos/15boston/151016_amyshane.jpg)","as:content":"
Today set out to be a quiet day of working/procrastinating from home, then a flurry of last minute plans and serendipity meant I got to meet people I previously only knew of online, and have some good conversations that will lead to future exciting work and travel related things. Sweet!
\r\nAt short notice, my roommate Liz invited me sailing on the Charles. When we got there there were no boats available, but some friendly strangers had space in theirs and picked us up. One of those strangers happened to be Nate, whose Microsoft Research blog posts I'd read this summer and who had been twitter-introduced to me a couple of months ago by our mutual friend Doc. I'd been meaning to follow up and find time to meet up with him. After about 15 minutes of chatting with him and his friends in their boat, I realised who I was talking to. What are the odds?! Nate's research is relevant to mine, and he recommended a seminar group I should attend; bumping into him this way was an incredible stroke of luck!
\r\n\r\n\r\n\r\nEarlier today I learned that Shane is in town for a couple of days as part of a roadtrip around the US, so I met him and Morgan for dinner, and we talked indieweb, travel and vegan food for a few hours. And I might now have exciting and exotic christmas plans as a result.
\r\n","as:name":"In which I suddenly meet people from the internet","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-10-17T03:12:00+0100"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/boston"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/jamesdoc"},{"@id":"https://rhiaro.co.uk/tags/life"},{"@id":"https://rhiaro.co.uk/tags/mit"},{"@id":"https://rhiaro.co.uk/tags/mofo27"},{"@id":"https://rhiaro.co.uk/tags/natematias"},{"@id":"https://rhiaro.co.uk/tags/sailing"},{"@id":"https://rhiaro.co.uk/tags/serendipity"},{"@id":"https://rhiaro.co.uk/tags/travel"},{"@id":"https://rhiaro.co.uk/tags/veganstraightedge"}]},{"@id":"https://rhiaro.co.uk/2015/11/1446953889","@type":"as:Announce","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"","as:object":{"@id":"http://aaronparecki.com/notes/2015/11/07/4/indiewebcamp"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-08T03:38:09+0000"},"as:summary":"Amy shared http://aaronparecki.com/notes/2015/11/07/4/indiewebcamp","as:tag":[{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"}]},{"@id":"https://rhiaro.co.uk/2015/11/1447269565","@type":"as:Announce","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"","as:object":{"@id":"http://agaric.com/blogs/marking-drupals-blog-posts-indieweb?utm_term=%23drupal+%23drupalcr&utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Drupal+Universe"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-11T19:19:25+0000"},"as:summary":"Amy shared http://agaric.com/blogs/marking-drupals-blog-posts-indieweb?utm_term=%23drupal+%23drupalcr&utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Drupal+Universe","as:tag":[{"@id":"https://rhiaro.co.uk/tags/drupal"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"},{"@id":"https://rhiaro.co.uk/tags/microformats"}]},{"@id":"https://rhiaro.co.uk/2015/11/indiewebcamp-mit","@type":"as:Event","blog:tmpcontent":"# Indiewebcamp MITHelping to coordinate two days of decentralised personal social hacking at IWC MIT","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"Helping to coordinate two days of decentralised personal social hacking at IWC MIT
","as:endTime":{"@type":"http://www.w3.org/2001/XMLSchema#dateTime","@value":"2015-11-08T18:00:00+05:00"},"as:inReplyTo":{"@id":"http://aaronparecki.com/events/2015/11/07/1/indiewebcamp"},"as:location":{"@id":"http://dbpedia.org/resource/Ray_and_Maria_Stata_Center"},"as:name":"Indiewebcamp MIT","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-07T03:25:12+0000"},"as:startTime":{"@type":"http://www.w3.org/2001/XMLSchema#dateTime","@value":"2015-11-07T09:00:00+05:00"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/boston"},{"@id":"https://rhiaro.co.uk/tags/events"},{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"},{"@id":"https://rhiaro.co.uk/tags/mit"},{"@id":"https://rhiaro.co.uk/tags/organising"},{"@id":"https://rhiaro.co.uk/tags/rsvp"}]},{"@id":"https://rhiaro.co.uk/2015/11/indiewebcamp-sf","@type":"as:Event","blog:rsvp":"yes","blog:tmpcontent":"# Indiewebcamp SFAttending!","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"Attending!
","as:endTime":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-12-05T02:00:00+0000"},"as:inReplyTo":{"@id":"https://kylewm.com/2015/12/indiewebcamp-sf-2015"},"as:location":{"@id":"https://kylewm.com/venues/mozilla-sf-san-francisco-california"},"as:name":"Indiewebcamp SF","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-07T03:36:30+0000"},"as:startTime":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-12-03T17:30:00+0000"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"},{"@id":"https://rhiaro.co.uk/tags/mozilla"},{"@id":"https://rhiaro.co.uk/tags/rsvp"},{"@id":"https://rhiaro.co.uk/tags/san+francisco"}]},{"@id":"https://rhiaro.co.uk/2015/11/let-records-show","@type":"as:Note","sioc:has_reply":[{"@id":"https://kylewm.com/2015/11/aw-haha-i-wish-i-could-take-credit-they-ve-always"},{"@id":"https://snarfed.org/"}],"blog:tmpcontent":"Let the records show that I will never click or tap the twitter heart icon. Apparently it explodes or something? Dumb. All twitter likes are henceforth (finally) [*fully automated*](https://bitbucket.org/rhiaro/slogd/commits/67c1fe366988a9fe13cd08fd9c07899508d14fc6) via [bridgy](https://brid.gy).\r\n\r\n(And a million thanks to [kylewm](https://kylewm.com/) for spontaneous inclusion of error logs in bridgy profile pages!)","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"Let the records show that I will never click or tap the twitter heart icon. Apparently it explodes or something? Dumb. All twitter likes are henceforth (finally) fully automated via bridgy.
\r\n(And a million thanks to kylewm for spontaneous inclusion of error logs in bridgy profile pages!)
","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-19T05:17:29+0000"},"as:summary":"Amy wrote about Kyle Mahan, hacking, indieweb, slogd, twitter, webmention, bridgy, & like","as:tag":["https://kylewm.com/",{"@id":"https://rhiaro.co.uk/tags/bridgy"},{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/like"},{"@id":"https://rhiaro.co.uk/tags/slogd"},{"@id":"https://rhiaro.co.uk/tags/twitter"},{"@id":"https://rhiaro.co.uk/tags/webmention"}]},{"@id":"https://rhiaro.co.uk/2015/11/no-sessions-yet","@type":"as:Note","sioc:has_reply":{"@id":"https://brid-gy.appspot.com/like/twitter/rhiaro/663458020970598400/369017201"},"blog:tmpcontent":"No sessions yet, but you can now sign into my site with indieauth!Thanks for help [aaronpk](http://aaronpk.com)!","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"No sessions yet, but you can now sign into my site with indieauth!
\r\nThanks for help aaronpk!
","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-08T20:47:27+0000"},"as:summary":"Amy wrote about hacking, indieweb, slogd, indiewebcamp, login, http://aaronpk.com, & indieauth","as:tag":["http://aaronpk.com",{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/http%3A%2F%2Faaronpk.com"},{"@id":"https://rhiaro.co.uk/tags/indieauth"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"},{"@id":"https://rhiaro.co.uk/tags/login"},{"@id":"https://rhiaro.co.uk/tags/slogd"}]},{"@id":"https://rhiaro.co.uk/2015/11/right-mine-does","@type":"as:Note","blog:tmpcontent":"Right, mine does a ton of metadata parsing, I put everything in the content field, it's kind of awful, but also works great..\r\n\r\n![Quill metadata hack](https://rhiaro.co.uk/posts/151110_quill.png)","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"Right, mine does a ton of metadata parsing, I put everything in the content field, it's kind of awful, but also works great..
\r\n","as:inReplyTo":{"@id":"http://kongaloosh.com/e/2015/11/10/yeah-my-micropub-endpoint-was-the-first-thing-i-built-so-that-i-could-just-use-quill-instead-of-making-my-own-forms"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-10T23:03:40+0000"},"as:summary":"Amy wrote about hacking, indieweb, slogd, editor, & client","as:tag":[{"@id":"https://rhiaro.co.uk/tags/client"},{"@id":"https://rhiaro.co.uk/tags/editor"},{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/slogd"}]},{"@id":"https://rhiaro.co.uk/2015/11/site-things-im","@type":"as:Note","blog:tmpcontent":"This site things I'm in the middle of doing / have branches for:\r\n\r\n* Auto likes and reposts to twitter using bridgy publish.\r\n* Weekly summaries of post types and minutes/hours spent doing things.\r\n* Expanding likes and reposts.\r\n* Fixing /where\r\n* Pages for vague locations.\r\n* URLs to names for person tags.\r\n* List of follows/subscriptions.\r\n* Make various feeds discoverable.\r\n\r\n[This weekend](https://indiewebcamp.com/2015/MIT), maybe I'll finish one or two of them, but I also might implement indieauth login for my site instead.","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"This site things I'm in the middle of doing / have branches for:
\r\nThis weekend, maybe I'll finish one or two of them, but I also might implement indieauth login for my site instead.
","as:latitude":"43.67896","as:longitude":"-79.61143","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-07T15:50:05+0000"},"as:summary":"Amy wrote about hacking, indieweb, slogd, & indiewebcamp","as:tag":[{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"},{"@id":"https://rhiaro.co.uk/tags/slogd"}]},{"@id":"https://rhiaro.co.uk/2015/11/tried-quill","@type":"as:Note","sioc:has_reply":{"@id":"http://kongaloosh.com/e/2015/11/10/yeah-my-micropub-endpoint-was-the-first-thing-i-built-so-that-i-could-just-use-quill-instead-of-making-my-own-forms"},"blog:tmpcontent":"Have you tried [Quill Editor](https://quill.p3k.io/editor)?\r\n\r\nAnd you could generally ask around IWC about [various interfaces](https://indiewebcamp.com/create) other people are using and see if there's one you like. You can use different things for different types of post. I'm totally going to write a checkins client soon.","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"Have you tried Quill Editor?
\r\nAnd you could generally ask around IWC about various interfaces other people are using and see if there's one you like. You can use different things for different types of post. I'm totally going to write a checkins client soon.
","as:inReplyTo":{"@id":"http://kongaloosh.com/e/2015/11/10/i-should-probably-get-brid"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-10T14:48:36+0000"},"as:summary":"Amy wrote about indieweb, blog, & editor","as:tag":[{"@id":"https://rhiaro.co.uk/tags/blog"},{"@id":"https://rhiaro.co.uk/tags/editor"},{"@id":"https://rhiaro.co.uk/tags/indieweb"}]},{"@id":"https://rhiaro.co.uk/2015/11/youre-looking","@type":"as:Note","sioc:has_reply":[{"@id":"https://brid-gy.appspot.com/like/twitter/rhiaro/662965658070724608/139199211"},{"@id":"https://brid-gy.appspot.com/like/twitter/rhiaro/662965658070724608/235193328"}],"blog:tmpcontent":"If you're looking for something to do in Cambridge this weekend, come learn/hack on personal social web stuff at [indiewebcamp](https://indiewebcamp.com/2015/MIT)","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:content":"If you're looking for something to do in Cambridge this weekend, come learn/hack on personal social web stuff at indiewebcamp
","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-11-07T12:06:14+0000"},"as:summary":"Amy wrote about hacking, indieweb, & indiewebcamp","as:tag":[{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/indiewebcamp"}]},{"@id":"https://rhiaro.co.uk/2015/12/1449205520","@type":"as:Follow","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:object":{"@id":"https://twitter.com/andigalpern"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-12-04T05:05:20+0000"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/iwcsf2015"},{"@id":"https://rhiaro.co.uk/tags/ux"}]},{"@id":"https://rhiaro.co.uk/2015/12/1450547069","@type":"as:Follow","as:actor":{"@id":"https://rhiaro.co.uk/about#me"},"as:object":{"@id":"http://whatthefuck.computer/blog/"},"as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-12-19T17:44:29+0000"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/emacs"},{"@id":"https://rhiaro.co.uk/tags/hacking"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/linux"},{"@id":"https://rhiaro.co.uk/tags/matrix"},{"@id":"https://rhiaro.co.uk/tags/quantified+self"}]},{"@id":"https://rhiaro.co.uk/2015/12/socialwg4-summary","@type":"as:Article","blog:tmpcontent":"# Social Web WG 4th face-to-face summary\r\n\r\n*This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG!*\r\n\r\nSee 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).\r\n\r\nWhat follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome.\r\n\r\n## tl;dr ##\r\n\r\n* Most AS2 issues are closed! CR-blocking issues are now due by 15th December.\r\n* We took a bunch of things to Editor's Draft and are pushing for FPWDs as soon as is viable.\r\n* 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.\r\n* Go check out the specs and build bits of them and give the editors feedback!\r\n\r\n## ActivityStreams 2\r\n\r\nWe 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.\r\n\r\nJSON-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.\r\n\r\nStill 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.\r\n\r\nWe 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.\r\n\r\nLots of discussion about testing frameworks and how to meaningfully test production and consumption of syntax and vocabulary. I refer you to the minutes, as this is beyond my ability to summarise well enough, but it seemed like the people working on this gained some clarity and a plan to move forwards.\r\n\r\n## Social API\r\n\r\n### Editor's Draft all the things\r\n\r\nThere's some contention around what it means to accept a spec as an Editor's Draft in the WG. Our general consensus was that it means a spec isn't necessarily going to be rec-track, or even the direction the group is going to take, but it's in-scope and worth some portion of our attention, even if that is just to inform other things. Most specs we've picked up are work that the editors were doing anyway, and this just means the WG should explicitly not ignore them. It's expected that the specs will change significantly going forward, in response to input from the WG.\r\n\r\nAs such, it's okay that some of our now-ED specs currently cover overlapping territory. We hope that WG attention will serve to refine, cut, expand, merge, and otherwise sort this out. We may end up multiple small specs derived from our current set of EDs which cover pieces of the social puzzle, or several specs will demonstrate multiple viable ways of doing the same thing. My preference is for the former, but the latter is better than nothing. (I tentatively extrapolate the latter into either one gets wide adoption and the others quietly fade out, or they all get equal adoption and people build bridges between them, either way not a total loss).\r\n\r\n### Social Web Protocols\r\n\r\nI finally convinced people to stop calling this \"Amy's SocialAPI Document\" and renamed everything to [Social Web Protocols](https://w3c-social.github.io/social-web-protocols/social-web-protocols). This document describes the individual componants we are trying to standardise (based on user stories), covering both the API and Federation. Given the potential for the WG to produce multiple small specs, work on this is to continue to describe and serve as a guide to each building block. This should highlight both points of convergence between separate specs, and gaps that no existing specs are filling adequately.\r\n\r\nIssues filed should be to that end. Point out obvious points of commonality between specs that I haven't noted, or where it would be worth replacing the vague overview with more spec-like details.\r\n\r\nI aim to take this to FPWD next week (which does *not* imply WG consensus on the contents yet) with the expectation that this is currently an overview document: a guide to the different areas being standardised by the WG. If we end up with a bunch of small (or overlapping) specs, this could end up as a Note, detailing how they relate to each other as a guide to implementors. If we end up with one spec that covers everything, either this becomes it following input from the other drafts, or this has done its job at converging things and is dropped completely. The rationale behind going to FPWD with this document is to better advertise and explain the different angles of work the WG is doing to other WGs and the public, and to seek wider feedback thereon. The issues become a place to discuss features based on *functionality*, where they are not specific to one of the other individual specs.\r\n\r\n### ActivityPump and Micropub\r\n\r\nBoth now EDs. Micropub covers a subsection of functionality of ActivityPump, but is uncoupled from any other pieces of functionality, whereas ActivityPump intertwines lots of things. There are distinct similarities - both POST JSON to a specific endpoint to create, update and delete content. The editors are keen to cooperate so there's value in working on them both in sync.\r\n\r\n### jf2\r\n\r\njf2 is a social syntax to complement (*not* compete with!) AS2, where jf2 is content-centric and AS2 is activity-centric. The editors of both agreed that it would be beneficial to work on these in conjunction. I've written more about [the relationship between them here](/2015/12/things-happenings).\r\n\r\n### Post type discovery\r\n\r\nPTD is an algorithm to help consumers who find themselves with implicitly typed objects to derive explicit AS2 types, if that's what they prefer to work with. My concern is that it's biased towards the microformats2 vocabulary and currently useful for a niche - but a very small niche. However, James pointed out that types are actually optional in AS2 in general, so it could be expanded to help go from untyped AS2 objects to typed ones as well.\r\n\r\nMy other concern is that this space is such a moving target, and having a fixed algorithm to derive post types based on properties is going to get dated really fast. A constantly shifting algorithm doesn't fit into W3C workflow, and of course brings its own problems (who has implemented which version as it changes over time). I don't have an answer to this.\r\n\r\n## Federation: Realisations and moving forward\r\n\r\nEvan forced us to slow down and really think about what we meant by federation. I don't know if anyone else did, but I had a bit of a lightbulb during this discussion. Bogged down in the particular bits of federation that are within reach to me (basically, notifications), I forgot there are a great many other things one might want to federate, like search, following topics, user discovery, recommendations... The WG is not required to tackle all of these, as a 'federation protocol' is the icing on our charter cake, but we absolutely don't want to de-prioritise federation completely as it's important and actually ties in well with a lot of the work we're already doing. But taking a step back to reassess - and clarify to the outside world - what we're actually doing is important, and there's some effort going into that now.\r\n\r\n### Webmention\r\n\r\nWebmention has been an ED for a short while, and there were some issues to work through. Some really interesting points have been raised around technical details, security concerns and functionality enhancements, and lots of different ways to refine this spec are emerging. We talked through open issues, and group resolutions were made for most of them.\r\n\r\nThe one I'm most interested in is addition of the [`property` parameter](http://csarven.ca/webmention) for better disambiguation of the assertion being made by a webmention. It surfaces a need of people outside of the current core webmention implementors to send and verify claims more precisely, whilst adding minimal additional overhead for those who don't need it. Since bringing this spec to the WG is an effort to gain wider adoption and investigate broader use cases than what we have at present, taking these kinds of expansions seriously is good. The benefits were positively acknowledge overall, and I was hoping we'd see this added to the current version, even if marked 'at risk' pending future implementations. But the decision was taken to leave it out, in the same vein as AS2 currently relegating all *addition* suggestions to extensions. On the plus side, the webmention spec will link to all proposed extensions which are written up as specs, and if any extensions see enough adoption over the course of the work they can be integrated into the core.\r\n\r\n## Cooperation\r\n\r\nBridging between worlds has been an ongoing theme in this WG.\r\n\r\n[Chris](https://dustycloud.org) has done some great work on [Activipy](http://activipy.readthedocs.org), a Python library for handling AS2, and overnight between meeting days he added support for jf2 as well by simply passing in an alternative JSON-LD context. This means you can pass in AS2 and serialize out again as jf2, and vice versa! More or less, at least... this might even be improved by adding PTD in between for where mappings aren't already obvious.\r\n\r\nIn general, tensions between specs that could be overlapping have changed to editors supporting each other to drive all of the work forward, and, I'm hoping, to optimise where redundancies exist. We all have the same goals, after all. We've still got a long way to go, but we ended on the feeling that we can probably get there.\r\n\r\nAnd we played almost no SocialWG bingo, so it must have been a good meeting.","as:content":"This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG!
\r\nSee also day 1 minutes and day 2 minutes.
\r\nWhat follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome.
\r\nWe 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.
\r\nJSON-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.
\r\nStill 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.
\r\nWe 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.
\r\nLots of discussion about testing frameworks and how to meaningfully test production and consumption of syntax and vocabulary. I refer you to the minutes, as this is beyond my ability to summarise well enough, but it seemed like the people working on this gained some clarity and a plan to move forwards.
\r\nThere's some contention around what it means to accept a spec as an Editor's Draft in the WG. Our general consensus was that it means a spec isn't necessarily going to be rec-track, or even the direction the group is going to take, but it's in-scope and worth some portion of our attention, even if that is just to inform other things. Most specs we've picked up are work that the editors were doing anyway, and this just means the WG should explicitly not ignore them. It's expected that the specs will change significantly going forward, in response to input from the WG.
\r\nAs such, it's okay that some of our now-ED specs currently cover overlapping territory. We hope that WG attention will serve to refine, cut, expand, merge, and otherwise sort this out. We may end up multiple small specs derived from our current set of EDs which cover pieces of the social puzzle, or several specs will demonstrate multiple viable ways of doing the same thing. My preference is for the former, but the latter is better than nothing. (I tentatively extrapolate the latter into either one gets wide adoption and the others quietly fade out, or they all get equal adoption and people build bridges between them, either way not a total loss).
\r\nI finally convinced people to stop calling this "Amy's SocialAPI Document" and renamed everything to Social Web Protocols. This document describes the individual componants we are trying to standardise (based on user stories), covering both the API and Federation. Given the potential for the WG to produce multiple small specs, work on this is to continue to describe and serve as a guide to each building block. This should highlight both points of convergence between separate specs, and gaps that no existing specs are filling adequately.
\r\nIssues filed should be to that end. Point out obvious points of commonality between specs that I haven't noted, or where it would be worth replacing the vague overview with more spec-like details.
\r\nI aim to take this to FPWD next week (which does not imply WG consensus on the contents yet) with the expectation that this is currently an overview document: a guide to the different areas being standardised by the WG. If we end up with a bunch of small (or overlapping) specs, this could end up as a Note, detailing how they relate to each other as a guide to implementors. If we end up with one spec that covers everything, either this becomes it following input from the other drafts, or this has done its job at converging things and is dropped completely. The rationale behind going to FPWD with this document is to better advertise and explain the different angles of work the WG is doing to other WGs and the public, and to seek wider feedback thereon. The issues become a place to discuss features based on functionality, where they are not specific to one of the other individual specs.
\r\nBoth now EDs. Micropub covers a subsection of functionality of ActivityPump, but is uncoupled from any other pieces of functionality, whereas ActivityPump intertwines lots of things. There are distinct similarities - both POST JSON to a specific endpoint to create, update and delete content. The editors are keen to cooperate so there's value in working on them both in sync.
\r\njf2 is a social syntax to complement (not compete with!) AS2, where jf2 is content-centric and AS2 is activity-centric. The editors of both agreed that it would be beneficial to work on these in conjunction. I've written more about the relationship between them here.
\r\nPTD is an algorithm to help consumers who find themselves with implicitly typed objects to derive explicit AS2 types, if that's what they prefer to work with. My concern is that it's biased towards the microformats2 vocabulary and currently useful for a niche - but a very small niche. However, James pointed out that types are actually optional in AS2 in general, so it could be expanded to help go from untyped AS2 objects to typed ones as well.
\r\nMy other concern is that this space is such a moving target, and having a fixed algorithm to derive post types based on properties is going to get dated really fast. A constantly shifting algorithm doesn't fit into W3C workflow, and of course brings its own problems (who has implemented which version as it changes over time). I don't have an answer to this.
\r\nEvan forced us to slow down and really think about what we meant by federation. I don't know if anyone else did, but I had a bit of a lightbulb during this discussion. Bogged down in the particular bits of federation that are within reach to me (basically, notifications), I forgot there are a great many other things one might want to federate, like search, following topics, user discovery, recommendations... The WG is not required to tackle all of these, as a 'federation protocol' is the icing on our charter cake, but we absolutely don't want to de-prioritise federation completely as it's important and actually ties in well with a lot of the work we're already doing. But taking a step back to reassess - and clarify to the outside world - what we're actually doing is important, and there's some effort going into that now.
\r\nWebmention has been an ED for a short while, and there were some issues to work through. Some really interesting points have been raised around technical details, security concerns and functionality enhancements, and lots of different ways to refine this spec are emerging. We talked through open issues, and group resolutions were made for most of them.
\r\nThe one I'm most interested in is addition of the property
parameter for better disambiguation of the assertion being made by a webmention. It surfaces a need of people outside of the current core webmention implementors to send and verify claims more precisely, whilst adding minimal additional overhead for those who don't need it. Since bringing this spec to the WG is an effort to gain wider adoption and investigate broader use cases than what we have at present, taking these kinds of expansions seriously is good. The benefits were positively acknowledge overall, and I was hoping we'd see this added to the current version, even if marked 'at risk' pending future implementations. But the decision was taken to leave it out, in the same vein as AS2 currently relegating all addition suggestions to extensions. On the plus side, the webmention spec will link to all proposed extensions which are written up as specs, and if any extensions see enough adoption over the course of the work they can be integrated into the core.
Bridging between worlds has been an ongoing theme in this WG.
\r\nChris has done some great work on Activipy, a Python library for handling AS2, and overnight between meeting days he added support for jf2 as well by simply passing in an alternative JSON-LD context. This means you can pass in AS2 and serialize out again as jf2, and vice versa! More or less, at least... this might even be improved by adding PTD in between for where mappings aren't already obvious.
\r\nIn general, tensions between specs that could be overlapping have changed to editors supporting each other to drive all of the work forward, and, I'm hoping, to optimise where redundancies exist. We all have the same goals, after all. We've still got a long way to go, but we ended on the feeling that we can probably get there.
\r\nAnd we played almost no SocialWG bingo, so it must have been a good meeting.
","as:name":"Social Web WG 4th face-to-face summary","as:published":{"@type":"http://www.w3.org/2001/XMLSchema#datetime","@value":"2015-12-07T23:59:00+0000"},"as:tag":[{"@id":"https://rhiaro.co.uk/tags/activitypump"},{"@id":"https://rhiaro.co.uk/tags/activitystreams"},{"@id":"https://rhiaro.co.uk/tags/as2"},{"@id":"https://rhiaro.co.uk/tags/federation"},{"@id":"https://rhiaro.co.uk/tags/indieweb"},{"@id":"https://rhiaro.co.uk/tags/jf2"},{"@id":"https://rhiaro.co.uk/tags/meeting"},{"@id":"https://rhiaro.co.uk/tags/mf2"},{"@id":"https://rhiaro.co.uk/tags/microformats"},{"@id":"https://rhiaro.co.uk/tags/micropub"},{"@id":"https://rhiaro.co.uk/tags/phd"},{"@id":"https://rhiaro.co.uk/tags/social+protocols"},{"@id":"https://rhiaro.co.uk/tags/social+web"},{"@id":"https://rhiaro.co.uk/tags/socialapi"},{"@id":"https://rhiaro.co.uk/tags/socialwg"},{"@id":"https://rhiaro.co.uk/tags/standards"},{"@id":"https://rhiaro.co.uk/tags/w3c"},{"@id":"https://rhiaro.co.uk/tags/webmention"}]},{"@id":"https://rhiaro.co.uk/tags/indieweb","@type":"as:Collection","as:totalItems":{"@type":"http://www.w3.org/2001/XMLSchema#nonNegativeInteger","@value":"110"}},{"@id":"https://rhiaro.co.uk/tags/indieweb?before=https://rhiaro.co.uk/2015/12/1450547069&limit=16","@type":"as:CollectionPage","as:items":[{"@id":"https://rhiaro.co.uk/2015/12/1450547069"},{"@id":"https://rhiaro.co.uk/2015/12/socialwg4-summary"},{"@id":"https://rhiaro.co.uk/2015/12/1449205520"},{"@id":"https://rhiaro.co.uk/2015/11/let-records-show"},{"@id":"https://rhiaro.co.uk/2015/11/1447269565"},{"@id":"https://rhiaro.co.uk/2015/11/right-mine-does"},{"@id":"https://rhiaro.co.uk/2015/11/tried-quill"},{"@id":"https://rhiaro.co.uk/2015/11/no-sessions-yet"},{"@id":"https://rhiaro.co.uk/2015/11/1446953889"},{"@id":"https://rhiaro.co.uk/2015/11/site-things-im"},{"@id":"https://rhiaro.co.uk/2015/11/youre-looking"},{"@id":"https://rhiaro.co.uk/2015/11/indiewebcamp-sf"},{"@id":"https://rhiaro.co.uk/2015/11/indiewebcamp-mit"},{"@id":"https://rhiaro.co.uk/2015/10/1446071359"},{"@id":"https://rhiaro.co.uk/2015/10/1445051305"},{"@id":"https://rhiaro.co.uk/2015/10/suddenly-meet"}],"as:name":"indieweb","as:next":{"@id":"https://rhiaro.co.uk/tags/indieweb?before=https://rhiaro.co.uk/2018/08/social-web&limit=16"},"as:partOf":{"@id":"https://rhiaro.co.uk/tags/indieweb"},"as:prev":{"@id":"https://rhiaro.co.uk/tags/indieweb?before=https://rhiaro.co.uk/2015/10/1445017360&limit=16"}}]}