#social 2015-12-02
2015-12-02 UTC
# azaroth ... if you don't know anything about micropub and you get a request you could use PTD to decide what to do with the request, per Amy
# eprodrom ack kevinmarks
# azaroth eprodrom: Good principle to follow
# eprodrom ack eprodrom
# azaroth kevinmarks: Sense of separation here. We are using micropub to route things between systems
# azaroth ... one example is ??? that uses instagram and micropub
# azaroth another example is silo.pub that maps from MF to various things
# azaroth ... it wraps blog in an envelope to post to blogger, or finds the image to send to flickr
# azaroth ... mostly individual things we've built
# azaroth ... lots of targeted protocols that are moving together, whereas you have a bigger suite
# azaroth ... partly where the mappings get odd
# eprodrom q?
# azaroth Tantek: different kind of answer. What drove the different protocols. WebMention happened first.
# eprodrom ack tantek
# kevinmarks azaroth: ownyourgram.com you sign into instagram and it posts your photos to your own site
# azaroth ... different user model between federation and users.
# azaroth ... Conceptually defend the distinction. Federation standpoint it's FYI. THe receiver is not required to do anything on any timescale
# azaroth ... other than how you validate it. After that there's suggested things you can do. If it has X content, then it's a comment and you should copy it to your post as a reply
# azaroth ... but the ultimate decision of action is on the receiever. It has its own agency
# azaroth ... all the boundaries for federation are corssed
# azaroth ... for an API scenario, both ends are under the control of the same user
# azaroth ... so the user issues a command to create something, then the server MUST create it
# azaroth ... it's a hard requirement, so very different from auth and user agency perspective, permissions, trust, number of actors etc.
# azaroth ... don't do auth for federation, you just send it
# azaroth ... Maybe wrong with drawing the difference, but lots of differences?
# azaroth sandro: Clear to me
# azaroth tantek: User 1 vs user 2, rather than one user and thing 1 vs thing 2
# azaroth cwebber2: Same technical design could do both
# azaroth ... webmention is cool in that it's very minimal
# azaroth tantek: a different contract
# azaroth cwebber2: You could emulate in activity pump, nice that it doesn't require a lot of work
# azaroth ... if I run my own pump io server, I know that I'm posting to my thing. The same design and serialization.
# azaroth ... little distinction between what is a client and a server
# azaroth ... don't always control the server. Might decide that you're a spammer even if you have an account, so might still filter
# azaroth ... if I set up my own server, better not do that to myself
# azaroth ... same concepts could be accomplished with same tech, more usable in the long run
# azaroth ... even with lack of distinction, it's not as big a division as you might thing
# azaroth think
eprodrom_ joined the channel
# azaroth rhiaro: my micropub endpoint when it receives a post sends a webmention
# azaroth ... webmention and mf completely separate so no requirement but that's how I hooked it up
# azaroth ... with activity pump you must do it
# azaroth cwebber2: The receiving server might reject it
bblfish and bblfish_ joined the channel
# azaroth ... what happens if you do mpub post to a third party? Do you have to "own" the micropub endpoint?
# azaroth tantek: You have to be oauthed up
# azaroth ... but not in webmention
# azaroth ... which is essential for lightweight federation
# kevinmarks try silo.pub with twitter
# azaroth cwebber2: Right not saying it's not useful, but that it would also be useful if mpub also did federation
# azaroth aaronpk: another difference
# azaroth ... mpub as a way to create content, the content is part of the request
# azaroth ... the bearer token is prearranged
# azaroth ... webmention is only by reference, content is not in the request
# azaroth ... don't say here's my photo etc
# kevinmarks q+
# azaroth ... that would be trackback, and garbage because it's unauthenticated
# azaroth ... only way to send content is if it's authenticated
# azaroth cwebber2: or go back and verify it, but then you might as well not send it
# azaroth eprodrom: activity pump does two legged oauth
# azaroth ... so server to server
# azaroth aaronpk: for mpub there's no URL until the request is handled
# azaroth ... if you used the same protocol for webmentions, you're delivering the contents of the post
# azaroth ... but unless you authenticate there's no way to trust it
# azaroth ... and they probably want to verify it anyway
# azaroth ... so just send the url
# azaroth ... so it's just what we have now :)
# azaroth sandro: You might auth once every long period of time?
# azaroth eprodrom: So because of pingback style of webmention, there's something here you might be interested in, it doesn't make sense to use the same interaction
# azaroth ... if it was PuSH service, ala activity pump, it would make sense?
# azaroth aaronpk: Interesting. Pretty sure most PUSH systems dont' send the contents in the broadcast
# azaroth ... that would look more like micropub
# azaroth ... if PuSH has too many limitations, then may it's just micropub and that's where it fits in
# eprodrom q?
# azaroth ... not the same use case as micropub
# azaroth cwebber2: suggesting that it's easy to drop into an existing blog which is hard with activity pump
# azaroth aaronpk: extending to also handle distribution of content for subscribers is different from webmention
# eprodrom ack cwebber
# azaroth cwebber2: spec is well written. Main concern is that it doesn't talk about specific silos
# azaroth aaronpk: Also anchors it in time
# azaroth tantek: +1 :)
# eprodrom q?
# eprodrom ack kevinmarks
# azaroth s/it doesn't/it shouldn't/
# azaroth kevinmarks: presumption for sending stuff out is that it's replication
# azaroth ... might be a way to couple the two together
# eprodrom q?
# eprodrom ack tantek
# azaroth tantek: to argue against myself ... we have had some experiments and one production use of webmention like an api and webm for federation
# azaroth ... sending a copy somewhere is like federation, for federation-hostile people
# azaroth ... with webmention we have bridgy, that built a protocol for publishing on top of it
# azaroth ... it acts like micropub in a way
# azaroth ... if you send a particular mention to one place it'll publish content to another server
# azaroth ... take this specific action that is triggered by a webmention
# azaroth ... brainstorming on server to server, with distinct users
# azaroth ... didnt' scale well. If you're one someone's website and they have a comment box, you want it to post to YOUR site not just their site
# azaroth ... so it should act like a micropub client and then use webmention to get it back
# azaroth ... if you auth in ... no you might not want to give out arbitrary permissions
# azaroth ... so walked down the path a bit and it didn't seem like a good trust design
# azaroth kevinmarks: have web actions via client side voodoo
# azaroth tantek: without auth
# azaroth kevinmarks: looks like it's going to one site, actually to others
# bengo q?
# azaroth tantek: federation of all the little buttons on posts like like, reply, bookmark, etc. a way to have sites take actions to a different site
# azaroth ... users configure their client to handle them
# azaroth ... built a shim with web components
# azaroth ... a protocol handler that makes it work
# azaroth ... your site will take over the functionality of those buttons on the remote site
# azaroth ... UI federation? not sure how we conceptually captured it
# azaroth kevinmarks: The example of it working is woodwind
# azaroth tantek: with micropub?
# azaroth kevinmarks: with all of them
# azaroth tantek: woodwind is a reader that you sign into with your own domain and it tracks what you're reading
# kevinmarks woodwind is reader.kylewm.com
# azaroth ... if your own site supports micropub you can sign in there and it posts to your site
# azaroth ... if you don't, it can fall back to other options
# bengo q+ to ask about separation of request semantics and resource representation
# eprodrom q?
# eprodrom ack bengo
# azaroth bengo: Maybe controversial, but keeping the object representation separate from what to do with the object. Curious why edit this or post this or delete this is in the body, rather than the method?
# azaroth aaronpk: Reason is to allow delegation of functionality, rpc-style.
# azaroth ... where you might have a static website other than GET, but you can delegate to some other endpoint
# azaroth ... but you can't delete that endpoint
# azaroth ... the objects don't live under the micropub endpoint
# azaroth ... thus the RPC style
# azaroth ... Could say that the endpoint could delete based on a query string, but seems contrived for no particular reason
# azaroth eprodrom: to answer that for other things... for activity pump... pump.io does do that. One way to follow someone is to post your id to their following list
# azaroth ... you add yourself to their followers
# azaroth ... or deleting an object directly
# azaroth ... managing some of the life cycle of the social graph works that way.
# azaroth ... Some things are harder to do like that. If I like something, posting to a list of likers might make sense
# azaroth bengo: Unliking a thing seems either deleting a like resource, or posting an unlike, could try different ways until something works
# azaroth ... but could be just one way
# azaroth eprodrom: we would concentrate on the one way of using AS as written
# azaroth ... always been a logging style format we repurpose as a command langage
# azaroth ... how that happened. Interesting to reconsider purely from a REST mechanism without a command language
# azaroth bengo: having it all in the message is useful for websockets based things too not inherently bad, might just hear that's not restful over and over again
# azaroth eprodrom: expectation has been there'd be a stream of activities, natural to think in atompub style of posting an activity to the feed
# eprodrom q?
# eprodrom ack cwebber
# azaroth cwebber2: couple of CRUD activities, but also others like join ... no HTTP verb
# azaroth eprodrom: COuld have a members resource and posting an ID to it
# azaroth cwebber2: I think this group resolved ... should we use all these verbs...everyone was using the AS verbs not HTTP methods
# azaroth ... so do AS first
# eprodrom q?
# azaroth tantek: I recall that as well. Don't want to have the argument again :)
# azaroth eprodrom: wrap up with micropub? anthing to discuss in next 10 minutes?
# azaroth cwebber2: ready to go to ED?
# azaroth ... I think we should propose it?
# kevinmarks +1
# eprodrom +1
# azaroth +0
# bengo +0
# azaroth jasnell, et al: Make it explicit regarding moving to WD in the status section
# eprodrom RESOLVED: Move MicroPub to Editor's Draft status
# azaroth eprodrom: Resolved :)
# azaroth ... have 90 minutes left, one more item on agenda
# azaroth ... everyone in late afternoon doldrums. Dinner at 7.
# azaroth ... hopefully group photo will not take half an hour
# azaroth tantek: 7th floor with bay bridge
# azaroth [temporarily adjourn]
jasnell, azaroth, kevinmarks2, bengo and tantek joined the channel
# azaroth q+ to say it looked very good :D
# azaroth ack azaroth
eprodrom joined the channel
# eprodrom q?
# bengo q+
# eprodrom q+
# eprodrom ack bengo
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=86982&oldid=86981
# eprodrom B-)
bblfish joined the channel
# eprodrom ack eprodrom
# bengo List the things I triggered to create their side effect?
# bengo Or List the things I've done (feed)
# bengo I don't think it can be both
# bengo s/thing/understand how
# bengo I can weigh in as to why command semantics outside of request body is useful (caching intermediaries like varnish can't easily understand semantics)
# kevinmarks q+ to state issues with over-literal REST CRUD
# eprodrom ack tantek
# eprodrom q?
# eprodrom ack kevinmarks
# eprodrom q?
# eprodrom ack bengo
# eprodrom q?
# eprodrom q?
azaroth_ joined the channel
# eprodrom q?
# eprodrom ack cwebber
# eprodrom ack sandro
# bengo define inbox, outbox, feed as linkRelations
# bengo get html, link response header, webfinger support for free
# bengo profile == link rel me?
# azaroth_ q+ to express concern :)
# kevinmarks things have lots of endpoints already
# azaroth_ +1 to linking to a profile, not linking to potentially many endpoints
# kevinmarks linking to many endpoints is common
# bengo q+
# kevinmarks try looking at any wordpress site
# eprodrom q?
# azaroth q-
# eprodrom ack azaroth_
# eprodrom q?
# kevinmarks on a wordpress blog I see pingback, alternate, EditURI and https://api.w.org/ as rels
# eprodrom ack bengo
# eprodrom q?
# eprodrom ack cwebber
# bengo q+
# azaroth +1
# azaroth Section X: Security Concerns. You should do authentication.
# bengo q?
# azaroth q+ to +1 not mandating a particular version of a particular auth system
melvster joined the channel
# azaroth q?
# jasnell FYI: AS2.0 Editor's Drafts updated to reflect today's resolutions and editorial comments discussed at the F2F (http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/, http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-vocabulary/ )
# Arnaud here is what the LDP WG did: http://www.w3.org/TR/2015/REC-ldp-20150226/#security
# bengo let it come up as an issue
# eprodrom q?
# bengo q-
# azaroth q-
# jasnell FYI: implementation for Node.js has been updated as well (npm install activitystrea.ms), as has the working copy of the JSON-LD context document at http://asjsonld.mybluemix.net
# eprodrom q?
# azaroth jasnell++
# eprodrom ack tantek
# eprodrom q?
# azaroth W3C Trail. You have died of Identity. Would you like to play again?
# bengo Activity Pump inboxes apply equal well to my house or plant or Thing as to my personal profile
# eprodrom q?
# bengo activitysteams does not have identity anymore
# bengo jasnell Profile isn't in here? http://www.w3.org/TR/activitystreams-vocabulary/#actor-types
# eprodrom q?
# eprodrom ack cwebber?
# bengo fwiw http://www.w3.org/TR/activitystreams-vocabulary/#dfn-profile thanks jasnell
# eprodrom q?
# eprodrom ack cwebber2
# eprodrom ack cwebber
# eprodrom ack aaronpk
# eprodrom q?
# bengo +1
# azaroth +1
# eprodrom +1
# eprodrom RESOLVED: accept ActivityPump as editor's draft
# azaroth :)
# ben_thatmustbeme cwebber2 no need to flip the table :)
# RRSAgent I have made the request to generate http://www.w3.org/2015/12/01-social-minutes.html trackbot
# ben_thatmustbeme turns on video\
# tantek aside: http://www.w3.org/2013/socialweb/social-wg-charter.html does say: "Other components necessary for building federated/decentralized social Web systems are in scope but will not lead to Recommendation-track work without re-chartering, and should be discussed in the Social Interest Group."
bblfish, shepazu_, tantek, Arnaud, jasnell, kevinmarks, Arnaud1, kevinmarks2, jaywink, shevski, peacekeeper, elf-pavlik and azaroth joined the channel
# azaroth will be there about 10:20 or so today, shifted one on campus meeting and the big one was cancelled by someone else :)
# azaroth but need to step out from 12:00 till 1:00
kevinmarks, kevinmarks2, tilgovi, tantek and jasnell joined the channel
jasnell, kevinmarks and jasnell_ joined the channel
bengo and eprodrom joined the channel
# eprodrom I'm running a few minutes late.
# kevinmarks my train gets in ~10:10 so there a bit before 10.30 but I can talky in if I'm needed
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87028&oldid=86982
# elf-pavlik thanks tantek!
# tantek if anyone has any more proposed techincal agenda items for today, please add them to : https://www.w3.org/wiki/Socialwg/2015-12-01#Proposed_technical_items cc:bengo
# elf-pavlik i just joined
# elf-pavlik but will only listen
# elf-pavlik yes i can hear!
RRSAgent joined the channel
# RRSAgent logging to http://www.w3.org/2015/12/02-social-irc
# bengo present+
# wseltzer present+
evanp joined the channel
e_s_p joined the channel
Arnaud joined the channel
# Loqi Bgoering made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87029&oldid=87028
# Loqi Cwebber2 made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87030&oldid=87029
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87031&oldid=87030
eprodrom_ joined the channel
# eprodrom_ q+
bengo joined the channel
azaroth joined the channel
# aaronpk all the comments on http://www.kevinmarks.com/ are pulled in via that herokuapp
# Loqi Tantekelik made 2 edits to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87033&oldid=87031
# eprodrom q+
# rhiaro Federation and social api things are not too different. I tmight end up not being in terms of micropub depending on what comes out of aaron's brainstorming. If it turns out we can do those things in one fell swoop, it would be kind of nice and nice to not force ourselces to not work on them if is actually most efficient for us to address them together
# eprodrom q?
# eprodrom q+
# rhiaro s/Federation and social api things are not too different. I tmight end up not being in terms of micropub depending on what comes out of aaron's brainstorming. If it turns out we can do those things in one fell swoop, it would be kind of nice and nice to not force ourselces to not work on them if is actually most efficient for us to address them together/cwebber2: Federation and social api things are not too different. I tmight end up not being in terms of
# ben_thatmustbeme finally catching up on all the logs, i had an app that did server to server micropub for syndication to twitter, the negotiation of access keys was the most annoying part really, but once that was done, it worked fine
bengo joined the channel
# wseltzer waves to kevinmarks, tsyesika , though I'm seated beside the video camera
# bengo q+
# Loqi Tantekelik made 2 edits to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87035&oldid=87033
# kevinmarks present+
# kevinmarks I am now
# kevinmarks muted and video off
# kevinmarks as the train is in noisy level crossing mode
bengo joined the channel
# kevinmarks if we want to do a micropub+webmention+webaction demo later, I have all the bits for that set up
# tantek kevinmarks - if you want to do that, could you add to https://www.w3.org/wiki/Socialwg/2015-12-01#Proposed_technical_items ?
# rhiaro cwebber2: I think a couple of things. 1) most of the companies that ar eputting out things like this probably don't want to use an off the shelf mobile app anyway, because they want to control their brand in some way. Although it is true that when media goblin implemented the pump api we were able to use existing clients and it just worked
# kevinmarks hi wseltzer see you in 40 mins or so
# eprodrom q+
# kevinmarks is not sure the talky is worth it in this noise; will fall back to reading scribed
# bengo It would be interesting to resolve finalizing reader/writer Social API stories above federation, which could just be standardizing processing rules for that API
# Loqi Aaronpk made 1 edit to [[Socialwg]] https://www.w3.org/wiki/index.php?diff=87036&oldid=86942
# Loqi Eprodrom made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87037&oldid=87035
# kevinmarks when is break? I added a demo suggestion to the items
# kevinmarks OK, I'll be there by then
# kevinmarks if you want to schedule a few minutes for a webmention micropub demo
# Loqi Kmarks2 made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87038&oldid=87037
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87039&oldid=87038
# bengo q+
# kevinmarks is the verification part going to be normative?
# kevinmarks or suggested
tilgovi joined the channel
# wseltzer s/mediat ype/media type/
# eprodrom q?
# kevinmarks what do we mean by 'each media type' - would we process a QR code?
# ben_thatmustbeme present+
# ben_thatmustbeme totally confused myself on start time
# wseltzer q+
# wseltzer s/ietf discussion/ietf apps-area discussion/
# wseltzer q+
# wseltzer q+
# wseltzer q+ to comment on security review
# bengo q+
# wseltzer s/??/Privacy IG and Security IG/
# wseltzer s/w3c/WG/
kevinmarks joined the channel
# bengo q-
# kevinmarks No-one is on reception, can someone let me in?
# wseltzer imagines the "feed a prohibited URL to get the mention-collector blocked by authorities"
# kevinmarks Never mind
kevinmarks_ joined the channel
# ben_thatmustbeme presumably we don't actually need to send that namespace correct?
# ben_thatmustbeme or rather the context?
# elf-pavlik webmention seems to represent a link, how about using terms from as:Link ?
# kevinmarks_ mine doesn't
azaroth joined the channel
# ben_thatmustbeme are we bothering with queue?
# bengo q+
# ben_thatmustbeme nevermind, aaronpk basically said what i was going to
# bengo q-
snarfed joined the channel
# kevinmarks_ like-of
# kevinmarks_ I implemented this in http://mention-tech.appspot.com
# kevinmarks_ and it was very confusing
# azaroth q?
# ben_thatmustbeme q+ to discuss my concerns with it
# bengo verification is already not required
# bengo It all already says 'you cant trust the ping', you SHOULD verify it
# kevinmarks_ like me - I record it without valdiating it
# azaroth q+ re extensions and #9
# ben_thatmustbeme other issue with one proposed advantage of it is that it allows you to dismiss types you don't support, but thats just as premature as accepting likes without verifying them
# bengo wilkie agree
jasnell joined the channel
# azaroth +1 to tantek
# kevinmarks_ it's currently written up at http://csarven.ca/webmention
# ben_thatmustbeme i wouldn't call that at all spec like. It generally explains it
jasnell_ joined the channel
# ben_thatmustbeme but what do you do with it if its not found? what do you do if it is given, also that page talks about making target optional
# ben_thatmustbeme indeed, link to extensions in the spec +1
# azaroth q?
# bengo q+
# bengo q-
# bengo accounts.qa-ext.livefyre.com/.well-known/openid-configuration
# ben_thatmustbeme i think a registry of "extensions fields" and links to extension in IWC wiki would make a lot of sense
# ben_thatmustbeme needs to switch computers, losing the conf room
# wseltzer ACTION: $login to do bar
melvster joined the channel
# eprodrom I sent Rene an email; let's see if it produces anything.
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87040&oldid=87039
# kevinmarks_ if I webmention people from the logs, what happens?
tessierashpool_, ElijahLynn and kevinmarks_ joined the channel
# ben_thatmustbeme for demos could we turn talky to projector?
# azaroth ben_thatmustbeme: is that better?
# ben_thatmustbeme thank you whoever that was :)
# ben_thatmustbeme yes
# azaroth :)
# ben_thatmustbeme azaroth++
# kevinmarks_ this is very neat
# azaroth but wait ...
# ben_thatmustbeme "But Wait, Theres more"
# ben_thatmustbeme azaroth beat me to it
melvster joined the channel
jaywink joined the channel
# ben_thatmustbeme talky lost focus sooo bad
# ben_thatmustbeme azaroth a little to the left?
# azaroth that left?
# azaroth or the other left? :)
# ben_thatmustbeme thanks for trying, but still blurry as hell
# ben_thatmustbeme was hoping it would help
# ben_thatmustbeme thinkgs its just color of the page
# ben_thatmustbeme i can see now
# ben_thatmustbeme thanks
# azaroth no problem :)
# bengo (or microdata)
# ben_thatmustbeme cwebber2, in the next couple days i will be moving in to a more specific repo for the spec, but for now, https://github.com/dissolve/socialstream/issues
# ben_thatmustbeme or more specifically https://github.com/dissolve/socialstream/blob/master/jf2.jsonld
# ben_thatmustbeme kevinmarks++
# ben_thatmustbeme cwebber2++ for last demo
# eprodrom scribenick: eprodrom
# eprodrom jasnell_: I'm happy to summarize rene's issues
# eprodrom jasnell_: He's opened a number of issues with new terms to add to the vocabulary
# eprodrom jasnell_: based on the discussion on those proposals, Rene asked what is the principle between vocabulary and extensions
# eprodrom jasnell_: Rene wants to have a documentation of those guidelines
# eprodrom jasnell_: Conversation has been between Rene and myself
# eprodrom jasnell_: I have said we should be conservative in expanding the vocabulary
# eprodrom jasnell_: Default position is to reduce, not add new classes
# eprodrom jasnell_: Hopefully when Rene reads the minutes he can correct if necessary
# eprodrom q+
# azaroth q+
# azaroth q-
# azaroth (that :) )
# eprodrom eprodrom: can we document scope for vocabulary?
# bengo q+
# eprodrom tantek: This would be appropriate to discuss in the draft
# eprodrom jasnell_: are we in agreement on that position?
# eprodrom bengo: It sounds like our principle is don't add anything that doesn't meet that bar
# eprodrom bengo: but what is that bar?
# eprodrom jasnell_: I'd like to leave that open
# eprodrom sandro: Do we have a registry for extensions?
# eprodrom sandro: if good extensions come up, we may add them to the next versions
# eprodrom jasnell_: I have a list of items removed from the spec already, which could go to an extension
# eprodrom jasnell_: What is the process for registering extensions
# eprodrom jasnell_: If it is a workgroup-managed thing, can we discuss the process?
# eprodrom q+
# eprodrom sandro: We can keep a list of extensions personally, or by the group
# eprodrom jasnell_: I have a list of other extensions
# eprodrom sandro: Do you own activitystrea.ms domain?
# eprodrom jasnell_: No, Chris Messina has it
# eprodrom jasnell_: but he will let us directly update it
# eprodrom bengo: A reasonable bar is approved user stories linked from the home page of the wiki
# eprodrom bengo: if any of those can't be described using the vocabulary, then that makes sense for an addition
# eprodrom jasnell_: in the list of proposals we have for adding vocabulary, we have 3 that might be worth discussing
# eprodrom jasnell_: Evan suggested a Blog type
# azaroth q+ to respond to sandro to suggest 2+ _promises of_ implementations at this stage
# eprodrom tantek: There's a section in the vocabulary about AS1 properties. Do you have any plans to include a section of changes, including dropped classes or properties?
# eprodrom jasnell_: Currently that table is not in the editor's draft to simplify
# eprodrom jasnell_: Considering creating a separate document to show differences, how to deal with differences
# eprodrom jasnell_: Still debating whether I'll have the time to write it
# eprodrom scribenick: eprodrom
# eprodrom jasnell_: we can have the registry have its own content document
# azaroth +1 to jasnell
# azaroth s/content/context/
# eprodrom jasnell_: if an extension becomes popular enough, the registry context can import it
# eprodrom jasnell_: There could be a curated list
# eprodrom jasnell_: It gives us an ability to promote popular extensions consistently
# eprodrom sandro: if that's true, it should be a curated list by the WG or a CG
# eprodrom sandro: if there are 2 implementations of a particular term, it should be included
# eprodrom sandro: or maybe a larger N
# eprodrom azaroth: If we have promises of implementations, then that makes more sense
# azaroth q-
# eprodrom sandro: if you're not going to write it, then that doesn't give us a lot of security that it's worth doing
# eprodrom tantek: I'd say deployed, not written
# eprodrom bengo: What about stuff that was implemented in AS1?
# eprodrom tantek: implementation documentation for AS1 is poor
# azaroth has inescapable call now, apologies
# eprodrom tantek: implementation links are poor, broken
# eprodrom jasnell_: except for in-reply-to, all other extensions of AS1 are out of AS2
# kevinmarks_ q+ to distinguish publishing and parsing implementations
# eprodrom jasnell_: most implementations of extensions of AS1 are not in AS2
# eprodrom jasnell_: The registry has an implied context, then implementation can use terms from the extensions
# eprodrom sandro: Doesn't that suggest changing the media type?
# eprodrom kevinmarks_: As part of your implementation test, you'd need publishers and parsers
# eprodrom sandro: I'd set the bar at 2 publishers and 2 consumers
# eprodrom jasnell_: That's the bar for adding. For terms already in the vocabulary, we are getting the minimal level of interop for most common cases.
azaroth_ joined the channel
# eprodrom jasnell_: Minimal stuff doesn't get pulled out if we're not going to use them
# eprodrom sandro: it'll get pulled out when we go to PR
# eprodrom jasnell_: Every term in there is optional
# eprodrom jasnell_: Implementers don't have to support them
# eprodrom kevinmarks_: If this is a bar for adding new things, then we should use the bar for deleting old things
# eprodrom jasnell_: we've already pulled things out like that
# eprodrom jasnell_: if we think some terms might be useful, we can reserve them, saying we might use them in the future
azaroth_ joined the channel
# eprodrom q+
tommorris_ joined the channel
# eprodrom ACTION eprodrom compare AS2 vocabulary with pump.io's use of AS1
# eprodrom eprodrom: this document is useful http://dret.github.io/W3C/SocialWG/AS1-in-AS2.html
# eprodrom sandro: This is useful
# eprodrom jasnell_: We could do this in the wiki
# eprodrom tantek: the first time we talked about what it would take to get AS2 to CR, I suggested we mark everything as at-risk
# eprodrom tantek: Now, I think we should take stuff to at-risk that's not in pump.io
bitbear joined the channel
# eprodrom sandro: we need to review this in CR
# kevinmarks_ so would sending PR's to http://dret.github.io/W3C/SocialWG/AS1-in-AS2.html be useful for eg bengo to do for his implementation
# eprodrom kevinmarks_: can we get information from bengo on this? Can we send PRs?
# eprodrom sandro: How do we update this document?
azaroth joined the channel
# eprodrom bengo: We don't use a lot of different verbs
# eprodrom bengo: We do have an ongoing project to exercise more verbs
# eprodrom tantek: There's a proposed agenda item for discussing federation protocol
# eprodrom tantek: 10-minute break
# eprodrom resume at 12:20
bret joined the channel
# kevinmarks_ gives loqi some lunch
# ben_thatmustbeme i still want a dump of the things loqi has karma on
# wseltzer scribenick: wseltzer
# wseltzer eprodrom: processes we've previously followed, esp for Social API
# wseltzer ... review of non-standardized implementations
# wseltzer ... about 20 APIs, a number of formats
# wseltzer ... collected candidate specs and then reviewed
# wseltzer ... we're trying to run in parallel or converge candidate specs for Social API
# wseltzer ... similar for Social Syntax
# wseltzer ... Is this also the process for Federation Protocol?
# wseltzer sandro: strawman proposal: don't distinguish between API and federation
# wseltzer ... over past few months; activitypump, solid are both; rhiaro's doc is both
# wseltzer ... not closing the door, but until we see a different proposal
# wseltzer eprodrom: saying we won't support unfederated social API?
# wseltzer aaronpk: my understanding was that while developing specs, we won't treat them as separata things, but that doesn't mean the result is combined
# wseltzer eprodrom: so one doc?
# wseltzer sandro: we have 3 stacks, keep thinking about them together
# wseltzer ... Social Web Protocols doc -- perhaps reorg so API sections first, federation second
# bengo q+
# bengo q-
# wseltzer tantek: I heard, we've done a whole process for API, re-use that for fderation
# wseltzer cwebber2: most of the work on federation has already been considered, discussed in many conversations
# wseltzer eprodrom: we haven't looked into details of what's required for federation
# wseltzer ... you can't use webmention for subscribing to remote feed
# wseltzer ... so we haven't fully considered federation
# wseltzer ... what does it mean to read a remote feed?
# wseltzer ... thesse are reqts of what a federation protocol do, not nec reflected in usec ases for API
# wseltzer cwebber2: starting to break things into levels
# wseltzer ... I think it's feasible to keep going that way
# kevinmarks_ the webmention bug on known.kevinmarks.com is fixed now
# wseltzer ... rather than saying federation stuff is off the table
# wseltzer ... we're already making progress
# wseltzer tantek: I didn't hear eprodrom say federation is off the table
# wseltzer ... but exisiting rqts not yet reflected
# wseltzer cwebber2: can we say that moving forward with API, editors are encouraged to keep working with federation?
# wseltzer eprodrom: that we mix up the 2 deliverables we're supposed to produce?
# wseltzer ... We don't have rqts for federation protocol; we don't have significant analysis of what's out there
# wseltzer ... I'm not trying to stop federation
# tantek rhiaro can you update the link to "Amy's Social API document" here https://www.w3.org/wiki/Socialwg/2015-12-01#Editors_drafts ?
# wseltzer ... but asking for systematic analysis, not just byproduct of API wokr
# wseltzer ... good protocol that people cna implement
# wseltzer sandro: Like you, I think federation is important; it would be interesting to analyze
# kevinmarks_ stop trying to make federation happen
# wseltzer ... also think each of the 3 stacks has already come up with a solution they think works
dwhly joined the channel
# wseltzer ... we're all talking about federation; could probably do it better, but that sounds like R&D
# wseltzer eprodrom: we did analysis of API, syntaxes
# wseltzer aaronpk: have we used that?
# wseltzer tantek: for API we did
# wseltzer ... AS we chose to move with because so much adoption already
# wseltzer ack tantek
# wseltzer tantek: Existing federation solutions may not be solving all rqts Evan sees as necessary
# eprodrom Review of social syntaxes
# wseltzer ... We did lots of reserach for API
# wseltzer ... user stories, gathering, voting, etc. took lots of time
# wseltzer ... I wouldn't want to repeat all for federation
# eprodrom q+
# wseltzer ... and yet we need method to address Evan's issues
# wseltzer ... hope we could find some middle ground; some user stories illustrating federation
# wseltzer ack wilkie
# wseltzer ack cw
# wseltzer cwebber2: user stories designed to be topologically neutral
# kevinmarks_ sorry
# wseltzer ... Evan, what ground od we need to cover; how to use work already done?
# wseltzer eprodrom: List of requirements for federation:
# wseltzer .... e.g. @@ remote access to replies
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87048&oldid=87040
# Loqi Rhiaro made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87049&oldid=87048
# wseltzer .... comment remotely, remote interaction with local site
# wseltzer ... which are in-scope, which out
# wseltzer cwebber2: I think everything you said is captiured in user stories
# wseltzer eprodrom: but not expressed as protocol requirements
# wseltzer ... could we do minimal amount of work, eg. wiki approved in a telcon?
# wseltzer tantek: one possible way of turning rqts into something more concrete
# wseltzer ... do you think we could come up with user stories to illustrate federation?
# wseltzer ... assuming there are holes, what additional miminal user stories would we need to cover rqts?
# wseltzer ... can you do the diff, and see what's missing from current user stories for federation?
# wseltzer ... add the misssing stories?
# wseltzer cwebber2: I think I mostly understand it, there are propbablyu some holes in the understanding
# wseltzer eprodrom: I'm thinking we take a number of federation protocols to the public/w3c, and say "this is a federation protocol", they'll ask "what does that mean"
# wseltzer ... we want to be able to say "here's what we considered; here's what we left out"
# wseltzer sandro: first reax, use cases cover them all
# wseltzer ... each stack has a topology
# wseltzer ... yet solid and indieweb have basic one-user-one-site
# wseltzer eprodrom: solid is everything mediated through the client
melvster joined the channel
# wseltzer tantek: webmention demos going through proxies
# wseltzer cwebber2: strawman: take evan's concern that not everything has been addressed, and try to address
# wseltzer ... ideally through user stories, or supplemental requirement, by a deadline
# wseltzer ... discuss
# wseltzer ... only if not already exposed by existing user stories
# wseltzer eprodrom: current user stories are topologically neutral.
# wseltzer ... e.g. 2 players in a "following" scenario, harder in a federated situaiton
# wseltzer tantek: I think we're using "topoligcally netural" differently
# kevinmarks_ we have done SWAT0 with both all indieweb players and with a facebook player https://snarfed.org/silo-swat0-on-facebook
# wseltzer cwebber2: we were saying, you should be able to take all these stories and assume users are on differnet servers, so must be federated
# wseltzer eprodrom: that igves different scope of work
# wseltzer tantek: provide lots of rqts for federation
# wseltzer cwebber2: so show that all the user stories, including gap-fillers, are met
# wseltzer tantek: if someone tags and responds, that's SWAT0
# wseltzer ... following a person is approved user story
# wseltzer eprodrom: we need a remote follow
# wseltzer cwebber2: current user story covers, if you say diff servers
# wseltzer cwebber2: could formalize: you ahve to assume users are on different servers
# wseltzer ... and b) give opprotunity to plug the gap
# wseltzer ... [repeat]
# wseltzer ... a) for your spec to qualify as federation...
# kevinmarks_ that one says "company social network"
# wseltzer eprodrom: does that mean we're soliciting new specs?
# wseltzer cwebber2: we're taking existing stacks
# kevinmarks_ which is not topologically neutral
# wseltzer ... unless there's a really good case for new
# wseltzer eprodrom: will we be adding new parts?
# tantek approved user stories: https://www.w3.org/wiki/Socialwg/Social_API/Sorting_user_stories#Entirely_Positive
# wseltzer sandro: Protocols document has indieweb stack, etc
# wseltzer eprodrom: expanding from micropub to indieweb stack
# wseltzer cwebber2: are you happy with loose description of "indieweb stack" ?
# wseltzer tantek: I'd prefer to avoid that characterization
# ben_thatmustbeme micropub was never a federation api, its social API isn't it?
# wseltzer cwebber2: more inclusivity; but not actively searching new approach
# bengo "Federation with Microformats2"
# ben_thatmustbeme okay, yead i read the logs on that
# kevinmarks_ well, there's syndication in micropub
# wseltzer cwebber2: proposal b) if gaps, opportunity to propose things not covered by existing user stories
# wseltzer ... do those proposals get there?
# wseltzer eprodrom: why not take tiem to think it through?
# wseltzer ... having already implemented 2 federation stacks, it's not an easy process, doesn't just fall out of user stories, so worth thinking through
# wseltzer ... don;'t want to force on the group, but think hard about what uiser stories imply about server-server communication
# wseltzer ... and requriements: discovery, identity,
# kevinmarks_ q+
# wseltzer ... if we pursue each of 2.5 stacks is the best way to go forward, let's, but think abou tit
# wseltzer cwebber2: what' smissing?
# wseltzer eprodrom: looking at other federation stacks that have been tried before, user stories, come up with requirements for federation protocol.
# wseltzer ... I think that's weeks, not months.
# bengo q+
# wseltzer needs a new scribe in 4 mins.
# bengo q-
# wseltzer kevinmarks_: one possible approach is SWAT0 on indieweb, wehre we asked what do we need fore ach person in the graph
# wseltzer ... mapping was informative
# wseltzer ... we found a few new pieces we needed to implement
# wseltzer ... how would you expand story into sequence of steps.
# eprodrom q+
# wseltzer tantek: eprodrom has built many of these systems
# wseltzer ... so I'm willing to believe that verything doesn't necessarily fall out of user stoires
# wseltzer ... wilkie has built a lot too
# eprodrom q+
# wseltzer bengo: can you add more of that knowledge to the not-existing stories
# wseltzer tantek: I agree we're missing pieces
# wseltzer thanks rhiaro
# wseltzer tantek: but I don't think we need such thorough research as previously
# wseltzer ... open the door for a few weeks
# wseltzer ... ... additional user stories for federation holes is reasonable; good place to cite prior efforts
# wseltzer ... e.g. in the past, this story was implemented by PQR
# wseltzer ... implementations as background to user story
# wseltzer eprodrom: I thin that makes sense
# wseltzer cwebber2: since I'm making three proposals, I should type them out
# wseltzer scribe appreciates that :)
# wseltzer eprodrom: I suggest that we ack that we're unlikely to solicit other federaation protocol proposals
# wseltzer ... besides activity pump, solid, indieweb cluster
# kevinmarks_ indieweb components?
# wseltzer ... pulling in lots of things there
# kevinmarks_ not so much a stack as a jumble
# wseltzer ... we'll move forward with those, review other feed proposoals, review of user stories with critical eye ot federation
# wseltzer ... we probably won't implement federated search
# ben_thatmustbeme was that wseltzer's phone?
# wseltzer ... idea that federation is "doing whatever social does on the web" is a long reach
# ben_thatmustbeme oh, n/m that was on talky i think
# wseltzer ... so describe what we ned to do
# wseltzer ... I'll take th lead
# wseltzer ... remote subsscribe, remote feedback, access to profilees
# wseltzer ... and "this is what we're not trying to do" e.g. federated search
# wseltzer ... so list, agree on telecon, and them move forward
# wseltzer ... reasonable next step?
# kevinmarks_ as in tantek.com/2015/224/b1
# wseltzer tantek: would you be open to be acuretor?
# wseltzer eprodrom: yes
# wseltzer sandro: I can't think of a user story
# wseltzer ... each feature that's out of bounds needs a paragraph explaining why it's out of bounds
# cwebber2 ack that we are unlikely to solicit other protocols / the bar is very high; as a side effort do review of other federation protocols, consider user stories with critical eye to federation, being critical of inbound new requests for expanding scope of the group (Evan will take lead / be "curator")
# wseltzer cwebber: ^
# wseltzer ... 1. we are unlikely to solicit other protocols / the bar is very high
# wseltzer .... 2. as a side effort do
# wseltzer review of other federation protocols, consider user stories with critical eye to federation, being
# wseltzer critical of inbound new requests for expanding scope of the group (Evan will take lead
Arnaud1 joined the channel
# wseltzer tantek: those sound like guiding principles
# wseltzer sandro: is pubsubhubbub part of the stack?
# wseltzer cwebber2: if indieweb stack does so
shepazu_ and azaroth_ joined the channel
# wseltzer tantek: table that discussion
tantek_ joined the channel
# wseltzer cwebber2: things we agreed at Boston meeting
# bengo This page now exists and has some related work: https://www.w3.org/wiki/Socialwg/Federation/Requirements
# Loqi Bgoering made 3 edits to [[Socialwg/Federation/Requirements]] https://www.w3.org/wiki/index.php?diff=87058&oldid=0
# eprodrom PROPOSED: Continue developing federation aspects of existing candidate specs (ActivityPump, SoLiD, Micropub/IndieWeb building blocks) and in parallel develop requirements from user stories and other federation protocol efforts
# eprodrom PROPOSED: Continue developing federation aspects of existing candidate specs (ActivityPump, SoLiD, Micropub/IndieWeb building blocks) and in parallel Evan will curate requirements from user stories and other federation protocol efforts
# eprodrom PROPOSED: Continue developing federation aspects of existing candidate specs (ActivityPump, SoLiD, Micropub/IndieWeb building blocks) and in parallel Evan will curate requirements from user stories and other federation protocol efforts, with documented reasons for non-requirements
rrika joined the channel
# bengo +1
# kevinmarks_ +1
# eprodrom +1
# rhiaro ACTION: eprodrom to Continue developing federation aspects of existing candidate specs (ActivityPump, SoLiD, Micropub/IndieWeb building blocks) and in parallel Evan will curate requirements from user stories and other federation protocol efforts, with documented reasons for non-requirements
# trackbot Created ACTION-83 - Continue developing federation aspects of existing candidate specs (activitypump, solid, micropub/indieweb building blocks) and in parallel evan will curate requirements from user stories and other federation protocol efforts, with documented reasons for non-requirements [on Evan Prodromou - due 2015-12-09].
eprodrom, jasnell and azaroth joined the channel
# ben_thatmustbeme @here, as I already have wget copies of all old socialWG minutes, would it be useful to put a page together for WG resolutions and what meetings they were in?
# eprodrom ben_thatmustbeme: that would be amazing
azaroth, azaroth_ and melvster joined the channel
# melvster I'd like to clarify one point. Solid is not bound to the one user one site policy. It would be essentially incapable of widespread adoption if it were, because it would be impossible for social nets like facebook, google, twitter, icloud etc. to adopt. If that's a limitation (actual or perceived) it should be looked at. But im not sure it is.
# Loqi Eprodrom made 1 edit to [[Socialwg/Federation/Patterns]] https://www.w3.org/wiki/index.php?diff=87062&oldid=0
# melvster the other part is about Solid being client side technology ... I can see why it gives that impression because most of the demos are client side apps ... but the same JS could actually live anywhere ... e.g. on a server running node, on a different server running node, in a desktop say electron app, or anywhere else ... when you want performance you'll probably use a server, when you want user control you'll probably use the the client ... in short, Solid
# ben_thatmustbeme huh, rhiaro, eprodrom, azaroth, it looks like there would be a lot of manual checking with that, but i'll throw a quick fetch of what i get in to the wiki, and we can work with it from there
# ben_thatmustbeme just literally grepping all minutes for 'resolved:' (case insensative)
jasnell joined the channel
# eprodrom melvster: sure
# ben_thatmustbeme aaronpk: i'll have the link to the document, i don't have link to the specific lines
# eprodrom But there are things like, if I post a note, the server would take care of distributing that note to all of my followers
# eprodrom In SoLiD, that is up to the client
# eprodrom Sorry, rhiaro just corrected me, there is server-to-server communication using WebSockets
# melvster eprodrom: it's good that you raise that, it ties in to my previous point. When a user posts a note, it happens on the server. Now all that is specified (loosely) is that some javascript (or other language) will then act on that posting and then federate out to followers. In the case of systems with few followers you can 'get away' with that JS living on the client. In the case of larger user bases, it's probably going to mean the JS has to live very
bengo joined the channel
# Loqi Eprodrom made 1 edit to [[Socialwg/Federation/Patterns]] https://www.w3.org/wiki/index.php?diff=87063&oldid=87062
# aaronpk you can find some of those here http://indiewebcamp.com/irc-people
# ben_thatmustbeme aaronpk, eprodrom https://www.w3.org/wiki/Socialwg/resolutions
# ben_thatmustbeme don't know where you want to link that
# ben_thatmustbeme needs a lot of cleanup still
# ben_thatmustbeme and i'm sure there are some missing
# eprodrom ben_thatmustbeme: really nice!
# eprodrom ben_thatmustbeme: one thing is that URLs are being handled weirdly
# eprodrom The full <a> is in there
# eprodrom Rather than just the URL
# ben_thatmustbeme eprodrom: yeah, i know thats just a quick dump, there is certainly cleanup to do
# ben_thatmustbeme and i've already found others
# bengo ben_thatmustbeme is there a github repo to which I can make pull requests of https://github.com/w3c-social/Social-Syntax-Brainstorming/wiki/jf2#context ?
# eprodrom ben_thatmustbeme: OK. Let me know when you're tired of re-dumping and I can edit by hand
# eprodrom Oh, am I still the scribe?
# Loqi Benthatmustbeme made 2 edits to [[Socialwg/resolutions]] https://www.w3.org/wiki/index.php?diff=87065&oldid=0
# eprodrom ben_thatmustbeme: OK. Let me know when you're tired of re-dumping and I can edit manually
# eprodrom lower hand
# wseltzer zakim, raise hand
# eprodrom hand
# eprodrom lower hand
# wseltzer zakim, lower hand
# Loqi Zakim: aaronpk left you a message 16 seconds ago: good morning http://socialwg.indiewebcamp.com/irc/social/2015-12-02/line/1449093231431
# Loqi Zakim: tantek left you a message 44 seconds ago: hand http://socialwg.indiewebcamp.com/irc/social/2015-12-02/line/1449093242149
# wseltzer aww, give a bot a hand
# wseltzer zakim, respond also to HAL
# Zakim Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help.
# azaroth zakim, who holds your hand
# azaroth zakim, azaroth holds your hand
# azaroth :(
# wseltzer i/*adjourn for lunch*
# wseltzer i/*adjourn for lunch*/Topic: LUNCH
# bengo forgot we actually have a bit of as2-ish like that
syncbot joined the channel
# syncbot Oh hi cwebber2!
# syncbot I'm a little irc bot for 8sync! Patches welcome / happy hacking!
# syncbot My source: https://notabug.org/cwebber/syncbot
# syncbot 8sync's source: https://notabug.org/cwebber/8sync
# azaroth And then we told them, RESOLVED: ...
# syncbot *engages turing test with trackbot*
# Loqi syncbot: tantek left you a message 3 minutes ago: hello http://socialwg.indiewebcamp.com/irc/social/2015-12-02/line/1449093573562
# syncbot *stupid puppy look*
# syncbot I can't help you... I can't even help myself!
# azaroth thanks rhiaro
# syncbot cwebber2: *rolls*... you get a 2!
# azaroth syncbot: dfate
# syncbot *stupid puppy look*
# azaroth syncbot: df
# syncbot *stupid puppy look*
# syncbot cwebber2: Rolling at 0: [_] [+] [-] [+] -> 1! (average)
snarfed joined the channel
# azaroth :)
# syncbot *eyes treat suspiciously... then furiously devours it!*
# syncbot *stupid puppy look*
# wseltzer [Lunch is over]
# wseltzer Topic: Agenda-bash, post-lunch
# wseltzer Arnaud1: jasnell wanted to talk activity streams, and he needs to leave
# wseltzer ... how much can we discuss without overriding agenda
# wseltzer tantek: I relinquish my time in favor of AS2
# wseltzer ... return with AOB if time
# wseltzer Arnaud1: more to talk about re API and federation protocol?
# ben_thatmustbeme eprodrom, cleaned up more https://www.w3.org/wiki/Socialwg/resolutions
# wseltzer ... f2f meeting schedule
# wseltzer ... github workflow
# wseltzer ... so for the next hour, we can talk AS2
# wseltzer ... Anything else not on the agenda?
# Loqi Benthatmustbeme made 1 edit to [[Socialwg/resolutions]] https://www.w3.org/wiki/index.php?diff=87066&oldid=87065
# wseltzer ... hearing no additions, let's move forward
# wseltzer ... Good progress yesterday closing AS issues, let's continue
# wseltzer Topic: Activity Streams Issues
# wseltzer Arnaud1: James, over to you
# wseltzer i/Agenda-bash/scribenick: wseltzer
# wseltzer jasnell: most pressing issues: adding new things, or bringing back things that were removed
# wseltzer ... about 3 we should discuss individually
# wseltzer ... Propose we start with bulk issues
# wseltzer ... If objection, pull it out of the list for discussion
# jasnell Specific types of Offer? - https://github.com/jasnell/w3c-socialwg-activitystreams/issues/175
# jasnell Account / accounts - https://github.com/jasnell/w3c-socialwg-activitystreams/issues/235
# jasnell Assign activity (bring back) - https://github.com/jasnell/w3c-socialwg-activitystreams/issues/240
# jasnell Confirm Activity (bring back) - https://github.com/jasnell/w3c-socialwg-activitystreams/issues/256
# jasnell CheckOut / CheckIn activities - https://github.com/jasnell/w3c-socialwg-activitystreams/issues/242
# wseltzer jasnell: as posted to irc ^
# wseltzer ... 175, author activity. eprodrom wondered if we need specific kinds of authors
# wseltzer s/author/offer/
# wseltzer s/authors/offers/
# wseltzer jasnell: I think we should drop offer
# wseltzer ... I'm recommending we close all these
# wseltzer jasnell: Account. none of our use cases call for it
# wseltzer ... Assign and Confirm previously removed from vocab for lack of broad interest
# wseltzer ... Checkout, Checkin. source-control use case
# wseltzer ... blob types, proposal was unclear, no justifying use-cases
# wseltzer ... PROPOSED: close the set due to lack of action/justification
# bengo +1
# wseltzer ... all can be done as extension if someone wants
# wseltzer jasnell: to eprodrom, do you ahve specific types of offers?
# wseltzer eprodrom: in the example, URN product-offer
# wseltzer ... examples should use core vocab if it exists, if not, are we covering schema of the verb
# wseltzer jasnell: we're only covering a bit of the idea
# azaroth +1
# wseltzer ... in general offer should be marked at-risk
# wseltzer eprodrom: that sounds ok to me
# wseltzer eprodrom: I'd rather put at-risk than define fully
# eprodrom +1
# wseltzer jasnell: hearing no objectins, mark the above set closed.
# wseltzer RESOLVED: mark the above set closed
# wseltzer RESOLVED: mark the above set closed: 175, 235, 240, 256, 242, and 223
# wseltzer jasnell: Also recommend closing 208 without action
# wseltzer ... proposal to revisit a fundamental design point in RDF
# wseltzer ... since RDF is optional, nothing to do, close
# wseltzer PROPOSED: close 208
# azaroth +1 to closing rather than starting again
# eprodrom +1
# bengo +1
# wseltzer Arnaud: Challenge, when we close issues when the person who raised it is not present in the discussion
# wseltzer ... likely a bit of resentment at not being able to defend
# wseltzer jasnell: this issue has been on github for a while
# wseltzer Arnaud: At least I'd like the justification we agreed on to be recorded
# wseltzer ... can we agree on the reason to close?
# ben_thatmustbeme also, we have a system for that, object at next meeting before approval of minutes
# wseltzer jasnell: as I said, the RDF modeling is optional, non-normative
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87067&oldid=87049
# Loqi Sandro made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87068&oldid=87067
# wseltzer azaroth: it's a total recasting of the spec to say that things that are currently classes should be relationships
# wseltzer jasnell: it goes back and changes fundameental design
# wseltzer sandro: no justification given for reopening this previously settled issue
# wseltzer Arnaud: also, the issue lacks description of the rational for reopening
# wseltzer rhiaro: there's a bunch of dsicussion in github
# wseltzer ... sounds as though it's going back to AS1, which was presumably changed for a reason
# wseltzer Arnaud: there's a link in the issue to a wiki page
# wseltzer ... describing a model he thnks is better without xplaining the benefit
# wseltzer rhiaro: I think he's saying the benefit is types of properties we can reuse for direct relations
# azaroth +1 to bengo
# wseltzer bengo, can you type that in?
# wseltzer missed it, thanks
# bengo wiki page proposes "If we have Follow, we need isFollowing and isFollowedBy relation"
# tantek aside: azaroth n.m. just found it at https://www.w3.org/wiki/TPAC/2015/SessionIdeas#Web_Annotations
# bengo that's state, not atomic activities (like log objects)
# bengo that may or may not still be true or guaranteed to have not been reversed
# azaroth tantek: ... Yep :) was just looking it up
# wseltzer jasnell: while it could be better in some use cases, that's not drawn out, unclear they're core use cases
# bengo state is harder than activity objects
# bengo make scope had
# bengo *hard
# ben_thatmustbeme ahs to go catch a train
# wseltzer Arnaud: can we agree that we're not convinced possible benefits justify reengineering the data model at this point?
# wseltzer RESOLVED: close issue 208
# wseltzer rhiaro: it could be reopened as an alternative
# bengo updating a stateful social graph from activity objects out of scope of this syntax
# wseltzer sandro: it could be a straightforward transform
# wseltzer jasnell: next set of proposals
# wseltzer ... 268 is one I'd like to see happen
# wseltzer ... removing existing content object, flatten hierarchy, simplify vocab
eprodrom joined the channel
# wseltzer ... Content obj in vocab now is non-functional abstract
# wseltzer ... duration could move up a layer, eliimnate layer of abstraction, simplify
# wseltzer ... clarify use of dimensions
# wseltzer ... overall, think it's an improvement.
# wseltzer ... I have a current;y open pull request
# eprodrom q+
# wseltzer PROPOSED: close the issue, dropping content objects
# wseltzer q=eprodrom
# wseltzer queue=eprodrom
# wseltzer eprodrom: to make sure I understand issue, content is intermediate abstract type
# wseltzer ... prperties used by it will be sent to object or used on clasees
# azaroth q+ to clarify properties -not- on the subclasss
# wseltzer ... since we dont' have range specified for CRUD verbs, no reason to maintain
# wseltzer jasnell: right
# wseltzer jasnell: only three properties. Height, width, duration
# wseltzer ... height and width move to link
# wseltzer ... dureation moves to object
# eprodrom +1
# wseltzer ... duration nt on link
# wseltzer s/nt/not/
# azaroth +1
# eprodrom +1
# wseltzer Arnaud: please vote
# bengo 0
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87069&oldid=87068
# wseltzer RESOLVED: close the issue, dropping content objects
# wseltzer jasnell: 157, opened by eprodrom
# wseltzer ... do we need a blog object type to repreesent that common use case
# wseltzer ... I'd like to propose either website or site
# wseltzer ... currently have a "page" type
# wseltzer ... site as same level of generality
# wseltzer eprodrom: motivation was that first example in core was using extension type for blog
# wseltzer ... if it's such a good exmample, maybe it should be in vocab, or change example
# bengo Site is in our domain: https://github.com/gobengo/activity-mocks/blob/master/mocks/livefyre/site-post-collection.json#L3
# wseltzer ... I like change to use ordered collection, rather than blog, in example
# bengo (as1)
# wseltzer ... as that's the only place "blog" is referenced
# wseltzer Arnaud: which do you prefer?
# wseltzer eprodrom: jasnell's pull request replaces "blog" with "prdered collection". that makes sense to me
# wseltzer s/prdered/ordered/
# wseltzer ... I prefer ordered collection.
# wseltzer PROPOSAL: close 157, replacing example with ordered collection
# wseltzer tantek: collection vs ordered collection?
# azaroth +1
# wseltzer jasnell: blogs tend to be ordered by date
# wseltzer s/PROPOSAL/PROPOSED/
# eprodrom +1
# wseltzer ... and it's just informative
# eprodrom +1
# wseltzer Arnaud: everyone agrees?
# wseltzer RESOLVED: close 157
# wseltzer jasnell: 251, language property
# wseltzer ... background. JSON-LD has @language keyword
# wseltzer ... that can be used within context
# wseltzer ... to specify language of document
# wseltzer ... or at value, to set for value
# wseltzer ... according to W3C guidelines, every format should have way to specify language default for each item
# wseltzer ... the only way we can do that is JSON-LD
# wseltzer ... current spec says it's optional, since JSON-LD is optional
# wseltzer ... propsal from Rob is to add language property
# wseltzer ... challeng is that it's not compatible with JSON-LD
# wseltzer tantek: you can't just alias?
# wseltzer jasnell: no
# wseltzer jasnell: @Context processing requires a processing model
# wseltzer sandro: or "use this boilerplate text, put your language here"
# wseltzer tantek: why doesn't it play well?
# wseltzer sandro: JSON-LD has its own way to do language tagging, and this isn't it
# wseltzer azaroth: JSON-LD, all the string values are now lang-type
# wseltzer ... thta doesn't mean you can use it with a web page
tilgovi joined the channel
# wseltzer jasnell: when I have a JSON-LD doc that @context Lang=EN, every string will be expanded to a language-tagged string
# wseltzer ... vs if we @@ the strings don't get tagged
# wseltzer ... to some of the JSON-LD folks, it's recognized as a limitation of JSON-LD
# wseltzer ... possibly to be addressed in new version, but not there yet
# wseltzer ... so we could go with limited profile of JSON-LD, boilerplate text
# wseltzer ... or we go with the language property, that was in the original version of AS2, that doesn't play well with JSON-LD
# wseltzer ... JSON-LD implementers would have to do more work with language property
# wseltzer cwebber2: I understand @language doesnt' cover all the case we want
# wseltzer ... within the scope of things it does do
# wseltzer ... is it possible ot alias @language to Language
# wseltzer jasnell: no.
# wseltzer ... JSON-LD algorithms will ignore Language except in very specific places
# wseltzer cwebber2: same for @vocab, @base
# wseltzer jasnell: yes
# wseltzer ... only ID and type can be aliased
# wseltzer tantek: inclusion of lang in HTML at a document level is at least 1/2 a disaster
# wseltzer ... lang=en is meaningless in the wild because it
# wseltzer ... is in templates
# wseltzer ... if we need to specifry language, we should have a property
# wseltzer ... if that requires extra work for JSON-LD processors, we should specify the extra work
# wseltzer jasnell: the extra work is not necssarily trivial
# azaroth Playground: http://json-ld.org/playground/index.html#startTab=tab-expanded&json-ld=%7B%22%40context%22%3A%7B%22language%22%3A%22%40language%22%2C%22value%22%3A%22%40value%22%2C%22foo%22%3A%22http%3A%2F%2Fexample.org%2Fvalue%22%7D%2C%22foo%22%3A%7B%22language%22%3A%22en%22%2C%22value%22%3A%22other%20stuff%22%7D%7D
# wseltzer ack sandro
# wseltzer sandro: can you do @language in AS per-value?
# wseltzer jasnell: @@
# wseltzer ... extension would ahve to define themselves
# wseltzer sandro: so issue is you read i18n guidelines as saying we need a whole-doc language tag?
# wseltzer ... my sense is it does more damage than help, so we shouldn't do it
# wseltzer jasnell: we could take current lang defaul tout
# wseltzer ... and dont add language property
# azaroth JSON-LD Playground example of aliasing @language and @value: http://tinyurl.com/zrnxo27
# wseltzer ... explicitly don't provide default language in the format
# wseltzer cwebber2: I think that's better
# wseltzer tantek: I didsagree
# wseltzer sandro: proactively go to i18n group with this question
# wseltzer jasnell: there's one doc section with default language context. propose to remove that section
# wseltzer ... and document the reasoning
# wseltzer tantek: anohter way to be proactive, is document, highlighting for specific i18n review
# wseltzer ... at CR time
# wseltzer Arnaud: what's our position in the meantime
# wseltzer jasnell: in the interime
# wseltzer ... remove the current text, close issue 251
# wseltzer PROPOSED: remove the current text, close issue 251
# wseltzer Arnaud: are you happy with that?
# wseltzer azaroth: yes
# wseltzer sandro: and get i18n review
# wseltzer jasnell: this has been messy for a while
# wseltzer ... so I'm happy to see movement
# wseltzer ACTION: Sandro to bring issue to i18n
# azaroth +1
# wseltzer note action-84, the "issue" is default language for whole document
# eprodrom +1
# wseltzer Arnaud: seeing agreement
# wseltzer RESOLVED: remove the current text, close issue 251
# wseltzer scribenick: bengo
# bengo jasnell: one way we could deal with transience is expires
# azaroth q+ to ask about value of property
# bengo jasnell: without necessarily needing processing model specified
# azaroth q-
# bengo jasnell: value would be date and time at whcih it should be considered invalid. has come up a few times
# bengo jasnell: was'nt acted upon because no implementations needed it
# eprodrom q+
# bengo jasnell: one way of dealing with this
# bengo azaroth: are there two implementations of this or promises to impl
# bengo jasnell no
# bengo eprodrom: this seems like a informative, nonpresriptive way
# bengo eprodrom: it's elegant way to handle
# bengo eprodrom: this makes the most sense. dont see better alternative
# bengo cwebber2: transiency came up. in pump.io you have to leave tombstone behind
# bengo cwebber2 that way other things can still reference it
# bengo cwebber2: how can you verify subcomponents of message if they go away
# bengo cwebber2: i had originally thoguht of dealing with this via source signatures, which are complex
# bengo cwebber2: Expires is interesting but in a federated context it could create its own complexities
# bengo cwebber2: if you make something and tell another system, but it's expired by then, the other system doesn't know if true or false
# bengo cwebber2 I'm not sure expires doesn't add more complexity unless thought through more.
# azaroth +1 to extension and experimentation
# bengo cwebber2 use an extension it would be easier to take time to think through
# tantek q+ to note that transient *content* (part of a post) is a use-case seen more than just "whole posts", from IndieWeb research: https://indiewebcamp.com/expiring_content
# bengo cwebber2: Whether expires, signatures, something else. Leave this as an unsolved problem
# bengo sandro: on flip side, can't do as extension
# bengo Arnaud: yes you can
# eprodrom q+
# bengo sandro: snapchat means expires and transiency is important enough to be Core
# bengo cwebber2: It's possible if activitypump processing rules require it
# bengo cwebber2: (even if extension)
# bengo cwebber2: might even be that we can't solve in this timeframe but do have to do in core eventually, but we should take our time
# bengo cwebber2: Each server in federation has a decision to make on expiry
# azaroth q?
# bengo eprodrom: Please don't say signatures again (to cwebber2 )
# bengo eprodrom: another form of transiency is very small or not that important of activities
# bengo eprodrom IMing, turned left, turned right, big data stuff
# bengo eprodrom expires coul dindicate "this isn't crucial"
# bengo cwebber2 ephemeral
# bengo Arnaud: Is anything like this in requirements?
# bengo Arnaud that would necessitate 'expires'
# bengo cwebber2 idk but I've wanted to bring this up since Boston
# bengo Arnaud ok just wanted to clarify
# eprodrom q-
# bengo jasnell: Worth noting this isn't first time
# bengo jasnell: last time we said to pump
# bengo jasnell: long standing discussion but only recently do prominent silos impl
# bengo tantek: even if federation can't validate transient things, may still be useful
# bengo tantek like parts of post could expire even if not full post
# bengo tantek: In favor of dropping it
# wseltzer ack sand
# bengo sandro: It's complicated, i get it. But so is rest of vocab. So what's the harm of putting it in
# bengo q+
# bengo sandro: gives us a first best effort at it if we let 'expires' in
# bengo sandro whats the harm?
# bengo sandro: only harm is if it people interpret as more than it does
# bengo tantek: there is harm with every addition
# bengo sandro it's hard to build a system wihtout this
# bengo cwebber2: There may be a way of doing this without time-based expiration.
# bengo cwebber2: In IMing and Game stuff, you don't need a log of it all anyway. The server can just relay and give a UUID
# bengo cwebber2: Could just have ephemeral flag instead of expiry date
# bengo q-
# bengo 'DNT'
# bengo cwebber2 there wouldn't be a permanent url
# bengo cwebber2 only for same-origin
# bengo jasnell we can do something like that already
# azaroth bengo - for the same person talking, you can put ... instead of their name for second and subsequent lines
# azaroth e.g. azaroth: Says something \n ... and then says something else
# wseltzer ENOMORECOFFEE
# bengo jasnell we have other activities in core like Invite and Offer that have a lifecycle
# bengo ... there are alreayd use cases for this
# azaroth wseltzer GET coffee => 404 :( :(
# bengo jasnell: Offer may be at risk, but this could still be useful for Invite
# bengo jasnell: Not arguing for. Just sayign we can
# bengo jasnell: but if we add, should mark at risk
# bengo jasnell: Then in CR if it's not going to work out, we drop
# bengo Arnaud: that's reasonable way of moving forward. Draws attention from others
# bengo cwebber2: At risk is good
# bengo sandro: I'm now more in favor of not having it
# bengo sandro: we need to solidify extensinos so it doesnt matter if in core
# bengo jasnell: Let's not decide to accept/reject yet. And see if there's a better solution
# bengo (consensus)
# bengo jasnell: we should consider a few more
# bengo jasnell: Is there anything else bad in spec to be forwards compatible? e.g. lists of lists
# bengo sandro: if they upgrade JSON-LD they'll have to be back compat anyway
# bengo jasnell: all open proposals are closed
# bengo jasnell: oops one more abuot lifecycles
# bengo sandro: we should make a community group that maintains a website that maintains all the terms/verbs/words
# bengo sandro: Thing description status of that thing
# bengo Arnaud: how about wiki page?
# bengo jasnell: start as wiki, if difficult, then we can adjust and see if CG is necessary
# bengo sandro: CG needed (even if trivial) because it gets us a wiki
# bengo tantek: siloed wikis are W3 antipattern
# bengo sandro: but they can give out namespaces
# bengo sandro: and that helps with extensions using a w3 namespace
# bengo tantek: What's wrong with custom elements convention of hyphens
# bengo sandro: Because that doesn't help with collissions
# bengo cwebber2: And we want JSON-LD expansion to work
# azaroth q+
# bengo tantek: ostensibly cusom elements have solved this
# wseltzer q+
# bengo sandro: no x-header (??) are the real solution
# azaroth q-
# bengo sandro: x-headers are widely acked as mistake i HTTP
# bengo sandro: And in this case we have an easier solution than that
# bengo sandro: (w3 namespace for extensions)
# bengo wseltzer: prefixes are bad pattern
# bengo tantek: only for some things
# bengo wseltzer: because they require revision later once the old prefix is standardized
# bengo tantek: As a trivial counterexample, border-radius in CSS
# bengo cwebber2: big db of past accrued activities would be really hard to re-name properties
# azaroth +1 to cwebber2
# bengo cwebber2: We should avoid that if possible
# bengo cwebber2: CG is reaosnable solution
# bengo sandro: Hard for even more reasons
# bengo eprodrom: One big apps to is schema at read
# bengo eprodrom: and avoid db migrations
# bengo eprodrom: *what big apps do
# bengo sandro: so whats wrong with CG?
# bengo jasnell: just whether the process overhead is worth it
# bengo sandro: Process overhead vs extension overhead
# bengo Arnaud: Who's signing up to create CG?
# bengo cwebber2: could just have wiki page of extensions with their own ns
# bengo ... not curated by official group but at least the activities are preserving their contents
# bengo jasnell: Other way of not having it be a WG thing is to make a github project managing this
# bengo jasnell: PRs/issues accepted
# bengo jasnell: this doesn't need w3 tamp
# bengo cwebber2: I'm cool with that
# bengo sandro: CG overhead is 10min
# bengo sandro: and github is compatible with that
# bengo jasnell: as long as overhead isn't too much and folks are willing to participate
# bengo sandro: same people as adminning a github repo
# bengo Arnaud: that's always the challenge. open wiki is open toa bbusers. Control requires personhours/effort
# bengo sandro: Should we let them use main namespace
# bengo bengo: no
# bengo jasnell: that could cause problems for implementations that build that into their namespace
# bengo jasnell: something can be in namespace without bieng in jsonld context
# bengo sandro: namespace just means they use it as imaginary prefix
# bengo jasnell: idk...
# bengo sandro: Let's analyze options later
# bengo Arnaud: What should we do?
# bengo eprodrom: Is this last one?
# bengo Arnaud: We said yesterday we would give folks two weeks to bring up issues so we have to wait now anyway
# bengo sandro: A more conventional way to do this would be to ask editor when they would like next review to happen
# bengo sandro: then 1 week or so before next phase
# bengo tantek: publishing moratorium coming soon
# bengo tantek: soon enough that changes just made are of sufficient enough value that we ought to publish WD with jasnell changes by... friday
# bengo sandro: And then aim to go to CR by early Jan
# wseltzer [W3C publications moratorium 21 Dec-1 Jan]
# bengo tantek: yeah issue velocity has dropped but if it picks back up we wont go to CR
# bengo tantek: it's great there is renewed interest and activity
# bengo jasnell: seems reasonable
# bengo jasnell: remaining issues are mostly editorial
# bengo jasnell: I think we're done
# azaroth +1
# bengo +1
# eprodrom +1
# kevinmarks_ +1
# bengo Arnaud: Let's shift gears
# wseltzer RESOLVED: publish a new WD of AS2 drafts as of / by Friday.
# bengo 15m break
# wseltzer rrsagent, draft minutes
# RRSAgent I have made the request to generate http://www.w3.org/2015/12/02-social-minutes.html wseltzer
# kevinmarks_ bye jessica
# wseltzer rrsagent, make logs public
# wseltzer rrsagent, draft minutes
# RRSAgent I have made the request to generate http://www.w3.org/2015/12/02-social-minutes.html wseltzer
# bengo eprodrom: next up, resolve more issues in api and federatio protocl. next F2F schedule
# kevinmarks_ did we lose post type?
# bengo just made https://github.com/gobengo/as2-validate
# eprodrom reconvene at 3:45
# wseltzer i|as I already have wget copies|Topic: LUNCH
# wseltzer rrsagent, draft minutes
# RRSAgent I have made the request to generate http://www.w3.org/2015/12/02-social-minutes.html wseltzer
# snarfed bengo: cool! any idea how you expect it to differ from https://github.com/jasnell/activitystreams.validator , https://github.com/apparentlymart/activity-streams-tester , https://github.com/w3c-social/as2test , etc?
# bengo it depends on the former
# bengo and james told me to keep as separate
# bengo I just wanted a cli
# snarfed ah ok
# bengo so i could
# bengo (curl "https://gist.githubusercontent.com/gobengo/aef6d083290930e25025/raw/02bdf242d4d39000efdb4849db414bad85ec3463/indieweb-social.json" | node index.js ) && echo "perfect"
# bengo ... it is not perfect
# snarfed lol
# bengo sorry, not `node index`, `as2-validate`
# bengo which you can now `npm install -g as2-validate`
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-12-01]] https://www.w3.org/wiki/index.php?diff=87070&oldid=87069
# wseltzer Topic: Open Issues for other drafts than AS2
# eprodrom q?
# wseltzer and there's a W3C Advisory Committee meeting March 20-22
# eprodrom q?
# eprodrom ack tantek