#jasnellThe way Link's were handled, for instance. Those changes were motivated entirely by community feedback and direct implementation experience
#tantekjasnell - in that case, it sounds like this is a big enough revision from last week's draft to give people another week to review this draft before publishing as a first public working draft (FPWD)
#jasnellyes. I'm going to need an additional few days to work on the changes to the other document... the one that talks about the serialization, and to write up a bunch of example cases that illustrate the changes
#tantekwhen do you think you'll have a draft ready for review for consideration for a FPWD?
#jasnellI ought to have both the vocabulary and the serialization draft done by the end of this week
#jasnellalong with a suite of test cases and examples
#tantekwhenever you think it's "ready for review", then we still need another week after that for the group to review it for FPWD publication consideration - does that make sense?
#jasnellthat's why I wanted to get this part out today at least. I was hoping to get both documents updated before tomorrow but simply ran out of time for the second one
#tantekI'm going to take that as you the editor saying you'd prefer to delay a FPWD to be based on this edited version, rather than last week's or even today's version
#tantekto reduce confusion we'll likely just put the same review deadline for both, unless you see an advantage to publishing one before the other
#jasnellputting them both together is fine. Looking at the schedule, it ought to be no problem getting both reviewed and published before tpac so we should be good to go
#jasnellgoal is to (a) finish the document this week, (b) provide examples and test cases by early next week, and (c) update our open source sample implementation available on github by tpac
#tantekare you going to be ok with providing a FPWD candidate by the end of the week then that you don't need to further tweak?
harry, bblfish, melvster, bblfish_, bblfish__, ShaneHudson and nicolagreco joined the channel
#oshepherdHmm. The removal of as:duplicate... On the one hand, it is rarely used; on the other, it would be useful for stuff like POSSE/PESOS (and particularly preventing import-export loops)
nicolagreco, bblfish, ShaneHudson, KevinMarks, melvster, deiu, harry, Shane and cmhobbs joined the channel
#Zakimthe conference code is 7625 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), markus
#oshepherdArnaud: Asking scribe to transcribe, post to mailing list once done so that people can discuss the cleaned up minutes, so that they have a heads up to chime in on last week's minutes
#oshepherdArnaud: Process is that as people review documents, raise a list of issues they have, and we can start working on those issues and moving forward
#jasnelltantek: yes. the AS2 vocabs is what I posted yesterday. I'm working on updating the AS2 syntax today and tomorrow
#oshepherdArnaud: Perfectly reasonable to publish an FPWD with open issues; nobody expects FPWD to have all issues closed
#oshepherdjasnell: As a bit of background, actions original proposal that was contributed overlapped fairly significantly with schema.org actions
#oshepherdjasnell: but took different approaches with regards to syntax and properties
#oshepherdjasnell: in update published yesterday, have revised model so that it is /closer/ to what schema.org has done, follows same basic model, but property names etc are slightly different, no direct dependency
#oshepherdjasnell: aligned so that community has /one/ way of doing things, but don't overlap
#oshepherdArnaud: Don't think we have discussed the merging of these two together in the past. It is important to indicate that we are abandoning separate document
#oshepherdjasnell: The actions portion is still separate section in the main vocab draft, so can be separateed out if necessary
#oshepherdtantek: So harry asked if anyone in Indieweb community had had a chance to review the AS2 draft
#oshepherdtantek: Don't speak for commuinity, just for myself; have looked over some of draft, haven't done a total reading
#oshepherdtantek: Don't see how to map some of Indieweb microformats usage into AS2 JSON...
#oshepherdtantek: ...but that might just be me not quite understanding it yet, not going to raise as a blocker
#ShaneI've read it but having not implemented AS, I don't have strong opinions either way
#oshepherdtantek: As I see it, the AS2 work should continue to go forward, should try to figure out some form of mapping
#oshepherdtantek: If we can't figure out some form of direct mapping, maybe worth bringing forth some form of proposal, not worth crossing bridge until we get to it
#jasnellI'm happy to work with you on exploring that mapping
#oshepherdtantek: Regarding the actions: thats all new, as far as I understand, not based upon anye xisting implementations
#oshepherdtantek: Based upon that I think we should keep it separate
#oshepherdtantek: Don't want tthat to cause any issues for existing AS2 syntax+vocab documents
#oshepherdtantek: Would prefer to go to FPWD with both vocab+syntax without actions
#jasnellDo we have a list of requirements for the Social API that we can use to evaluate candidates?
#oshepherdevanpro: As we go into discussing social API with our contributions of the AS portion of OpenSocial, would like to see some others so we can evaluate multiple candidates
#tantekjasnell - # of implementations would be a good start
#oshepherdArnaud: So people to go to wiki page and add candidates?
#oshepherdArnaud: See several people have agreed with people on IRC. Seems to be premature, not sure what the purpose of an implementers group would be
#jasnellI'd like to see a review from *everyone* ;-)
#oshepherdtantek: So I wanted to raise one of the points that we have made in this WG
#oshepherdtantek: (Pretty sure it is in the charter) that we should try to come up with minimal vocab
#oshepherdtantek: So in particular when reviewing the AS2 draft pay special attention to and provide feedback on what of the vocabulary you find useful
#oshepherdtantek: and what of the vocab, espeically if you have implemented AS1 or AS2 or similar functionality, what terms and values you have shipped, what you haven't
#oshepherdtantek: That information is useful to WG, if we see clear pattetns that implementers only care about 80% of terms, we can use that to make the vocab smaller
#oshepherdtantek: Smaller standard benefits everyone
#oshepherdtantek: so we can aim for minimal set based upon real world experience
#jasnellwilkie: either to the mailing list, wiki or the github issues
#oshepherdArnaud: Would like to remind people that as a part of the W3C spec track, there will be a point at which we have a call for implementations, at which point we need 2 implementations of _every_ feature to move forward
#oshepherdArnaud: We have a concept of a "feature at risk"; if we have a feature we aren't sure of, we can mark a feature like this indicating that we aren't sure if we are going to move forward with feature
#ZakimAs of this point the attendees have been bret, jasnell, Sandro, Arnaud, Lloyd_Fassett, elf-pavlik, jtauber, hhalpin, Tantek, bblfish, +1.703.670.aaaa, evanpro, Shane, MarkC,
#oshepherdArnaud: With everything said, looks like we can close this call a little early. Thank you all; see you again next week; meeting adjourned
#jasnell-github[w3c-socialwg-activitystreams] jasnell pushed 1 new commit to ontology-approach: http://git.io/46scow
#jasnell-githubw3c-socialwg-activitystreams/ontology-approach 4a51ce3 James M Snell: split actions vocabulary back out per WG preference to keep Actions...
jasnell-github joined the channel
#jasnell-github[w3c-socialwg-activitystreams] jasnell pushed 1 new commit to ontology-approach: http://git.io/QLssSg
#jasnell-githubw3c-socialwg-activitystreams/ontology-approach a15f1f1 James M Snell: cleanup... move some of the extra notes out of the repo. Will address...
caseorganic, nicolagreco, grantmacken, tantek, ShaneHudson, cmhobbs, harry, bblfish and jasnell-github joined the channel
#jasnell-github[w3c-socialwg-activitystreams] jasnell pushed 1 new commit to ontology-approach: http://git.io/-O10Lw
#jasnell-githubw3c-socialwg-activitystreams/ontology-approach d89b748 James M Snell: - Updated core AS draft reflecting vocal changes and json-ld basis....
jasnell-github joined the channel
#jasnell-github[w3c-socialwg-activitystreams] jasnell pushed 1 new commit to gh-pages: http://git.io/hhm3jg
#jasnell-githubw3c-socialwg-activitystreams/gh-pages 2b74c41 James M Snell: Updating the github site page...