cwebber2aaronpk: there were a few things to address, I've been working on a new draft that should be ready to go, I've summarized the pages in document
cwebber2aaronpk: here's the latest micropub draft, I've added in a link to the test suite describing what the test suite will do, I've added conformance and exit criteria listing all features you'd expect, basically spec infrastructure we did with webmention
cwebber2aaronpk: so the accessibility group looked over all 5 specs, only had comments about micropub, they said they'd like examples of posts including accessibility info, such as alt-text on an image
cwebber2tantek: from SocialWG perspective of studying proprietary APIs, have you done any background research as how twitter, instagram, etc have provided alt-text of an image, or if they do at all? if they don't that's also useful info
cwebber2... from what I've seen of people who actually consume alt-text of images, it's a description of the image, rather than what someone says about the post
cwebber2tantek: it may be good to discuss inline that there's an outstanding issue and summarize and link to it so that anyone else reviewing the draft can go "oh yeah someone took a look at this"
cwebber2... the second is the question of whether it makes sense that everything at risk, with the reductio ad absurdum (?) that nothing is implemented, or we have a small set of features and types that don't really hang together or have relationship together
cwebber2... so ralph has suggested that we identify a small number of classes which will definitely be in a future version, where we wouldn't be able to go forward without those types and properties
cwebber2... most of these were addressed by James, who did an omnibus pull request over the weekend, he can't be with us this time around, but what we have is a number of items about i18n in activitystreams
cwebber2... the one normative recommendation was that if there was not a way to identify the default language for a document that we recommend that implementers use the named map / content map / ** map properties rather than their default version
cwebber2... james noted that there are some implmeentations that will not be using the json-ld structure, and so he recommended that we use the longer mechanisms
rhiarocwebber2: I don't have a strong opinion. I think that it's not a bad thing or very hard even if you're not using a json-ld processor to look in that context
cwebber2eprodrom: another possibility is that if we use a language tag which means unknown, that could be somethign we use here to specify that if there is not a language tag, assume it's UND (undetermined)
rhiarocwebber2: I think I'm all for the suggestion that we make it a SHOULD when you know the language and we also say the implementations must look at @context to look for it. It's not too tough to look there even if you're not using json-ld
rhiaro... But I'm not sure that we should change every example in the activitystreams doc to include an @context with the language property, the reason being that there's a classic problem where people start wanting to provide a language with content they don't know, and suddenly you have a bunch of content in another language tagged as English because the programmer was lazy
rhiarosandro: It looks like in json-ld it can go in the ocntent if you're using the expanded form, but since you're using the compacted form there's no place for the language to go so it has to go in the context
rhiaro... There is the question, I'm not exactly sure what happens next, but I think we push back publication. When do we make our decisions here and then go forward? Or do we fix after we publish?
rhiarotantek: the first part is there is non-trivial discusison, we're not going to get an answer on this telecon. We allow people to continue iterating on that issue, specifically cwebber2, rhiaro and sandro to chip in more
rhiaro... Second is about publishing. Either we decide to publish with this issue outstanding in which case we may want to call it out explicitly in the draft
rhiarosandro: I think I heard Evan say he wasn't comfortable overriding one of James's decisions without James, so sounds like we need to wait until next week until James is back online and we can get his attention
rhiaroeprodrom: We've got two feet on the ground and it's which we want to lean on. I'd like to publish what we have as an ED as a WD, and that will make it easier for review
rhiarosandro: So we could try to go ahead with jf2 by itself. I had been waiting for other things, but as you've heard the other things have been snagged on other issues
KevinMarksthe specfic issue will be for parsing photo explicitly, and if we need to define a new object for those to hold richer metadata in parsed form
ZakimAs of this point the attendees have been sandro, aaronpk, rhiaro, akuckartz, cwebber, csarven, wilkie, eprodrom, annbass, ben_thatmustbeme, KevinMarks, tantek
Zakimleaving. As of this point the attendees have been sandro, aaronpk, rhiaro, akuckartz, cwebber, csarven, wilkie, eprodrom, annbass, ben_thatmustbeme, KevinMarks, tantek
rhiaroaaronpk: oh because the annotation on there is currently stored on a solid server which doesn't know how to not bother trying to auth you for public stuff
rhiarotantek: extensively on various whiteboards in our office, but presumably somewhere else as well, I'll check with dmitriz. I believe the main reason for openidconnect was the multiple existing implementations of services and libraries. I've been out of the loop on the actual dev of the auth stuff for the last month or so though
tantekThe biggest problem with openid connect is that it seems to be following the same multiple central silos (who don't accept each other's identifiers) antipattern that openid did
tanteklet me know if you find two big "implementations of services" who actually "peer", that is, both produce and consume each others identities. until then, OpenID Connect is no better "socially" or in a distributed/decentralized fashion than OpenID 1 or 2 etc.
tantekanyway, I'll wait for the online documentation, otherwise, I'll accept that "whiteboarding" is the decisioning making methodology that was used (and what that entails).
rhiaroBut while I'm looking at it, there's a list of implementations here and to what type of conformance they have (to what extent they talk to each other, I think) http://openid.net/certification/
Loqi Eprodrom made 1 edit to [[Socialwg/2016-07-12]] https://www.w3.org/wiki/index.php?diff=98972&oldid=98954
ben_thatmust waves
RRSAgent logging to http://www.w3.org/2016/07/12-social-irc
ben_thatmustbeme present+
KevinMarks present+
aaronpk changes described here http://micropub.net/draft/#changes-from-21-june-2016-wd-to-this-version
cwebber2 PROPOSED new draft of micropub at http://micropub.net/draft/ with addition of image upload alt-text feedback
rhiaro ... But I'm not sure that we should change every example in the activitystreams doc to include an @context with the language property, the reason being that there's a classic problem where people start wanting to provide a language with content they don't know, and suddenly you have a bunch of content in another language tagged as English because the programmer was lazy
tantek PROPOSED: publish AS2 documents as WDs with calling out issue https://github.com/w3c/activitystreams/issues/341 inline in the appropriate place in the document(s)