#trackbotaction-29 -- James Snell to Reach out to open social foundation participants to invite them to join the w3c social web wg -- due 2015-01-20 -- OPEN
#cwebber2tantek: another legitimate use of -1 is to say "this doesn't belong in the first version of the social API, it's too edge case to be in the 0 edition social API. Might mean you're not against the use case, but you don't think it's necessary yet, or don't think it's in the same class of needs as the other user stories"
#elf-pavlikq+ re: -1 not in core, please implement as extension first
#cwebber2tantek: i think that captures some of that, w3c does this a lot to capture for or against
#bill-loobyFYI - There is an extension mechanism implied by Story "Integration : Bringing tools together" . . . depending on what you consider an extension
#cwebber2tantek: so +0 or -0 kind of shows I'm kind of for or against, but I'm okay with what happens
#cwebber2... the "can live with it" is an important opinion that should be captured in these polls, so thanks for bringing up these options
#cwebber2... I think it's fine to cite silos as examples of where we've experienced these user stories, but as far as assumptions in our group, we should assume every user in our user story could be on a different system
#cwebber2eprodrom: do we need to call that out separately?
#cwebber2... or can we just leave that advice at that
#bblfish"You should assume that all of these stories are independent of network topologies: the stories should work whether all the actors have accounts on a single server, on different servers, and independently of where the data is located."
#cwebber2elf-pavlik: no note is fine, just wanted to clarify on call
#cwebber2eprodrom: so harry is on the queue, so will ack, but I think it's an interesting question
#cwebber2... let me give a bit of experience from activitystreams 1.0, early versions had different verbs that were based on different products based on companies' products
#cwebber2... eg digg had a "dug" thing, like you "dug" a url, but that didn't mesh with like etc
#cwebber2... so early system was built to convey that if you don't understand a "dig", fall back to "like"
#cwebber2... I'm not sure if this was conscious consensus or general laziness on part of implementers
#cwebber2... if a like was not literally a like, like the full identifying URI for a like, was just ignored.
#tantekq+ to note how in IndieWeb we've distinguished responses (includes all interactions, likes, replies, reposts), vs replies (just comments), likes, reposts individually
#Zakimsees harry, elf-pavlik, tantek on the speaker queue
#KevinMarkslike vs favorite have different mapping - heart versus star too
#Zakimsees harry, elf-pavlik, tantek, bill-looby, dret on the speaker queue
#bill-loobythere also wasn't an explicit hierarchical association to the extent there is with a vocabulary iirc
#cwebber2eprodrom: not sure if you Should or Must process these as "treat a like as a response" or a "fwoop as a like" and it'll actually get implemented
#Zakimsees elf-pavlik, tantek, bill-looby, dret on the speaker queue
#rhiaroQuora and Reddit (I think) have upvote which is similar but not quite the same as like, or maybe how similar depends on who is using it and when/where
#cwebber2... will get off my soapbox and ack harry
#cwebber2harry: basically the question is whether you should have some inference is should the implementations actually do so
#tantekq+ to also point out that the AS1 experience that eprodrom cited (implementers ignoring "special" likes / inference etc.) is a strong data point *against* arbitrary extensibility of such types etc. in practice, regardless of implementer/customer claims/wants
#Zakimsees elf-pavlik, tantek, bill-looby, dret on the speaker queue
#Zakimtantek, you wanted to note how in IndieWeb we've distinguished responses (includes all interactions, likes, replies, reposts), vs replies (just comments), likes, reposts
#Zakim... individually and to also point out that the AS1 experience that eprodrom cited (implementers ignoring "special" likes / inference etc.) is a strong data point *against*
#Zakim... arbitrary extensibility of such types etc. in practice, regardless of implementer/customer claims/wants
#elf-pavlikdret, even better if you can create it since you explain it very well :)
#cwebber2... it's counter-intuitive to the semantic web community which says extensibility is good, but my expereince is that extensibility is the opposite of interop
#cwebber2... it's stuff people publish but don't consume
#cwebber2... we should look at that as evidence to maybe even leave out extensibility in v1
#dretwe could at least tell people to label their snowflakes in interoperable ways. at the very least we should have a well-defined story. we don"t have one right now.
#cwebber2harry: a bit more formally, we have different ways to process, agree it would be great to do, but also understand it's hard from previous implementers
#tantekIn experience, what implementers/customer,-�sk for* and what they *implement* are two very different things
#cwebber2... we should work with working group to put it in the spec put it in as feature, feature at risk, and if not implementing it by last call, remove or change
#cwebber2... there's a tradition in w3c to wait till implement
#cwebber2... we're hoping to enter last call to see about implementation
#cwebber2eprodrom: is there a way we can split the baby on this one
#cwebber2... maybe suggest to publishers "you can do whatever extension you want, but best practice is to use a vocabulary verb because downstream is more likely to see it"
#tantekq+ to add to Harry's encouragement to implement early. when voting on user-stories, if you +1 as an implementer, say whether you *will* implement it, or *already have implemented!*
#Zakimsees elf-pavlik, tantek on the speaker queue
#dretthat's my pet project: the processing model section
#cwebber2... to consumer: you can concentrate on a particular activity type, but look at heirarchy
#Zakimtantek, you wanted to add to Harry's encouragement to implement early. when voting on user-stories, if you +1 as an implementer, say whether you *will* implement it, or *already
#ZakimAs of this point the attendees have been eprodrom, elf-pavlik, +1.617.247.aaaa, dret, [IPcaller], aaronpk, benthatmustbeme, cwebber2, Sandro, rhiaro, hhalpin, tantek, Tsyesika,
#ZakimAs of this point the attendees have been eprodrom, elf-pavlik, +1.617.247.aaaa, dret, [IPcaller], aaronpk, benthatmustbeme, cwebber2, Sandro, rhiaro, hhalpin, tantek, Tsyesika,