#social 2015-06-30
2015-06-30 UTC
bblfish and jasnell joined the channel
# Loqi Riannell made 1 edit to [[Socialwg/invited-experts]] https://www.w3.org/wiki/index.php?diff=84897&oldid=84818
jasnell, bblfish, tilgovi, jaywink, melvster and shepazu joined the channel
# melvster rhiaro: you may be interested in this post https://lists.w3.org/Archives/Public/semantic-web/2015Jun/0125.html
csarven joined the channel
# elf-pavlik hey! does your conversation relate to https://github.com/jasnell/w3c-socialwg-activitystreams/issues/134 ?
tantek joined the channel
# elf-pavlik previous conversations around that also in: https://github.com/jasnell/w3c-socialwg-activitystreams/issues/36
# elf-pavlik also check out http://tinyurl.com/nas73bc
# elf-pavlik if term e.g. *foo* doesn't have mapping in JSON-LD context, AS 2.0 will use assign it _:foo as identifier
eprodrom joined the channel
# elf-pavlik i explained issue with some "wrong interpretation" in this comment https://github.com/jasnell/w3c-socialwg-activitystreams/issues/134#issuecomment-108255400
# elf-pavlik csarven, hey! glad to see you joining this WG :)
# elf-pavlik melvster, IMO normative JSON-LD context for AS2.0 doesn't get enough visibility and as much review as core spec and vocab spec
tilgovi joined the channel
bblfish joined the channel
# elf-pavlik melvster, have you read my comment with ACME and Baz Inc?
# elf-pavlik melvster, i propose that if someone wants to use custom terms, person should just create namespace for them. even if it will just give HTP 404 to get started
# elf-pavlik this way you don't end up with merging two AS2.0 documents and having same identifier (blank node identifier _:foo) for two different terms
# elf-pavlik issue 134 caputes it with and example merging documents published by ACME and Baz Inc.
# elf-pavlik i think we may need a NOTE in the end, which explains how to use AS2.0 as RDF
# elf-pavlik for example *p3k-drink* ('pseudonamespaced' term extending microformats) doesn't have URL http://pin13.net/mf2/?url=https%3A%2F%2Faaronparecki.com%2Fmetrics%2F2015%2F06%2F29%2F205422%2F
# elf-pavlik aaronpk, post yes but not vocab term: p3k-drink
shepazu joined the channel
# elf-pavlik at least properties have *globaly unique* names, even if misused
# ben_thatmustbeme tries to follow conversation this late in
# ben_thatmustbeme difference is mis-use of standardized properties vs mis-use of extension properties (if i follow that correctly).
# elf-pavlik blank node
# elf-pavlik "The blank node identifier is scoped to the document in which it is used." IMO it can come tricky when merging two AS2.0 documents which happen to use same custom property which gets mapped to same _:foo while having intended different meaning
# elf-pavlik does anyone know what time earliest i can dial in to check Webex connection?
# ben_thatmustbeme no clue
# elf-pavlik i will use friend's iPad with Webex software
# elf-pavlik hmmm...
# elf-pavlik i'll try to call now to see what happens
# elf-pavlik i get 'meeting not started yet'
# elf-pavlik aaronpk, ben_thatmustbeme do you have any examples of *access controll* on HTML pages (aka read API) in IndieWeb community?
# elf-pavlik i stay again with fkooman in Berlin and we'll play with it more in next days :)
# aaronpk elf-pavlik: http://indiewebcamp.com/private_posts
# elf-pavlik aaronpk, as far as i remember nothing that would work with a 'reader' ?
# elf-pavlik "The serialized JSON form of an Activity Streams 2.0 document must be consistent with what would be produced by the standard JSON-LD 1.0 Processing Algorithms and API [JSON-LD-API] Compaction Algorithm using, at least, the normative JSON-LD @context definition provided here. Implementations may augment the provided @context with additional @context definitions but must not override or change the normative context. "
# elf-pavlik yeah, i remember very well this article http://manu.sporny.org/2013/rdf-identifiers/
# elf-pavlik melvster, In Your Opinion :)
# elf-pavlik sandro++
# elf-pavlik needs to read it!
# wseltzer csarven, the important thing is to present+ in IRC
# csarven Well, I'm having a 'java issue' when I try to join at https://mit.webex.com/mit/j.php?MTID=m60d8f99fc911f2b6fdbb0650665f22b4
# wseltzer csarven, you can just dial in by phone without the webex client
Arnaud joined the channel
# elf-pavlik i just connected, could someone please already join so i can test voice?
# wseltzer datespace, aargh
# elf-pavlik did anyone join webex call aready ?
# elf-pavlik 642 112 960 ?
# elf-pavlik hey cwebber2 :)
# elf-pavlik who joined as Call-in-User_2 ?
# elf-pavlik csarven, i guess you than :)
# elf-pavlik present+ elf-pavlik
# ben_thatmustbeme ben_thatmustbeme+
# ben_thatmustbeme or wait, was it
# ben_thatmustbeme +ben_thatmustbeme
# eprodrom present+ eprodrom
# wseltzer rrsagent, pointer?
RRSAgent joined the channel
# RRSAgent logging to http://www.w3.org/2015/06/30-social-irc
Zakim joined the channel
# eprodrom ?
# ben_thatmustbeme hears the bells
# eprodrom They're kind of charming
# wseltzer present+ csarven, elf-pavlik, ben_thatmustbeme, eprodrom, tantek
# wseltzer thinks she got the people who came in earlier
# bigbluehat present+ bigbluehat
# wseltzer present+ wseltzer
# wseltzer alas, poor zakim
# elf-pavlik Benjamin Young - i don't recognize your IRC handle...
# ben_thatmustbeme what is left that we use from Zakim?
# ben_thatmustbeme elf-pavlik Benjamin Young is bigbluehat
# elf-pavlik thanks ben_thatmustbeme
# elf-pavlik i can scribe
# ben_thatmustbeme scribeNick: elf-pavlik
# elf-pavlik topic: Approval of Minutes of 16 June 2015
# bigbluehat tnx ben_thatmustbeme
# eprodrom +1
# elf-pavlik s/16 June 2015/23 June 2015/
# elf-pavlik we decided to use new W3C license for all the work from this group
# elf-pavlik tantek: sandro have accepted this action item and will take it through W3C process
# elf-pavlik ... sandro do you have any rough estimates how long it will take?
# elf-pavlik sandro: it should take 2-3 to take it to AC
# elf-pavlik ... feel free to remind me next week
# elf-pavlik tantek: any questions on this point?
# elf-pavlik tantek: we have two drafts prepared for publication
# elf-pavlik ... thank you jasnell for preparing them! also ben_thatmustbeme thanks for PR with microformats examples
# ben_thatmustbeme i have more MF2 updates to do
# elf-pavlik jasnell: eprodrom posted number of PRs with grammar and spelling corrections which will get included
# ben_thatmustbeme but won't be ready for a little while
# KevinMarks present+
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-06-30]] https://www.w3.org/wiki/index.php?diff=84899&oldid=84870
# ben_thatmustbeme present+
# elf-pavlik tantek: you have purely editorial updates which you have included and which people might not read since they arrived this morning
# elf-pavlik jasnell: correct
# eprodrom q+
# elf-pavlik jasnell: ben_thatmustbeme do you have batch of updates to examples ready?
# elf-pavlik ben_thatmustbeme: not for today
# elf-pavlik tantek: what precent have you gotten through ben_thatmustbeme?
# elf-pavlik ben_thatmustbeme: i belive over half, most from core spec but vocab spec has a lot of examples as well
# elf-pavlik eprodrom, i've done a number of editorial PRs and have more through out rest of the day, i'll leave it to jasnell to decide which he wants to include before publishing new working drafts
# elf-pavlik ... i don't think anything that should hold publishing new WDs
# elf-pavlik +1
# eprodrom +1
# elf-pavlik jasnell++
# eprodrom q+
# elf-pavlik Arnaud: i have question with regard to next step, jasnell do you have a sense what it will take to go from current drafts to Candidate Recomendation (CR)
# elf-pavlik jasnell: we need aditinal review on extended vocabulary e.g. possibly adding *Organization* back as Actor type also an *insturment* proeprty
# elf-pavlik ... examples review as ben_thatmustbeme is doing
# elf-pavlik ... editorial review as eprodrom is doing
# elf-pavlik Arnaud: it answers my question
# elf-pavlik eprodrom: i see it very likely that Social API which we will come up with will use in some ways AS2.0, i'm not sure if we should go to CR unless we have better idea how Social API will look like
# elf-pavlik ... we may see some aditional needs as we get further with specs of Social API
# eprodrom Agree
# elf-pavlik jasnell: the impact Social API may have the most would be the vocabulary
# elf-pavlik ... we could push core to CR and hold on with vocab for little longer
# elf-pavlik ... i would rather not wait for to long
# elf-pavlik Arnaud: from process point of view, we have 3 requirement - 1. resoved all the issue 2. test suite 3. broad review
# elf-pavlik ... we should aim at closing all the issues, working on test suite and get broad review while we work on Social API
# elf-pavlik tantek: Arnaud is correct about the CR requirements from process perspective
# elf-pavlik ... eprodrom can you open issue on AS2.0 which would address need to making it 'make sense' from Social API point of view
# elf-pavlik Arnaud: i worry that we define this issue very vague, how can we tell: we're done with it - resolved
# elf-pavlik tantek: how about defining exit conditions for that issue
# elf-pavlik eprodrom: even having FWPD could work as exit condition
# elf-pavlik sandro: "what changes does the spec need to support the API"
# elf-pavlik ... regarding broad review, do we need it in terms of Social API ?
# elf-pavlik sandro, I didn't pay attention to AS2.0 since I didn't see it useful for any use cases we work with
# elf-pavlik sandro: but after meeting in Paris I realized that AS2.0 can come useful as integral part of Social API
# elf-pavlik ... and we shouldn't go to CR without answering this answer
# elf-pavlik tantek: as a chair I would like to propose to publish a montly heartbeat for AS2.0 documents
# elf-pavlik ... hopefully it will help somehow with getting more broad review (required for exiting CR)
# elf-pavlik sandro: why monthly? what motivates such interval?
# elf-pavlik tantek: with number of significant edits happening in last months, I see it useful to publish new drafts once a month
# elf-pavlik jasnell: usually we haven't made major changes every month, if some requements come from Social API, most likely they will relate to vocabulary no so much to core
# elf-pavlik ... i don't see why montly cycle would be benefitial for us
# elf-pavlik ... definitely something shorter than 5-6 months but 1 month not really needed
# eprodrom q+
# tantek in particular, review of http://w3c.github.io/web-annotation/protocol/wd/
# elf-pavlik eprodrom: last week we've heard about work from Web Annotations WG, including publishing FPWD
# elf-pavlik ... draft bases on LDP and uses some of its constraints
# elf-pavlik ... earlier we looked at aligning our work on Social API with Annotations WG
# KevinMarks reading it now
# elf-pavlik ... i have taken a look at this working draft, have anone else did?
# elf-pavlik eprodrom: ... explaining his understanding of Web Annotaions ...
# elf-pavlik ... a lot of this workflow fits with what we talked about in context of social interactions
# elf-pavlik ... annotations draft doesn't specify workflow for updating annotations etc.
# elf-pavlik ... same for following, reporting annotations back to original publisher etc.
# elf-pavlik ... if seems like very low level protocol which doesn't deal with high level stuff, feels in some ways similar to SoLiD proposal
# elf-pavlik tantek: chairs note - mentioned draft says W3C Editor's Draft 18 June 2014 http://w3c.github.io/web-annotation/protocol/wd/
# elf-pavlik ... not public Working Draft but only Editor's draft!
# bigbluehat it's about to be published. It's been approved by the WG last Wednesday
# wseltzer whispers that she has seen a publication request
# elf-pavlik eprodrom: date is a typo, Doug pointed it out last time
# elf-pavlik ... my question 1. does group wants to track this document?
# elf-pavlik tantek: as chair i want to point out, there seams to be a lot of overlap in scope between this group and Web Annotations WG
# eprodrom Great diagram on http://www.w3.org/annotation/
# elf-pavlik ... many annotations resemple interactions in activity streams model, replies comments etc.
# bigbluehat "CfC: publish FPWD of Web Annotation Protocol; concluded with support" - https://lists.w3.org/Archives/Public/public-annotation/2015Jun/0293.html
# KevinMarks it makes more sense with http://www.w3.org/TR/annotation-model/ as well
# elf-pavlik jasnell: after call last week with Doug we had good conversation about this overlap
# elf-pavlik ... we came up with a plan to make a note on describing this overlap and what we could work on together
# bigbluehat eprodrom doug's chart is fabulous...but it's also non-normative. notification and stuff hasn't been addressed as yet--which is why it's not noted in the protocol.
# KevinMarks the WAA diagram is good, not sue hwo it relates to that container spec as that is about a silo
# ben_thatmustbeme should we wait until they reach FPWD?
# KevinMarks the API does not show how to notify of an external annotation
# elf-pavlik +1
# eprodrom -1
# KevinMarks q+
# ben_thatmustbeme has figured out all by 3 of the callers in webex :P
# eprodrom q+
# elf-pavlik sorry missed you cwebber2 can you please minute it?
# elf-pavlik tantek: can you elaborate your -1
# eprodrom http://www.w3.org/TR/annotation-model/
# elf-pavlik eprodrom: i feel like AS2.0 and Web Annotation model are more equivalent and better to dicsuss them rather than possibly paralell Social API and Web Annotations protocol
# elf-pavlik thanks cwebber2!
# elf-pavlik jasnell: in the note we will focus on relation between data model and fundamental use cases
# elf-pavlik s/elf-pavlik: no prob//
# elf-pavlik s/oops//
# elf-pavlik :)
# KevinMarks franjkly, http://www.w3.org/annotation/diagrams/annotation-architecture.svg is much better than either the data model or API doc
# eprodrom +1
# ben_thatmustbeme cwebber2 it doesn't mess up minutes for this WG, others might have an issue though apparently,
# elf-pavlik sorry folks, i get bit lost here :(
# ben_thatmustbeme cwebber2 me too, i just ignore it
# elf-pavlik jasnell: focus on compatibility of AS2.0 model and Web Annotations model
# ben_thatmustbeme cwebber2 its default behaviour in pretty much EVERY IRC client, so its rediculous to harp on it when it makes no difference to this group
# elf-pavlik tantek: do you want to clarify the proposal? i think we need clarification from you for the end scope
# ben_thatmustbeme elf-pavlik, remember as scribe you can stop conversation if you need to
# elf-pavlik jasnell: note will focus on relation of AS2.0 and work of Web Annotations WG
# elf-pavlik i lost audio!!!!
# elf-pavlik can someone elese scribe for a while
# eprodrom I can do it
# eprodrom scribenick: eprodrom
# ben_thatmustbeme was just about to jump in
# eprodrom scribe: eprodrom
# eprodrom +1
# ben_thatmustbeme before that, why don't you clear the q
# eprodrom KevinMarks: It's doesn't seem to conform to the architecture that we all liked
# eprodrom KevinMarks: Only shows ways to post annotations onto a particular site, while the architecture shows doing it across multiple sites
# eprodrom KevinMarks: All the examples are on the same domain
# eprodrom KevinMarks: Which for us, we're looking at interactions across multiple sites
# eprodrom KevinMarks: So, that's an important issue to discuss with Annotations WG
# eprodrom tantek: Is that a blocking issue for this note?
# eprodrom KevinMarks: It's something worth review. It's fairly key to our model of how we think about this.
# eprodrom tantek: In our microformats examples we try to use different domains.
# eprodrom tantek: this sounds like something we need to discuss in this note.
# eprodrom KevinMarks: Will write a note to put up and point to.
# KevinMarks +1
# eprodrom +1
# elf-pavlik iPad i used for webex client overheated :( i can't join audio any more... eprodrom please continue scribing if you can and i will add minutes to the wiki
# eprodrom elf-pavlik, will do
# elf-pavlik eprodrom++
# tantek no raised: http://www.w3.org/Social/track/issues/raised
# eprodrom tantek: In our chairs discussion, we decided to move handling of issues and actions to the end of the meeting.
# tantek no pending either: http://www.w3.org/Social/track/issues/pendingreview
# eprodrom tantek: No raised issues
# eprodrom tantek: no pending issues.
# eprodrom tantek: There are no pending action items.
# tantek no pending actions either: http://www.w3.org/Social/track/actions/pendingreview
# eprodrom tantek: any reports on actions and issues that the group should know about?
# eprodrom jasnell: Looking at Github issue tracker, there are 9 open issues
# trackbot Error finding 'everyone'. You can review and register nicknames at <http://www.w3.org/Social/track/users>.
# eprodrom tantek: any outstanding business?
# eprodrom q+
# eprodrom unmuting 1s
# ben_thatmustbeme rhiaro is not on the call
# eprodrom eprodrom: Upcoming milestones in Social API brainstorming?
# elf-pavlik sandro, i mentioned you originally in issue 134, i thought you may have some feedback on "@vocab": "_:" hackhttps://github.com/jasnell/w3c-socialwg-activitystreams/issues/134
# eprodrom aaronpk: Can't speak for Amy and Tsyesika, have had other priorities in last couple of weeks, will have time in next couple of weeks
# ben_thatmustbeme rhiaro there was a question of updates on brainstorming doc
# eprodrom aaronpk++
# eprodrom tantek: Indiewebcamp 2015 event happening July 12 in Brighton, Portland, and possibly NYC
# eprodrom tantek: Open to anyone who has or wants to have their own site
# eprodrom tantek: Signup links are on shared URL
# eprodrom Cool!
# eprodrom tantek: Ending the call
# eprodrom elf-pavlik, will you edit the minutes?
# elf-pavlik eprodrom, yes!
# elf-pavlik eprodrom++
# RRSAgent I have made the request to generate http://www.w3.org/2015/06/30-social-minutes.html trackbot
# eprodrom jasnell: dang it
# eprodrom I just accidentally committed another spelling change to the vocab document directly
# eprodrom If you don't mind I'm not going to go back and revert and do a PR
# eprodrom I think I'm just going to stop using the in-page editor
# eprodrom The default is "commit directly"
# elf-pavlik eprodrom, IMO we also get quite some emails noise to the list with so many small PRs
# elf-pavlik today's minutes available on: https://www.w3.org/wiki/Socialwg/2015-06-30-minutes
# Loqi Pelf made 1 edit to [[Socialwg/2015-06-30-minutes]] https://www.w3.org/wiki/index.php?diff=84900&oldid=0
# ben_thatmustbeme eprodrom: yeah, the in-page editor means an immediate PR which means a message to the mailing list of every change, but makes for pretty colors https://github.com/jasnell/w3c-socialwg-activitystreams/network
# eprodrom I try to make atomic changes to leave it up to the editor to accept
# eprodrom Sorry about the mail though
# elf-pavlik eprodrom, you can make one PR with multiple commits which still allow cherry-picking
# eprodrom elf-pavlik: Thanks, but I'm going to stick to the way I'm doing it right now
# elf-pavlik eprodrom, as you wish
# ben_thatmustbeme or they can always just pull the PR into a branch and modify edits there
# elf-pavlik jasnell, do you have any preference?
# elf-pavlik aaronpk, do you have link to example of "p3k has support for private posts by specifying a list of the domains of people authorized to view a private post. " ?
# elf-pavlik kylewm, same for you :) "Red Wind has rudimentary support for private posts based on a simple list of the domains of people authorized to view a private post."
# ben_thatmustbeme elf-pavlik: thats sort of difficult to give an example of publicly, since they are private
# ben_thatmustbeme i have successfully viewed aaronpk's private posts though
# elf-pavlik example of ACL file not the post itself
# ben_thatmustbeme tantek: i don't post private notes right now
# ben_thatmustbeme its on my to-do list after i get contacts list working
# ben_thatmustbeme elf-pavlik: i'm pretty sure he doesn't use an ACL file, its specified entirely internally
# elf-pavlik tantek, i made quick prototype https://elf-pavlik.github.io/unmpc/ you can use it to post to group spaces https://phubble.tuxed.net/w3c-social/ (public) and https://phubble.tuxed.net/alice-b-day/ (secret) both using same file to define ACL https://github.com/w3c-social/social-web/blob/master/phubble-acl.json
# elf-pavlik i need to fix parsing microformats from secret spaces HTML (small issue with the way i select nodes, but you can see in dev console HTML coming if client app makes request with Bearer Token)
# Loqi Tantekelik made 1 edit to [[Socialwg/2015-06-30]] https://www.w3.org/wiki/index.php?diff=84901&oldid=84899
# elf-pavlik if i can't see private note using reader of my preference i don't see it very somooth experience to run all over the web and fiddle with all kind of UIs just to collect my messages :(
# elf-pavlik unmpc just uses Bearer Token for READ just the same way as for WRITE using micropub endpoint of group wall
# eprodrom jasnell: I've gotten about as far as I'm going to go today
# eprodrom So feel free to proceed without further input from me
# eprodrom NP
# eprodrom I've got 2 pages of notes and issues
# eprodrom But I'll put them into Github over the next couple of days
# eprodrom ha
# eprodrom don't plus plus me until you see the issues
# eprodrom They could be awful
# elf-pavlik aaronpk, kylewm do you use webmention to notify people about private posts ?
# elf-pavlik aaronpk, i get this web mention to my reader which i can use to get bearer token for read private note, then it could work i guess ...
# elf-pavlik jasnell, bblfish suggested tests with mergning data from AS2.0 orgiginating from different publishers, i would like to add example from issue 134 to such test https://github.com/jasnell/w3c-socialwg-activitystreams/issues/134#issuecomment-108255400
# elf-pavlik IMO system should treat _:foo != _:foo while ex:foo == ex:foo ... not sure how consumer can do this without applying JSON-LD context to flattened data?
# elf-pavlik _:foo != _:foo if they come from different documents
# elf-pavlik how can consumer not applying JSON-LD context know which properties can consider equal and which not?
# elf-pavlik only http://www.w3.org/TR/activitystreams-vocabulary/ can consider equal, for other it requers information from JSON-LD context
# elf-pavlik jasnell, what do you think about adding warning: "If you don't assign full URIs in JSON-LD context for custom terms that you use, consumers can NOT integrate your data with data from other sources" ?
# elf-pavlik hmmmm.... maybe at least validator can warn when it detects falling back to _: ?
# elf-pavlik just so people know that it comes with some draw backs
# elf-pavlik should i create issue in https://github.com/w3c/activitystreams-testing/issues ?
# elf-pavlik melvster, do you propose falling back to urn:foo: and urn:foo: in case of any use of not mapped foo property ?
# elf-pavlik melvster, IMO mapping two different foo properties to same urn:foo could make things even worst than how i see this _: trick
# elf-pavlik consumer would end up with properties which have same URI but got used with compleately different intention and meaning
# elf-pavlik catching _:foo != _:foo when they come from two documents sounds doable, if you map it to same URI you lost the distinction
# elf-pavlik jasnell, IMO we neede more https://www.w3.org/wiki/Socialwg/Deployments to get some real hands one experience
# elf-pavlik s/one/on/
jdp23 joined the channel
bblfish_, KevinMarks, shepazu, Arnaud and jasnell joined the channel