16:01:10 <RRSAgent> RRSAgent has joined #privacy
16:01:10 <RRSAgent> logging to http://www.w3.org/2014/05/29-privacy-irc
16:01:12 <trackbot> RRSAgent, make logs 263
16:01:12 <Zakim> Zakim has joined #privacy
16:01:14 <trackbot> Zakim, this will be
16:01:14 <Zakim> I don't understand 'this will be', trackbot
16:01:15 <trackbot> Meeting: Privacy Interest Group Teleconference
16:01:15 <trackbot> Date: 29 May 2014
16:01:17 <npdoty> npdoty has joined #privacy
16:01:27 <christine> Hi all. We'll start in a few minutes.
16:01:47 <fjh> zakim, this will be 7464
16:01:47 <Zakim> ok, fjh; I see Team_(privacy)16:00Z scheduled to start now
16:02:03 <fjh> zakim, make logs public
16:02:03 <Zakim> I don't understand 'make logs public', fjh
16:02:11 <jcraig> zakim, who is on the phone?
16:02:11 <Zakim> Team_(privacy)16:00Z has not yet started, jcraig
16:02:13 <Zakim> On IRC I see npdoty, Zakim, RRSAgent, gmandyam, Ryladog, janina, yrlesru, jcraig, fjh, christine, tara, TallTed, terri, trackbot, wseltzer
16:02:17 <christine> Thank you fjh
16:02:30 <yrlesru> zakim, this is yrlesru
16:02:30 <Zakim> sorry, yrlesru, I do not see a conference named 'yrlesru' in progress or scheduled at this time
16:02:42 <jcraig> Zakim, jcraig is [Apple]
16:02:42 <Zakim> sorry, jcraig, I do not recognize a party named 'jcraig'
16:02:44 <npdoty> rrsagent, please make logs public
16:02:48 <MichaelC_> MichaelC_ has joined #privacy
16:02:52 <npdoty> Zakim, code?
16:02:52 <Zakim> the conference code is 7464 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), npdoty
16:03:52 <christine> Giri, are you on the call?
16:04:21 <gmandyam> Yes I am
16:04:36 <JoeHallCDT> JoeHallCDT has joined #privacy
16:04:42 <fjh> zakim, ipcaller.a is me
16:04:42 <Zakim> +fjh; got it
16:04:44 <Zakim> +gmandyam
16:04:45 <jcraig> Zakim, Apple has jcraig
16:04:45 <Zakim> +jcraig; got it
16:04:48 <fjh> zakim, who is here?
16:04:48 <Zakim> On the phone I see [IPcaller], tara, hober, Katie_Haritos-Shea, [Apple], ??P1, +1.214.566.aaaa, WSeltzer, Michael_Cooper_(IndieUI), [CDT], +44.793.550.aabb, npdoty, terri, fjh,
16:04:51 <janina> zakim, ??P1 is me
16:04:52 <Zakim> ... gmandyam
16:04:52 <Zakim> [Apple] has jcraig
16:04:52 <Zakim> On IRC I see JoeHallCDT, MichaelC, npdoty, Zakim, RRSAgent, gmandyam, Ryladog, janina, yrlesru, jcraig, fjh, christine, tara, TallTed, terri, trackbot, wseltzer
16:04:52 <Zakim> +janina; got it
16:04:59 <fjh> Present+ Frederick_Hirsch
16:05:07 <christine> Zakim, [IPcaller] is me
16:05:07 <Zakim> +christine; got it
16:05:44 <christine> 1. Welcome and introductions 2. Geolocation WG 3. IndieUI WG 4. Privacy guidance and process documents 5. TPAC session 6. AOB
16:05:44 <Zakim> - +1.214.566.aaaa
16:05:45 <jcraig> zakim, who is noisy?
16:05:52 <npdoty> npdoty has changed the topic to: Agenda May 29: http://lists.w3.org/Archives/Public/public-privacy/2014AprJun/0009.html
16:05:56 <Zakim> jcraig, listening for 10 seconds I heard sound from the following: christine (64%), terri (4%)
16:06:07 <Zakim> + +1.214.566.aacc
16:06:09 <Hannes_Tschofenig> Hannes_Tschofenig has joined #privacy
16:06:23 <yrlesru> zakim this is aaaa
16:06:27 <janina> Hi, I'm Janina Sajka, Chair of IndieUI (and also PF in W3C-WAI)
16:06:29 <jcraig> Zakim, mute terri
16:06:29 <Zakim> terri should now be muted
16:06:32 <JoeHallCDT> Joe Hall here, chief technologist at the Center for Democracy and Technology, a global online digital civil liberties organization
16:06:38 <MichaelC> Michael Cooper, staff contact to IndieUI WG
16:06:39 <gmandyam> Giri Mandyam, Qualcomm Innovation Center - joining the PING call to go over Geolocation WG
16:06:45 <npdoty> scribenick: npdoty
16:06:46 <tara> Tara Whalen, co-chair of PING, Privacy Engineer at Apple.
16:06:48 <fjh> Frederick Hirsch, Nokia, Chair DAP
16:07:02 <npdoty> scribenick: JoeHallCDT
16:07:02 <tara> Thanks!
16:07:10 <Ryladog> Hi, I am Katie Haritos-Shea on IndieUI
16:07:11 <yrlesru> zakim, this will be aaaa
16:07:11 <Zakim> I do not see a conference matching that name scheduled within the next hour, yrlesru
16:07:13 <JoeHallCDT> done
16:07:36 <npdoty> Zakim, aaaa is yrlesru
16:07:36 <Zakim> sorry, npdoty, I do not recognize a party named 'aaaa'
16:07:38 <christine> Agenda item 2 - Geolocation WG
16:07:39 <yrlesru> zakim, this will be aacc
16:07:39 <Zakim> I do not see a conference matching that name scheduled within the next hour, yrlesru
16:07:46 <npdoty> Zakim, who is making noise?
16:07:46 <Zakim> sorry, npdoty, I don't know what conference this is
16:07:54 <npdoty> Zakim, this is 7464
16:07:54 <Zakim> ok, npdoty; that matches Team_(privacy)16:00Z
16:07:58 <npdoty> Zakim, who is making noise?
16:08:10 <Zakim> npdoty, listening for 10 seconds I heard sound from the following: gmandyam (64%), +1.214.566.aacc (40%)
16:08:12 <christine> Giri, we cannot understand you
16:08:22 <christine> Thanks, better
16:08:24 <tara> Much better, thanks.
16:08:49 <JoeHallCDT> discussing slide 2
16:08:52 <terri> Terri Oda, Security Researcher at Intel Open Source Technology Center
16:09:04 <JoeHallCDT> Giri: geoloc WG one of the first device API WGs
16:09:08 <christine> slides - http://lists.w3.org/Archives/Public/public-privacy/2014AprJun/att-0012/Geolocation_WG_Status_for_PING_May_29_2014.pdf
16:09:14 <JoeHallCDT> … specifically for mobile devices in mind
16:09:22 <JoeHallCDT> … level 1 spec is the geoloc api
16:09:28 <JoeHallCDT> … other level is  device orientation
16:09:43 <JoeHallCDT> … gyroscope, when the device is in motion, direction it's moving in cartesian coords
16:09:51 <JoeHallCDT> … both apis proved to be very popular
16:10:04 <JoeHallCDT> … have been interop. issues but lots of vendor take-up
16:10:26 <JoeHallCDT> … under the previous charter, attempt for level 2 api
16:10:40 <JoeHallCDT> … main feature reverse geocoding… lat/lon of address
16:10:44 <JoeHallCDT> … not developer interest
16:10:49 <JoeHallCDT> … spec shelved before last call
16:11:21 <JoeHallCDT> … Qualcomm Innov. Cntr. does a lot of the mobile chip geoloc stuff
16:11:40 <JoeHallCDT> … certainly are privacy concerns
16:11:44 <jcraig> s/spec shelved/reverse address lookup feature was shelved/
16:11:56 <JoeHallCDT> … safety issue, e.g., children exposing their home address
16:12:04 <JoeHallCDT> … legal issue, govt. tracking location
16:12:31 <JoeHallCDT> … not just a US issue given legal developments, but an issue in repressive nations
16:12:55 <JoeHallCDT> … recognized problem with the limited ability for users to control geoloc information through browser api
16:13:19 <JoeHallCDT> … users may not have a clue which sites they've given long-term access to geoloc. API
16:13:35 <JoeHallCDT> it's also an issue in WebRTC with permissions I believe
16:13:40 <npdoty> +1, not unique to Geolocation! persistence and revocation of permissions is a challenge
16:13:40 <JoeHallCDT> that was just me, not as scribe
16:14:07 <JoeHallCDT> … doesn't seem like the w3c has a uniform answer across WGs for this
16:14:17 <JoeHallCDT> … questions?
16:14:20 <JoeHallCDT> … none.
16:14:27 <JoeHallCDT> … slide 4 (slides are not numbered)
16:15:12 <jcraig> Slide #5 content:
16:15:13 <jcraig> New Geolocation Working Group Charter
16:15:16 <JoeHallCDT> … slide 5, "New Geoloc WG Charter"
16:15:22 <jcraig> Two main work items
16:15:23 <jcraig> – Adding geofencing to Geolocation API
16:15:25 <jcraig> • Leverage HW-based geofencing (as opposed to JS- based geofencing, which is possible with existing API)
16:15:26 <jcraig> – Cleaning up DeviceOrientation specification
16:15:28 <jcraig> • First version of spec resulted in poor interoperability
16:15:29 <jcraig> between different browser implementations
16:15:30 <JoeHallCDT> … Qualcomm has impliemented low-power geofencing
16:15:31 <jcraig> • In addition, development of use cases and requirements for indoor location extensions to API
16:15:32 <jcraig> Geofencing: Sample Use Cases
16:15:34 <jcraig> • Alerts when points of interest are in the user's vicinity
16:15:35 <jcraig> • Asset tracking
16:15:36 <jcraig> • Mobile marketing
16:15:37 <jcraig> – Advertisements related to geographical context
16:16:13 <jcraig> (That's actually Slides #5 and #6)
16:16:21 <JoeHallCDT> … there were problems with browser implementations of DeviceOrientation
16:16:33 <JoeHallCDT> … want to extend to indoor location extensions
16:16:47 <JoeHallCDT> q
16:16:50 <JoeHallCDT> q+
16:17:22 <JoeHallCDT> … this can specialize information to a specific location in a building (floors, etc.)
16:17:29 <JoeHallCDT> … didn't want this to be explicit in the charter
16:17:58 <JoeHallCDT> … issues with multiplatform support for that
16:18:19 <JoeHallCDT> … geofencing: alerts when points of interest are near
16:18:40 <JoeHallCDT> … asset tracking: where is your stuff?
16:19:34 <JoeHallCDT> … mobile marketing… ads based on geography and presence
16:20:14 <JoeHallCDT> … slide 7: references on identified issues wrt privacy in existing API
16:20:36 <npdoty> q+ to ask about civic address
16:21:03 <jcraig> q+ to ask about exposing geoloc justification to users
16:21:13 <npdoty> JoeHallCDT: what is the technology used to do indoor location? beacons, access points, etc.?
16:21:17 <jcraig> ack jo
16:21:33 <JoeHallCDT> q-
16:21:39 <JoeHallCDT> q+
16:21:49 <jcraig> BLE: Bluetooth Low Energy
16:21:50 <npdoty> giri: depends on the technology, we do use bluetooth beacons
16:21:54 <JoeHallCDT> … q: how does the indoor loc mojo work?
16:22:14 <JoeHallCDT> … wifi AP analytics, also beacons can be used
16:22:55 <JoeHallCDT> npdoty: follow up about the address thing
16:23:01 <jcraig> ack np
16:23:01 <Zakim> npdoty, you wanted to ask about civic address
16:23:06 <JoeHallCDT> … remember a petition to drop a v2, reverse geocoding
16:23:31 <christine> (Has the sound dropped, or aonly for me?)
16:23:35 <JoeHallCDT> … are there opportunities to provide less precise information with less UI stuff?
16:23:43 <JoeHallCDT> only for you CR
16:23:49 <Hannes_Tschofenig> I hear the sound quite well
16:23:56 <christine> Now okay
16:24:05 <JoeHallCDT> Giri: there is a flag, when set to false, allows the API to work on crude location
16:24:19 <npdoty> enableHighAccuracy flag
16:25:04 <JoeHallCDT> … might be difficult to get into a mobile browser
16:25:19 <JoeHallCDT> … as to second part of the question, have thought about it as a performance issue.
16:25:23 <jcraig> ack me
16:25:23 <Zakim> jcraig, you wanted to ask about exposing geoloc justification to users
16:25:25 <JoeHallCDT> ack joe
16:25:29 <Hannes_Tschofenig> I have a question as well about the relationship to the work in the IETF.
16:25:40 <npdoty> q+ hannes
16:25:56 <JoeHallCDT> jcraig: there is a related feature missing from the geoloc api
16:26:11 <JoeHallCDT> … i.e., an informal justification to the user as to why and app/site wants geoloc
16:26:31 <JoeHallCDT> … it is not always entirely obvious why a thing wants access to geoloc
16:26:38 <Hannes_Tschofenig> +1 That's sounds like a useful feature to me!
16:26:44 <JoeHallCDT> … this could be very useful
16:27:03 <npdoty> +1, I raised that back during v1
16:27:37 <Hannes_Tschofenig> I bet that they do not add such functionality
16:27:43 <JoeHallCDT> Giri: we reference a report from Berkeley that calls out this as a shortcoming
16:27:59 <JoeHallCDT> … how do you deliver this in a generic cross-WG manner
16:28:10 <JoeHallCDT> … e.g., WebRTC with browser-to-browser comms.
16:28:20 <Hannes_Tschofenig> I think that this is called "the race to the bottom".
16:28:21 <npdoty> the pushback heard then (and heard generally) is that the notification string could be fraudulent or misleading
16:28:22 <JoeHallCDT> … how do these video and audio streams stay with an intended recipient
16:28:37 <JoeHallCDT> or overloaded with legalese for secondary uses
16:28:39 <npdoty> I totally agree it would be good to give general guidance, since every WG is facing that question
16:28:46 <JoeHallCDT> jcraig: this could be optional
16:28:53 <JoeHallCDT> … some websites would like to us it.
16:29:08 <JoeHallCDT> gmandyam: good advice
16:29:11 <npdoty> s/us it/use it/
16:29:14 <jcraig> q?
16:29:24 <jcraig> ack ha
16:29:49 <JoeHallCDT> Hannes_Tschofenig: some of this is very similar to what we've standardized at IETF
16:30:04 <JoeHallCDT> … e.g. relative location is useful in a building
16:30:32 <JoeHallCDT> … also looked at privacy protections, wondering if you've looked at that
16:30:39 <npdoty> yeah, more precise indoor location might be a good reason to look at IETF's pidlo location object, as opposed to just a set of address fields
16:31:06 <JoeHallCDT> gmandyam: We've looked at the GeoPriv object… we're part of (some industry group Joe hasn't heard of)
16:31:15 <npdoty> http://www.in-location-alliance.com/en/about
16:31:52 <JoeHallCDT> … we have to in some sense get certain OS support to extend these features into the browser
16:32:27 <JoeHallCDT> … if we can't get two browsers to do something, it's difficult to justify work to do this
16:33:04 <JoeHallCDT> Christine: thank you very much, excellent intro to the re-chartered WG
16:33:15 <JoeHallCDT> … please keep us apraised of what you're doing
16:33:19 <npdoty> +1, thanks gmandyam!
16:33:37 <npdoty> Topic: IndieUI
16:34:19 <jcraig> Janina
16:34:30 <gmandyam> Thanks to PING for inviting me.  Thanks for all the good questions.  I unfortunately I have sign off now. - Giri
16:34:40 <christine> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html
16:34:48 <JoeHallCDT> janina: IndueUI WG is looking for advice from PING
16:35:04 <JoeHallCDT> … servers can do a better job for tailoring content to users if users can better specify something
16:35:13 <christine> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#privacy-model
16:35:28 <Zakim> -gmandyam
16:35:54 <JoeHallCDT> … the user is communicating preferences and this effort would tailor content to the user according to those prefs
16:36:12 <JoeHallCDT> … discloses possibly who this is and their preferences
16:36:16 <jcraig> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#privacy-model
16:37:07 <JoeHallCDT> … some of these settings are available… but not in a standard way
16:37:51 <JoeHallCDT> … caption styling is a big use case
16:38:33 <JoeHallCDT> … this spec has a justification string (like that just discussed for Geoloc)
16:38:54 <JoeHallCDT> … optional in some cases, required in some high-security preferences
16:39:05 <JoeHallCDT> q+ high-security preference example?
16:39:35 <JoeHallCDT> q+ to ask about high-security preferences
16:40:39 <JoeHallCDT> … media settings, like closed-caption styling, are probably not high-security preferences
16:42:07 <JoeHallCDT> … high-security preferences are ones where a user may want to trust certain sites with that info. and not others
16:42:08 <npdoty> is curious about the accessibility restrictions for Google Docs, though I'll look into that offline
16:42:21 <JoeHallCDT> … we aim to publish first draft of user preferences doc in late June
16:42:26 <christine> q?
16:42:39 <JoeHallCDT> ack
16:42:40 <jcraig> ack jo
16:42:40 <Zakim> JoeHallCDT, you wanted to ask about high-security preferences
16:42:41 <npdoty> I think the idea was that screenreader-in-use would likely to be higher privacy because it wouldn't generally needed and might be very sensitive
16:43:44 <christine> q+
16:43:52 <npdoty> q+
16:44:16 <jcraig> q+ to discuss fingerprinting
16:44:31 <JoeHallCDT> npdoty: some things, captions, are things that can be done on the client side
16:44:43 <JoeHallCDT> … the server may not need to participate in this
16:44:55 <npdoty> q-
16:44:56 <JoeHallCDT> … have we thought about which of these cases need to have the server knowing prefs?
16:45:07 <JoeHallCDT> jcraig: all is happening on client-side, so up to web applications
16:45:07 <hober> hober has joined #privacy
16:45:21 <jcraig> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#userMediaSettings
16:45:24 <npdoty> (was unprecise in describing "server" when web app JavaScript is also a case)
16:45:29 <jcraig> 5.3.1 Key: subtitles
16:45:30 <jcraig> Web authors using a native video player should allow subtitles to be displayed natively. Web authors using a custom subtitle view should display the custom-rendered subtitles based on this setting.
16:45:30 <hober> Zakim, who is on the phone?
16:45:30 <Zakim> On the phone I see christine, tara, hober, Katie_Haritos-Shea, [Apple], janina, WSeltzer, Michael_Cooper_(IndieUI), [CDT], +44.793.550.aabb, npdoty, terri (muted), fjh,
16:45:33 <Zakim> ... +1.214.566.aacc
16:45:33 <Zakim> [Apple] has jcraig
16:45:33 <JoeHallCDT> … the use case npdoty talks about is only when you use an HTML5 <video> which is not always possible
16:45:58 <npdoty> another reason to switch to HTML5 video!
16:47:04 <npdoty> q-
16:47:33 <christine> q-
16:47:41 <JoeHallCDT> Christine: want to hand it over to james to talk about how he's dealt with tracking and fingerprinting
16:48:06 <npdoty> I guess I think we should be careful about what a11y features we add for native/plugins, rather than noting those as bugs with the HTML features
16:48:29 <JoeHallCDT> jcraig: please read Section 4 of the draft linked about about the privacy model
16:49:28 <JoeHallCDT> … we don't restrict access to things that are already figure-out-able
16:49:44 <JoeHallCDT> … we've talked about solutions for more high-security prefs
16:49:49 <JoeHallCDT> … https, restrictions, etc.
16:50:18 <JoeHallCDT> … this is why we want to put certain things, like assistive tech, behind a prompt
16:50:26 <christine> q?
16:50:28 <jcraig> ack me
16:50:28 <Zakim> jcraig, you wanted to discuss fingerprinting
16:50:51 <JoeHallCDT> npdoty: we are trying to get common guidance on fingerprinting
16:51:20 <JoeHallCDT> … it is good to consider what things are likely to be useful for fingerprinting
16:51:27 <JoeHallCDT> … rather than (something I missed)
16:51:41 <npdoty> don't particularly see HTTPS as more important than usual here
16:51:53 <npdoty> and observability can be useful regarding fingerprinting as well
16:52:00 <npdoty> and we should follow up over email as well :)
16:52:49 <JoeHallCDT> Christine: thanks them for being so careful about privacy
16:53:31 <JoeHallCDT> Katie: are you hoping that any interaction that involves fingerprinting should be behind https?
16:53:46 <npdoty> I don't think FPWD needs to wait on our group; a first draft is a great thing to get out there, and can get good feedback (including on privacy)
16:53:47 <JoeHallCDT> me: don't get it, https doesn't protect things from the other end!
16:54:18 <JoeHallCDT> … the thinking behind https, just in case the web app wants to store some prefs on the server, they'd have to send via https
16:54:37 <JoeHallCDT> … barrier to entry to using https
16:54:50 <JoeHallCDT> … could be a barrier to uptake of the API
16:54:59 <npdoty> hopes blog sites will be using HTTPS, and that it'll be easy for them to do so
16:55:10 <JoeHallCDT> yes!
16:55:31 <Zakim> -Michael_Cooper_(IndieUI)
16:55:36 <JoeHallCDT> Christine: TPAC
16:55:43 <Zakim> -janina
16:55:46 <janina> janina has left #privacy
16:55:46 <npdoty> Topic: TPAC
16:55:46 <JoeHallCDT> … how can we useful use the time we will have at TPAC?
16:55:49 <Zakim> -Katie_Haritos-Shea
16:55:57 <jcraig> Thank you all. Dropping off the call. I'll remain on IRC.
16:56:04 <Zakim> -[Apple]
16:56:06 <npdoty> Topic: Guidance
16:56:07 <JoeHallCDT> Topic: Privacy Considerations Document
16:56:16 <jcraig> zakim, who is on the phone?
16:56:16 <Zakim> On the phone I see christine, tara, hober, WSeltzer, [CDT], +44.793.550.aabb, npdoty, terri (muted), fjh, +1.214.566.aacc
16:56:27 <JoeHallCDT> Christine: npdoty has sent comments, Joe plans to, Christine is in planning stages to plan to
16:56:41 <npdoty> present+ Hannes_Tschofenig
16:56:43 <JoeHallCDT> … let's have an informal task force to work on this document?
16:56:46 <npdoty> present+ yrlesru
16:56:56 <JoeHallCDT> … suggesting hannes, joe, nick, and Christine
16:56:58 <Zakim> -hober
16:57:04 <JoeHallCDT> love it. agreed.
16:57:15 <JoeHallCDT> hannes: read through Nick's review...
16:57:25 <JoeHallCDT> … can definitely make some changes based on that
16:57:40 <JoeHallCDT> … put it in w3c github, maybe npdoty can do that
16:57:48 <npdoty> action: doty to move Privacy Cons. doc to w3c github organization
16:57:48 <trackbot> Created ACTION-6 - Move privacy cons. doc to w3c github organization [on Nick Doty - due 2014-06-05].
16:57:53 <JoeHallCDT> Christine: pretty please, get that going
16:58:10 <npdoty> Nick has taken an action item. :)
16:58:36 <JoeHallCDT> hannes: there are still a few process-related items in that document
16:58:56 <JoeHallCDT> … want to consolidate and pull that out
16:59:09 <npdoty> yrlesru/Frank has been handling process stuff in the Specification Privacy Assessment document
16:59:51 <JoeHallCDT> yrleru: also, we had an informal meeting about this in March at CDT, Joe sent an email
17:00:09 <JoeHallCDT> … we identified some deep issues: if you do privacy considerations after chartering, hard to get that back in
17:00:25 <JoeHallCDT> … need to think about potential footprint of privacy and security in chartering
17:00:49 <JoeHallCDT> me: this speaks to more changes across w3c process than simply advice to WGs and chairs
17:00:57 <JoeHallCDT> … not sure how to process that
17:01:06 <JoeHallCDT> … Joe may have some good idea
17:01:13 <npdoty> hmm... that was earlier than I was imagining, but I'd be happy to discuss how we can do better at noting things during charter process
17:01:34 <JoeHallCDT> yes, this is part of the conversation and I hope part of this nascent task force
17:01:46 <yrlesru> Sure!
17:01:49 <JoeHallCDT> they can't be the same thing
17:01:50 <JoeHallCDT> ?
17:01:50 <npdoty> are people going to be in DC in June for PLSC?
17:01:53 <JoeHallCDT> I am!
17:01:55 <tara> I am !
17:01:58 <npdoty> I am!
17:01:59 <npdoty> q+
17:02:19 <npdoty> http://www.w3.org/blog/TAG/2014/05/22/capability-urls-feedback/
17:02:20 <JoeHallCDT> npdoty: three things PING might want to be aware of:
17:02:35 <npdoty> http://www.w3.org/TR/capability-urls/
17:02:46 <JoeHallCDT> … 1) capability URLs, the TAG has been working on this document and best practices… very much a privacy use case
17:02:49 <JoeHallCDT> … asking for feedback
17:03:09 <JoeHallCDT> … 2) Do Not Track work is in Last Call… part of it, at least
17:03:10 <npdoty> http://www.w3.org/TR/tracking-dnt/
17:03:31 <JoeHallCDT> … TPE is in last call (this is the technical signal) June 18
17:03:44 <JoeHallCDT> … 3) Web Security Group is looking into some process for reviews
17:04:05 <wseltzer> Please review; http://www.w3.org/Security/wiki/IG/W3C_spec_review
17:04:17 <JoeHallCDT> neat!
17:04:35 <wseltzer> s/Please review:/Web Security IG is looking for review of guidelines,/
17:04:40 <JoeHallCDT> Christine: how is 26 June?
17:04:55 <JoeHallCDT> wfm
17:05:16 <tara> Looks good so far...
17:05:26 <Zakim> -christine
17:05:29 <npdoty> the Web Security Interest Group review process might be particularly relevant if we want to coordinate with a privacy review, which I think is generally a good idea
17:05:36 <JoeHallCDT> ok, we lost Christine
17:05:51 <yrlesru> Bye folks!
17:06:06 <JoeHallCDT> woo!
17:06:07 <Zakim> -fjh
17:06:08 <JoeHallCDT> JoeHallCDT has left #privacy
17:06:12 <Zakim> -npdoty
17:06:12 <Zakim> -[CDT]
17:06:13 <npdoty> [adjourned]
17:06:17 <Zakim> -tara
17:06:18 <npdoty> trackbot, end meeting
17:06:18 <trackbot> Zakim, list attendees
17:06:19 <Zakim> As of this point the attendees have been tara, hober, Katie_Haritos-Shea, gmandyam, +1.214.566.aaaa, WSeltzer, [CDT], +44.793.550.aabb, npdoty, terri, Michael_Cooper_(IndieUI),
17:06:19 <Zakim> ... fjh, jcraig, janina, christine, +1.214.566.aacc
17:06:21 <Zakim> - +44.793.550.aabb
17:06:23 <Zakim> - +1.214.566.aacc
17:06:26 <trackbot> RRSAgent, please draft minutes
17:06:26 <RRSAgent> I have made the request to generate http://www.w3.org/2014/05/29-privacy-minutes.html trackbot
17:06:27 <trackbot> RRSAgent, bye
17:06:27 <RRSAgent> I see 1 open action item saved in http://www.w3.org/2014/05/29-privacy-actions.rdf :
17:06:27 <RRSAgent> ACTION: doty to move Privacy Cons. doc to w3c github organization [1]
17:06:27 <RRSAgent>   recorded in http://www.w3.org/2014/05/29-privacy-irc#T16-57-48
17:07:37 <RRSAgent> RRSAgent has joined #privacy
17:07:37 <RRSAgent> logging to http://www.w3.org/2014/05/29-privacy-irc
17:07:43 <npdoty> rrsagent, please draft minutes
17:07:43 <RRSAgent> I have made the request to generate http://www.w3.org/2014/05/29-privacy-minutes.html npdoty
17:08:04 <npdoty> RRSAgent, bye
17:08:11 <npdoty> rrsagent, make logs public
17:08:13 <npdoty> rrsagent, bye
17:08:13 <RRSAgent> I see no action items