#social 2016-07-26

2016-07-26 UTC
ben_thatmust, jasnell, tantek and eprodrom joined the channel
#
sandro
trackbot, start meeting
#
trackbot
is preparing a teleconference.
RRSAgent joined the channel
#
trackbot
RRSAgent, make logs public
Zakim joined the channel
#
RRSAgent
I have made the request, trackbot
#
trackbot
Zakim, this will be SOCL
#
Zakim
ok, trackbot
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 26 July 2016
#
tantek
heads-up: Evan is supposed to chair today per our regular schedule from the home page
#
tantek
unless Arnaud is able to swap back for him since Evan chaired for Arnaud last week
#
sandro
present+
#
Loqi
ben_thatmustbeme: tantek left you a message on 2015-03-09 at 11:41pm UTC: yes thank you for the reminder re: chairing tomorrow. updated: https://www.w3.org/wiki/Socialwg/2015-03-10
#
aaronpk
oh man haha
#
aaronpk
i fixed the !tells
#
Loqi
awesome
#
aaronpk
present+
#
rhiaro
brb 3 minutes
#
tantek
present+
#
eprodrom
About to join
#
eprodrom
present+
#
cwebber2
present+
#
eprodrom
Arnaud: are you in?
annbass joined the channel
#
ben_thatmustbeme
offers to scribe
#
rhiaro
present+
#
eprodrom
scribenick: ben_thatmustbeme
#
ben_thatmustbeme
scribe: Ben Roberts
#
eprodrom
chair: eprodrom
#
csarven
present+
#
annbass
present+
#
annbass
(still dialing in)
dmitriz joined the channel
#
ben_thatmustbeme
Topic: approval of last weeks meetings
#
dmitriz
present+
#
eprodrom
TOPIC: Minutes for last week
#
eprodrom
PROPOSED: accept https://www.w3.org/wiki/Socialwg/2016-07-19-minutes as minutes for meeting of 2016-07-19
#
ben_thatmustbeme
if youl have a moment please review the minutes
#
ben_thatmustbeme
eprodrom: i think there was an action to clear out the AS2 issues, but i'm not sure it got formalized in any way
#
eprodrom
+1
#
ben_thatmustbeme
... I think hte minutes are pretty good though
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
ben_thatmustbeme
eprodrom: if you have a opinion on the minutes please chime in
#
tantek
quickly reads
#
tantek
+1 looks good
#
eprodrom
RESOLVED: accept https://www.w3.org/wiki/Socialwg/2016-07-19-minutes as minutes for meeting of 2016-07-19
#
ben_thatmustbeme
is tempted to put minutes in pig latin some week and see if how long before anyone notices
#
ben_thatmustbeme
eprodrom: lets mark that as resolved and move on
#
rhiaro
ben_thatmustbe... has crossed my mind too :)
#
ben_thatmustbeme
... i have one admin item i'd like to move up here
#
eprodrom
TOPIC: reducing meeting frequency during August
#
ben_thatmustbeme
eprodrom: we have done this during vacation periods before. During late july, early aug, people tend to be on vacation on lot
#
Zakim
sees rhiaro on the speaker queue
#
eprodrom
ack rhiaro
#
Zakim
sees no one on the speaker queue
KevinMarks joined the channel
#
ben_thatmustbeme
... so this is a good argument for reducing meetings, but we are on a limited schedule
#
ben_thatmustbeme
rhiaro: If we move to bi-weekly formal meetings, i would suggest having informal Social Web Protocols meeting
#
KevinMarks
present+
#
cwebber2
I'm for that if others are interested
#
ben_thatmustbeme
rhiaro: just to make sure things keep moving until september as we have a lot of work to do
#
tantek
q+ to just note he'll be out Aug 9 and 16
#
Zakim
sees tantek on the speaker queue
#
ben_thatmustbeme
eprodrom: that sounds like a great way to lessen our load while still moving forward
#
eprodrom
ack tantek
#
Zakim
tantek, you wanted to just note he'll be out Aug 9 and 16
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
tantek: i think thats probably a good suggestion. i have a few dates that i'll be away (listed in IRC)
#
ben_thatmustbeme
... we have 5 telcons scheduled in august now.
#
ben_thatmustbeme
eprodrom: how about we do the 2nd and the 23rd and have a two week gap
#
eprodrom
PROPOSED: only hold formal WG telecons on Aug 2 and Aug 23 2016
#
ben_thatmustbeme
sandro: so cancelling 9th, 16th, and 30th
#
sandro
+1 works for me
#
eprodrom
+1
#
ben_thatmustbeme
eprodrom: and those would be good times for informal meetings
#
cwebber2
+1 assuming we do the informal meetings
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
rhiaro
+1 assuming we can have inbetweeny meetings for spec editors
#
sandro
(not sure I can make the 23rd)
annbass_ joined the channel
#
ben_thatmustbeme
eprodrom: looks like sandro and tantek may be out for the 23rd. i think it would be bad to have 4 weeks off
#
ben_thatmustbeme
tantek: if i'm not chairing, i can at least listen in
#
eprodrom
RESOLVED: only hold formal WG telecons on Aug 2 and Aug 23 2016
#
ben_thatmustbeme
tantek: does that put Arnaud to chairing the 23rd?
#
ben_thatmustbeme
eprodrom: yes, and i'm his backup
#
ben_thatmustbeme
eprodrom: great, lets move on to our actual work for this week
#
eprodrom
julien?
#
ben_thatmustbeme
TOPIC: welcoming Julien
#
rhiaro
He said in email he'd be here
#
ben_thatmustbeme
eprodrom: if not, the topic may not be worthwhile, he said he would be here, but he may have had trouble getting on to IRC
#
rhiaro
I can do
#
ben_thatmustbeme
... if anyone wants to try on that email thread to contact him, maybe he will come in later
#
ben_thatmustbeme
TOPIC: AS2 status
#
tantek
chair: tantek
#
ben_thatmustbeme
eprodrom: that is going to be me mostly just talking. tantek could you chair this segment
#
annbass_
notes the benefit of 3 chairs .. lots of flexibility
#
tantek
notes https://www.w3.org/wiki/Socialwg#Future_Meetings has been updated with previous telcon resolution
#
ben_thatmustbeme
... when we talked last week, we had a number of outstanding issues around internationalization that were in various states
#
ben_thatmustbeme
... most of them have been resolved, the ones that have not been resolved are because there is some disagreement
#
ben_thatmustbeme
... one thats awaiting approval but i think was resolved. 337 was resolved to commenter's specifications. one of them is one that james objected to (344) so we are waiting for commenter. thats an editorial issue of where we include certain properties
#
ben_thatmustbeme
... there was one important normative one that we resolved through consensus (341) we did get feedback from jsnell and he was in agreement with the last proposal so there were no more objections to it
#
ben_thatmustbeme
... we had one non-editorial, normative change that is still outstanding. I would like some guidance from the group on it (338)
#
ben_thatmustbeme
... the issue is around the name property
#
ben_thatmustbeme
... everything in AS2 has a name, it was originally title, then display-name, then we resolved it to name. the previous versions of this property have not allowed HTML in the property.
#
ben_thatmustbeme
... this would be for things like name of a video, title of a photo, etc. etc. etc. This likely comes from ATOM, which discouraged putting markup in the title property
#
ben_thatmustbeme
... there is the stylistic of being similar to html, not having markup in the page title. The nice thing is for out-of-band display of an object
#
ben_thatmustbeme
... so you could just use name and know that you do not have markup
#
KevinMarks
atom title can have markup, fwiw
#
ben_thatmustbeme
... there would be some advantage for internationalization
#
ben_thatmustbeme
... yes KevinMarks, you can, but you have to add some extra tags
#
ben_thatmustbeme
... but the default is not to do it
#
ben_thatmustbeme
... i think its also possible to do it with HTML, but it gets badly rendered
#
eprodrom
name: "My recipe for gazpacho"
#
KevinMarks
tantek used to confuse Reader by putting xhtml in his atom:title
#
Zakim
sees aaronpk on the speaker queue
#
tantek
what KevinMarks means is that I would demonstrated bugs in Reader :P
#
eprodrom
"My recipe for <span lang="en">gazpacho</span>"
#
ben_thatmustbeme
... the use came that came up was something like, "if you have a name like "my name is gazpacho'" its doesn't show that gazpacho is another language
#
ben_thatmustbeme
you could do some extra markup for switching languages within a name
#
ben_thatmustbeme
... that is the motivation for adding markup to the name property
#
Zakim
sees aaronpk on the speaker queue
#
ben_thatmustbeme
... there is also the question of doing directionality
#
KevinMarks
s/en/es/
#
ben_thatmustbeme
... there is also a way to do this in UTF8
#
eprodrom
q?
#
Zakim
sees aaronpk on the speaker queue
#
ben_thatmustbeme
... its possible to do directionality without markup, its not possible to do language without markup
#
ben_thatmustbeme
tantek: let me stop you for a second there for aaron
#
tantek
s/aaron/evan
#
ben_thatmustbeme
aaronpk: i wanted to mention i had a siimilar issue against micropub, and i think the example you gave is not the core issue, its mostly about the directionality of text
#
ben_thatmustbeme
... the problem comes up where you have both directions , left to right and right to left within the same string
#
KevinMarks
"I pronounce <span lang="vi">Phở tái </span> like French for armchair, <span lang="fr">fauteil</span> "
#
ben_thatmustbeme
... heres a link to a draft that has been written up on this. the better issue on this is punctuation when it switches direction like a quote in text, and the punctuation in it needs extra data
#
sandro
screen readers care about the language, I believe.....
#
ben_thatmustbeme
... the solution in micropub was you define a base directionality and there isn't much use to doing it on the word, but there is actual reasoning to directionality on punctuation. hopefully that gives some background to it as its pretty unfamilliar to many of us
#
ben_thatmustbeme
annbass: has it been solved elsewhere?
#
ben_thatmustbeme
aaronpk: only in HTML as you can specify directionality of any block
#
ben_thatmustbeme
tantek: thats a problem in every json format then really
#
ben_thatmustbeme
aaronpk: its a string encoding issue
#
annbass
Richard Ishida = r12a
#
ben_thatmustbeme
... there is one question i'm asking him about, there is a unicode character for right-to-left-mark, and i'm asking to see if thats sufficient for it
#
eprodrom
'It will force people to convert to or use control characters for inline bidirectional controls, and will prevent inline annotation for language change.'
#
annbass
W3C Team leader for Internationalization (i18n) ... world expert on i18n in web technologies
#
ben_thatmustbeme
... this was all on the micropub issue. i would suggest reading the intro that was written there
#
ben_thatmustbeme
.... i would suspect he's not really asking for markup in the name, but asking for directionality to be solved
#
ben_thatmustbeme
eprodrom: i think he is actually asking for it, its in the title of the issue...
#
ben_thatmustbeme
aaronpk: i think he's asking "why its not there" not actually "asking for it" which is very different
#
ben_thatmustbeme
annbass: have you talked to him?
#
ben_thatmustbeme
aaronpk: i didn't realize this was an issue on as2 as well
#
csarven
W3C Web Annotation WG uses `oa:textDirection` with values like oa:ltr or oa:rtl. That however is for the subject.
#
ben_thatmustbeme
tantek: whats odd about this is that this is an issue on any string encoding
#
csarven
.. that is not for a particular property
#
ben_thatmustbeme
... so i'm a little frustrated by it being brought up like its asking us to solve the problem for everyone else
#
Loqi
[Robert Sanderson] Web Annotation Vocabulary
#
ben_thatmustbeme
sandro: well there is a solution, use html
#
annbass
that's my point, Tantek .. if this is a problem that needs a global solution, maybe a small team could work on ... including others from i18n and whatever other groups
#
ben_thatmustbeme
eprodrom: we do use html in other properties, its just we don't allow it in this case
#
Zakim
sees aaronpk, cwebber on the speaker queue
#
tantek
ack aaronpk
#
Zakim
sees cwebber on the speaker queue
#
ben_thatmustbeme
... from my POV the burden is put on implementers to have to sanitize it though
#
ben_thatmustbeme
... its non-trivial vs a stirng that you can just HTML escape and just show on a webpage
#
tantek
q+ to note that we tried this for Atom with entry title with markup, and implementations failed to get interop.
#
Zakim
sees cwebber, tantek on the speaker queue
#
ben_thatmustbeme
... it would be putting a lot of AS2 consumers, for what seems to be only two use-cases
#
ben_thatmustbeme
aaronpk: to be clear, i am in favor of not having HTML, but its an issue that would be possible to solve later
#
ben_thatmustbeme
(back and forth about what the commentor actually wanted, including quoting the issue)
#
sandro
:-) :-) cwebber2
#
Loqi
cwebber2 has 67 karma
#
tantek
cwebber2++ wow
#
Loqi
cwebber2 has 68 karma
#
eprodrom
"It will force people to convert to or use control characters for inline bidirectional controls, and will prevent inline annotation for language change."
#
ben_thatmustbeme
eprodrom: he seems to think thats sub-optimal but could work. but would not work for language change
#
ben_thatmustbeme
... i'm not sure about this. it sounds like what you are saying we should do.... (incomplete thoughts)
#
Zakim
sees cwebber, tantek on the speaker queue
#
tantek
ack cwebber
#
Zakim
sees tantek on the speaker queue
#
Loqi
[James M Snell] Activity Streams 2.0
#
ben_thatmustbeme
tantek: cwebber has been on the queue
#
ben_thatmustbeme
cwebber2: i agree with evan that it does raise the level of work for implementors
#
ben_thatmustbeme
... i've certainly seen plenty of implementers just use the title and assume no html
#
ben_thatmustbeme
... i also wonder, is the Unicode RTL method composable in HTML and whether or not that would make any impact
#
Zakim
sees tantek on the speaker queue
#
tantek
ack tantek
#
Zakim
tantek, you wanted to note that we tried this for Atom with entry title with markup, and implementations failed to get interop.
#
Zakim
sees no one on the speaker queue
#
cwebber2
that's a good point
#
ben_thatmustbeme
tantek: this whole, embedding markup in names thing actually made it in to the atom spec, i don't know why, but it did. so i tried putting that in my website just to test it across everything. the end result was that there was almost no readers that supported
#
KevinMarks
or they did support it and it blew up their layout - when you put an <h2> in it
#
sandro
+1 try giving that answer, maybe in spec
#
ben_thatmustbeme
... it led to bad interop on that property. so i would say to push-back strongly saying that it leads to bad interop
#
ben_thatmustbeme
... i notice that a bunch of these are novel things, that is to say, its not really a criticism of this spec, no spec really supports that
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
... if you look at any existing APIs in the social space, and i'll bet you will find none who support this
#
eprodrom
+1
#
cwebber2
yeah +1 as well
#
ben_thatmustbeme
... so you could push back saying that if its such a strong use-case, why has no company had to deal with this before?
#
ben_thatmustbeme
sandro: i think thats a reasonable response, but it might be worth noting in the spec why thats not supported
#
Zakim
sees annbass on the speaker queue
#
ben_thatmustbeme
eprodrom: i'd be happy to maybe add this in our description of the name property, give a quick gloss on why it does not support HTML markup. for historical reasons, implementator experience, etc
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
sandro: and a work-around of saying you can always put that markup down in some body-ish
#
tantek
q+ to note that not even HTML <title> allows nested markup :P
#
Zakim
sees tantek on the speaker queue
#
Loqi
[James M Snell] Activity Streams 2.0
#
annbass
I think it is important to acknowledge the issue, but with explanations such as being discussed to say why we didn't solve it
#
ben_thatmustbeme
eprodrom: i'd be happy to do that. is it possible for us to do this.... the suggestion that aaron made, i think james has already addressed in 4.7.1.1
#
eprodrom
"Because the name (and corresponding `nameMap`) property does not permit HTML markup, the Unicode Bidirectional Control characters [ BIDI] may be used to identify text direction:"
#
ben_thatmustbeme
eprodrom: I think that should probably be sufficient
#
annbass
if we spoke Arabic or Hebrew, we'd probably be more sensitive to the issue
#
Zakim
sees tantek on the speaker queue
#
tantek
annbass that sounds hypothetical
#
eprodrom
"Explain why there's no markup in 'name' in the vocabulary document"
#
ben_thatmustbeme
regrets volunteering to scribe
#
tantek
ack tantek
#
Zakim
tantek, you wanted to note that not even HTML <title> allows nested markup :P
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
tantek: i wanted to bring up one more thing. the HTML <title> tag itself does not allow markup
#
KevinMarks
because title is not in body.
#
annbass
(I was just expressing my thoughts; not proposing text for summary)
#
ben_thatmustbeme
... i would suggest we could go further and say MUST NOT add markup to the title
#
Zakim
sees annbass on the speaker queue
#
ben_thatmustbeme
... json-apis don't do it, html doesn't do it. etc
#
eprodrom
+1 to tantek's point
#
tantek
ack annbass
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
... and bounce it back to i18n, to say thay have a lot more work if they are just going to try to push this in to random specs
#
cwebber2
it's probably a very hard problem
#
ben_thatmustbeme
annbass: my concern is that its a catch-22, if you say 'others don't do it, so we won't'
#
cwebber2
so I'm not sure that it's the fault of other groups
#
cwebber2
I agree to annbass' wording
#
ben_thatmustbeme
tantek: its not a catch-22, its their job to define how to do it
#
ben_thatmustbeme
annbass: I think its better to at least accept that its an issue, but its not something we are going to solve in this group
#
ben_thatmustbeme
tantek: i'm saying that if it was a problem, then it is a global problem, but given that every implementation for social space have not hit this issue, then i would qustion that the problem exists
#
annbass
+1 on Sandro's point
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
sandro: can i suggest that we step back from this issue, and its not something we want to deal with in this group and just say that there is some historical reasons for not doing it right now, we are not going to push that ball uphill
#
ben_thatmustbeme
tantek: sandro would you like to propose a resolution so we can push this through
#
ben_thatmustbeme
wonders who is talking randomly
#
annbass
sorry was me
#
ben_thatmustbeme
i wasn't going to call out name :P
#
tantek
that's the job of the chairs :P
#
ben_thatmustbeme
rests his hands
#
Zakim
sees rests, his on the speaker queue
#
annbass
hehe; that's the danger of unmuting to say something
#
sandro
PROPOSED: We reply to r12a about as#338 and micropub #37 saying that we don't do HTML in these fields because implementation experience as with atom has shown it's too hard to implement / doesn't get implemented, and we think it's more important to have consistency
#
ben_thatmustbeme
aaronpk: i'm only going to point out that in micropub #37 that he never asks for html in the property
#
ben_thatmustbeme
... i did find the unicode control characters for this so i responded with that but have not heard back yet
#
KevinMarks
fwiw, feedparser has test cases for atom with html titles in all 3 modes
#
ben_thatmustbeme
... my suggestion is to note that HTML is not the solution for that, in case that comes up
#
aaronpk
this is a great post describing how twitter solved it https://blog.twitter.com/2012/right-to-left-support-for-twitter-mobile in short, they detect the number of RTL vs LTR chars and set the base text direction accordingly.
#
sandro
PROPOSED: We reply to r12a about as#338 (and as far as it applies to micropub #37) saying that we don't do HTML in these fields because implementation experience as with atom has shown it's too hard to implement / doesn't get implemented, and we think it's more important to have consistent interop
#
eprodrom
+1
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
annbass
but it doesn't get at Aaron's point that r12a didn't ask for HTML
#
ben_thatmustbeme
tantek: any objections to that?
#
annbass
I'm fine with making a statement .. just needs to be accurate re: what Richard asked
#
aaronpk
annbass, it's fine, we're not proposing closing the micropub issue with this
#
annbass
could we work with Richard to find accurate language?
#
eprodrom
annbass: yes we can
#
cwebber2
with annbass wording though
#
ben_thatmustbeme
tantek: given that we have given it a few minutes, and we have several +1s, lets declare this resolved to give a good consensus
#
sandro
RESOLVED: We reply to r12a about as#338 (and as far as it applies to micropub #37) saying that we don't do HTML in these fields because implementation experience as with atom has shown it's too hard to implement / doesn't get implemented, and we think it's more important to have consistent interop
#
tantek
chair: eprodrom
#
ben_thatmustbeme
eprodrom: i'll do the response to richard and other additions
#
ben_thatmustbeme
... we only have 2 miniutes left, i see 2 options, we defer micropug #36 to next week or we extend the meeting a little
#
ben_thatmustbeme
aaronpk: i'd like to get the group to look at this its, short
#
ben_thatmustbeme
eprodrom: lets extend a little
#
ben_thatmustbeme
TOPIC: micropub issue 36
#
ben_thatmustbeme
aaronpk: this is likely something that applies to other APIs, etc. it is basically about the error messages not containing anything for directionality, etc
#
ben_thatmustbeme
... my proposal is that this is out of the oauth 2.0 spec that says these are specifically for developers and not user-facing
#
tantek
sounds like a reasonable proposal
#
ben_thatmustbeme
so i would specifically like to add that wording and that we specifically don't have a method for localizing those
#
tantek
sounds like we could use a PROPOSED for that?
#
Zakim
sees rests, his on the speaker queue
#
eprodrom
PROPOSED: Adopt OAuth 2.0 language for error message purpose and defer any localization of error messages
#
Zakim
tantek, if you meant to query the queue, please say 'q?'; if you meant to replace the queue, please say 'queue= ...'
#
Zakim
tantek, if you meant to query the queue, please say 'q?'; if you meant to replace the queue, please say 'queue= ...'
#
Zakim
tantek, if you meant to query the queue, please say 'q?'; if you meant to replace the queue, please say 'queue= ...'
#
eprodrom
PROPOSED: Adopt OAuth 2.0 language for error message purpose and defer any localization of error messages in API result
#
tantek
q- rests, his
#
Zakim
sees no one on the speaker queue
#
eprodrom
ROPOSED: Adopt OAuth 2.0 language for error message purpose and defer any localization of error messages in API results
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
eprodrom
+1
#
rhiaro
haha I thought everyone had just drifted off for a while
#
ben_thatmustbeme
eprodrom: if we could get some votes on that
#
Loqi
nice
#
ben_thatmustbeme
eprodrom: I don't see any -1s so i'm going to mark this as resolved
#
eprodrom
PROPOSED: Adopt OAuth 2.0 language for error message purpose and defer any localization of error messages in API results
#
rhiaro
+0 because I don't know enough, not unenthusiastic.. deferring to editor :)
#
eprodrom
RESOLVED: Adopt OAuth 2.0 language for error message purpose and defer any localization of error messages in API results
#
ben_thatmustbeme
what date are we publishing PTD, JF2, etc?
#
annbass
thanks a lot Evan and Ben!
#
annbass
and Tantek too
#
eprodrom
trackbot, end meeting
#
Zakim
As of this point the attendees have been sandro, ben_thatmustbeme, aaronpk, tantek, eprodrom, cwebber, rhiaro, csarven, annbass, dmitriz, KevinMarks
#
trackbot
is ending a teleconference.
#
trackbot
Zakim, list attendees
#
tantek
ben_thatmustbeme: today if we can
#
trackbot
RRSAgent, please draft minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2016/07/26-social-minutes.html trackbot
#
trackbot
RRSAgent, bye
#
tantek
sandro are you around to help?"
#
RRSAgent
I see no action items
#
sandro
to help draft minutes? I always ask amy for help
#
rhiaro
to help figuring out publishing ptd and jf2, I presume
#
tantek
sandro to help with publishing two specs that have basically been ready for publishing
#
tantek
but we've delayed to try to sync-up with the CRs which are now actually blocked on substantive issues
#
rhiaro
This is just getting them out as fpwd, right?
#
tantek
can you help with that too? since you're also a staff contact for the WG :)
#
rhiaro
I know how to do this now \o/ sandro: Shall I just sort them both out for publishing next Tues?
#
rhiaro
Assuming tantek and ben_thatmustbeme have versions of the docs that mostly pass pubrules
#
tantek
rhiaro: why do we have to wait a week? it's still Tuesday
#
rhiaro
Thursday is possible.. The webmaster wants at least 24 hours notice
#
tantek
ah, that's for FPWD right?
#
tantek
Thursday would be good
#
rhiaro
sandro: just confirm, no reason to delay any further? If not I can push all the buttons to get the request sent this afternoon
#
rhiaro
tantek and ben_thatmustbeme, can you put Thursday's date on them and link me to the definitive versions you want published please?
#
rhiaro
is excited about newfound w3c CVS powers. The novelty will probably wear off soon..
#
bigbluehat
rhiaro: with great power...
#
ben_thatmustbeme
comes lots of people annoying you to use it for them
#
tantek
thanks rhiaro working on date adjustment
#
tantek
rhiaro: other than a few false-negatives from pubrules, https://tantek.github.io/post-type-discovery/index-wd.html looks good to go dated for 2016-07-28
#
Loqi
[Tantek Çelik] Post Type Discovery
#
tantek
can you let me know what else I need to do? or do you have it from here?
#
rhiaro
tantek: I've got it I think. I'll let you know if anything comes up.
#
rhiaro
ben_thatmustbeme: can you do the same for jf2 so I can send one email to the webmaster?
#
tantek
Thank you! And yes I'm ok with waiting for ben_thatmustbeme / jf2 to pair them.
#
ben_thatmustbeme
rhiaro: sorry, i got distracted, this has been ready for a while. just updated the dates in it http://dissolve.github.io/jf2/publish/
#
Loqi
[Benjamin Roberts] JF2 Post Serialization Format
#
rhiaro
Thanks!
shepazu_ and tantek joined the channel
#
Zakim
excuses himself; his presence no longer seems to be needed
shepazu joined the channel
#
tantek
!tell Arnaud are you available to chair the SWWG telcon 2016-08-23?
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek
ALL: Draft agenda for next week's telcon is up: https://www.w3.org/wiki/Socialwg/2016-08-02
KevinMarks joined the channel