Technical Architecture Group Teleconference

<trackbot> Date: 08 May 2014

<slightlyoff> I can't make today's standup

<slightlyoff> I've got an overlapping meeting which I'm supposed to be running = \

<slightlyoff> sincerest apologies

<slightlyoff> my status is predictable, though: this is my first day back from a week out of commission due to a health issue.

<slightlyoff> not much change

<slightlyoff> been better, been worse. Working from home

<slightlyoff> off the pain meds entirely, so I think I'm pretty close to "back"

<slightlyoff> thanks for asking = )

trackbot, start telcon

<trackbot> Meeting: Technical Architecture Group Teleconference

<trackbot> Date: 08 May 2014

<dka> Example of capability URLs “gone bad”: http://classic.slashdot.org/story/14/05/07/009248 (story about private files on dropbox leaking due to people accidentally sharing the URLs)

<plinss> trackbot, prepare telcon

<trackbot> Meeting: Technical Architecture Group Teleconference

<trackbot> Date: 08 May 2014

<Domenic_> JeniT: I think if you look at the full minutes it will be better.

<scribe> ScribeNick: JeniT

<scribe> Scribe: Jeni Tennison

AppLinks

plinss: we need to give feedback on AppLinks

Domenic_: I briefly read the articles and took a look, but I’m not sure how it applies to the web

plinss: it seems like the opposite of web intents

… diverting web content into native apps

Domenic_: my opinion is that this is a sign that the web is failing

… and our policy should be to fix the web

<plinss> http://applinks.org/documentation/

Domenic_: I don’t know what kind of feedback they want

<dka> Right - links that invoke native apps…

plinss: I think they want more high-level design policy feedback

Domenic_: it’s reasonable for companies to encourage this because it gives best user experience right now

… from a policy perspective, we should fix the web and this shouldn’t be necessary for a good user experience

dka: realistically, there’s often a need to invoke a application

… whether it’s a web application or a native application is irrelevant

… and to link to a specific view, eg a specific tweet or specific restaurant in OpenTable

… deep linking to that content

… the way that works right now is very platform specific

… even if we imagine a world where all apps are web apps running as first-class citizens

… we’ll still need that functionality

… the question is whether the web already has what we need for that

Domenic_: my ideal would be to link to a tweet on the web

… and if in the interim you want to redirect to the twitter native app

… you shouldn’t need different syntax

+1

… it should be intercepted by the OS and link to the app

… the examples aren’t clear

… they’ve clearly worked on this problem technically, and know what’s necessary for the user experience they want

… maybe we should ask about whether it’s possible to make links to existing websites the alternative

dka: it’s becoming a middle man between all these things linking to each other

… and the point of the web is you don’t need a middle man

Domenic_: sure, if the app doesn’t exist on the web you need something different, but pretty much all these apps are on the web, the links should exist

strong +1 from me

dka: someone should write that up and send that to them; I’d be happy to

Domenic_: it would be great if you could do an initial draft, I’d be interested in being involved

JeniT: I’d be happy to review & contribute to that too

<twirl> +1

dka: I’d like to get Dom involved in that conversation as well

… he’s done a lot of thinking about this

<dka> ACTION: Dan to draft an initial feedback on applinks [recorded in http://www.w3.org/2014/05/08-tagmem-minutes.html#action01]

<trackbot> Created ACTION-866 - Draft an initial feedback on applinks [on Daniel Appelquist - due 2014-05-15].

Sergey

twirl: I’m doing work on web animations & eme resolution, nothing new

JeniT

JeniT: we need to take forward or pass on the packaging work

<dka> Feedback Sergey still needs: https://github.com/w3ctag/spec-reviews/pull/27 , https://gist.github.com/twirl/9483deeb93d134ad2aa8

… there’s the draft spec, a couple of issues that need some attention, but it needs to be passed on

plinss: we talked about doing some work to give the TAG the ability to do this work

dka: I sent an initial email, I haven’t had a reply, I need to follow up

plinss: I imagine it won’t be quick, so we probably shouldn’t wait

… I don’t know who to

JeniT: I think the thinking was either WebApps or SysApps

<dka> +1 on not blocking

JeniT: I don’t think there’s any technical work that’s being blocked: it needs to be published as a Working Draft for input

… and I’d rather hand over earlier in the process than later, to enhance engagement

plinss: I’ll reach out to the chairs of WebApps & SysApps & see what they say

dka: nothing has happened about the URL spec since our F2F

JeniT: I think dka was going to do a blog post about capability URLs

dka: oh yes, I’ll draft something

JeniT: I also have to email TAG about integrity URLs

Domenic_

Domenic_: I’ve continued on WebCrypto review and I need to write it up

… the editor is aware but for reference I should write it

… also I gave a talk about what the web needs to do to compete with native

Dan

dka: I sorted out the minutes from the F2F

Domenic_: could you blog about that?

dka: I should do, yes

Domenic_: at least topics that were discussed (I know it takes time)

Peter

plinss: we still need to make a resolution for twirl about web animations

Domenic_: I *will* look at it this week

… on EME I’m not sure I’m the right person

plinss: yeah, we need feedback from a few other people on that

AOB

ADJOURNED