TAG/MeetCandidates2023/Daniel Appelquist

From W3C Wiki

Daniel Appelquist - TAG Candidate 2023

These are Dan's answers to the 2023 TAG Candidate Questions.

You can also read Dan Appelquist's nomination statement here.

Quotes from the minutes are not verbatim, and may not accurately reflect the candidate's statements.

What's an interesting question about how the Web’s architecture should evolve that you've come across recently?

Answer here.

What are the technical trends you notice are happening on the Web, and what implications do you see for the work of the W3C?

From the minutes...

The use of the web across multiple platforms, multiple modalities, has been a key driver, making sure that what we do is relevant to all the platforms on which people use the web. Example: in the TAG we have sometimes had design reviews for APIs that look like they are specifically focused on desktop, but the majority of use of the web is on mobile devices. So if we discount mobile are we being relevant to the majority of the use?

What should the TAG's role be in reviewing WG charters?

From the minutes...

As we transition to director-free it's important that the TAG help to chart the technical direction. Reviewing charters and being more involved in the charter development process is one way that can happen. I don't want the TAG to become a blocker or choke point for new work. We have to make sure the TAG can provide feedback in an asynchronous way.

Maps are increasingly important, but maps are done in javascript today, making them inaccessible. How do you feel about adding maps to the web platform?

From the minutes...

Location has been a long discussion. One of the key elements in the geolocation discussion has been how to deal with privacy. Geolocation is a core element of the web, we need to do more with it. Maps is an interesting space; if there is a groundswell of activity I don't see architectural blockers. One way to build activity is to hold a workshop. That's worked well in other areas.

How do you think the appointed TAG seats should be used?

Answer here.

Has the TAG been taking the wrong approach in any of its recent activities, and if so, what would you change?

From the minutes...

The TAG constantly adjusts and tunes itself, deciding how best to use our resources. The TAG has to deliver value. I agree with DanClark's comments about increasing velocity. The TAG has created subgroups to work in parallel; this has helped increase velocity. The TAG has to be open to changing how it works to focus on delivering value. This is a key driver for me.

What can the TAG and W3C do about the environmental and social impacts of the Web?

From the minutes...

I've mentioned this in talking about the Ethical Web Principles. When adding new specs to the web platform we think about a11y, privacy. We can also think about whether the idea causes problems for marginalized communities, or for power consumption. We can think at a macro level about how the web consumes power. Ensuring that as we build web platform design principles or privacy principles we link back to high-level principles. This has not done a sufficient job of getting us to look at remediating existing problems. We need to work together on that.

How do you see the TAG filling a gap in technical leadership?

Answer here.

What is the most important problem the Web Platform faces that the TAG could reasonably address?

Answer here.

What values will you bring to the TAG that other candidates might disagree with?

From the minutes...

Wanted to talk about what Martin was saying. If ppl disagree, we can still interact as humans and maybe agree what consensus can look like. We've had those discussion in TAG for e.g. privacy. We can work through them, figure out what the shape of consensus is, what we agree on... That ability to work with each other in a non-partisan way, to hold onto values and understand where you can work w/ those w/ different values, that's an important aspect of being TAG member. We do our best work when people hold those values. I'd encourage Membership to think about that when voting for TAG.


I'm reminded of what I was going to say: it was that we were talking about role of the TAG in the technical direction of the web, the tussle between things like charter review and getting ahead of new work, and the current heartbeat of TAG, design reviews. TAG's current work mode is because TAG asked for that. We are constantly evolving and I embrace that. We've been adapting and evolving our process: 2 person breakout teams, parallelize work, PP TF to get additional work done. We've been experimenting w/ a lot. Listening to Martin, Mark, Dan Clark I started to get excited about the future of the TAG. This is the kind of energy we need to bring.

What do you see as the role of the TAG in relation to regulators?

Answer here.

What are examples of W3C work that's not really in scope, and of work elsewhere that could be in W3C's scope?

From the minutes...

I'll take the poison chalice. I think W3C takes on areas which seem related to core web, e.g. mobile. When I was involved w/ W3C it was to push a narrative of mobile browsers. I remember ppl saying “this is not the web, the web has nothing to do w/ mobile phones”. Now the majority of web usage is mobile devices. There are certain elements of existing work at w3c for e.g. web auto where the TAG has given feedback where we say “we think this should be more aligned w/ values of the web”. I hear some of the same noise like mobile. It might be the same trajectory. TAG can provide feedback and motive force to bring topic areas back in line w/ the web and across the web plaform.

What specific things did you accomplish in your previous TAG term, or plan to accomplish in your first TAG term?

From the minutes...

As Peter mentioned when we came on as co-Chairs we took the TAG in a new direction. One thing was how to interact w/ web developers. We ran web developer meet-ups alongside TAG meetings. We'd go to Berlin and have a TAG meeting, and found WikiMedia who was willing to host a meet up. We had like 100 developers. We had this in Tokyo. Boston. Melbourne. Many places. This got me excited in role of TAG in demystifying standards and W3C as a place to work in. Also to be answerable to developers. We do this not just for member companies but the community of the web at large, and developer are key to that.

What is your experience/expertise on browser-based front-end and server-backed or back-end standards?

From the minutes...

I was an early support of Social web -> ActivityPub. I co-chaired. I am strongly behind the web not just [missed]. Glad ActivityPub got wide adoption. I think w3c needs to lean into that. I support rechartering that. Community work. I'm a big supporter of that in particular.

What organizational or technical skills will you bring to the TAG?

Answer here.