12:13:54 RRSAgent has joined #swxg 12:13:54 logging to http://www.w3.org/2009/09/02-swxg-irc 12:44:40 AndreaP has joined #swxg 12:44:49 zakim, code 12:44:49 I don't understand 'code', AndreaP 12:44:52 zakim, code? 12:44:52 the conference code is 7994 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), AndreaP 12:49:14 danbri has joined #swxg 12:50:31 hi folks 12:50:32 DKA has joined #swxg 12:50:40 rreck has joined #SWXG 12:50:43 i might be irc only today i'm afraid (drupalcon multitasking) 12:52:15 hhalpin did you send out minutes to approve? 12:56:02 INC_SWXG()9:00AM has now started 12:56:08 + +95177aaaa 12:57:06 bblfish has joined #swxg 12:57:11 +??P17 12:57:22 zakim, ??P17 is me 12:57:22 +rreck; got it 12:57:55 low voter turnout 12:58:07 pchampin has joined #swxg 12:58:17 tinkster has joined #swxg 12:58:22 +??P18 12:58:44 zakim, ??P18 is me 12:58:44 +melvster; got it 12:58:47 zakim, who's here? 12:58:47 On the phone I see +95177aaaa, rreck, melvster 12:58:48 On IRC I see tinkster, pchampin, bblfish, rreck, DKA, danbri, AndreaP, RRSAgent, melvster, hhalpin, FabGandon, caribou, karl, Zakim, trackbot 12:59:07 +tinkster 12:59:29 Yuk has joined #swxg 13:00:02 looks like the past minutes are not posted yet? 13:00:45 it is :) 13:01:15 zakim, what is the code? 13:01:15 the conference code is 7994 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), DKA 13:01:24 +adam 13:01:38 zakim, who is adam 13:01:38 I don't understand 'who is adam', DKA 13:01:52 looks like the webpage links to minutes are wrong, many link to jul 22 13:01:53 zakim, adam is DKA 13:01:53 +DKA; got it 13:02:20 the last minutes I recieved are http://www.w3.org/2009/08/19-swxg-minutes.html 13:02:27 and the link works 13:02:38 AlexPassant has joined #swxg 13:02:49 + +1.314.683.aabb 13:03:04 oshani has joined #swxg 13:03:06 +??P31 13:03:08 http://www.w3.org/2009/07/29-swxg-minutes.html 13:03:12 +bblfish 13:03:13 Adam has joined #swxg 13:03:16 +??P32 13:03:20 +caribou 13:03:22 Zakim, ??P32 is me 13:03:26 +AlexPassant; got it 13:03:29 zakim, who is here? 13:03:32 On the phone I see pchampin, rreck, melvster, tinkster, DKA, +1.314.683.aabb, ??P31, bblfish, AlexPassant, caribou 13:03:38 Zakim, ??P31 is hhalpin 13:03:41 On IRC I see Adam, AlexPassant, Yuk, tinkster, pchampin, bblfish, rreck, DKA, danbri, AndreaP, RRSAgent, melvster, hhalpin, FabGandon, caribou, karl, Zakim, trackbot 13:03:45 links to agenda, etc should be OK here - http://www.w3.org/2005/Incubator/socialweb/wiki/Telecons 13:03:46 +hhalpin; got it 13:03:50 Last meeting minutes are linked from agenda 13:04:08 zakim, aabb is me 13:04:08 +Adam; got it 13:04:10 http://www.w3.org/2009/07/29-swxg-minutes.html 13:04:31 you mean victim 13:04:51 oshani has joined #swxg 13:04:52 I don't mind if nobody else wants to. 13:04:56 +??P2 13:05:02 zakim, ??p2 is me 13:05:02 +AndreaP; got it 13:05:06 +1 tinkster 13:05:07 ScribeNick: tinkster 13:05:15 Scribe: Toby 13:05:36 -bblfish 13:05:40 i saw dan perform some incantation 13:05:40 zakim, what meeting is this? 13:05:40 I don't understand your question, DKA. 13:05:44 jsalvachua has joined #swxg 13:05:49 zakim, this is SWXG 13:05:49 caribou, this was already INC_SWXG()9:00AM 13:05:50 ok, caribou; that matches INC_SWXG()9:00AM 13:06:29 Agenda: http://www.w3.org/2005/Incubator/socialweb/weekly-agenda.html 13:06:35 +bblfish 13:06:42 DKA: Let's kick off. First item on our agenda is (as usual) to review last week's minutes. 13:06:42 hi 13:06:43 Zakim, agenda+ Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z 13:06:43 agendum 5 added 13:06:53 + +34.91.549.aacc 13:07:03 zakim, aacc is me 13:07:03 +jsalvachua; got it 13:07:13 http://www.w3.org/2009/08/26-swxg-minutes.html 13:07:31 Zakim, what's the agenda? 13:07:31 I see 2 items remaining on the agenda: 13:07:32 4. DanBri on WebFinger [from hhalpin] 13:07:34 5. Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z [from hhalpin] 13:07:39 oshani has joined #swxg 13:07:47 didn't we do webfinger last week? 13:07:56 +1 approve minutes 13:08:04 Zakim, agenda- 4 13:08:04 agendum 4, DanBri on WebFinger, dropped 13:08:04 ie. http://www.w3.org/2009/08/26-swxg-minutes.html#item05 13:08:18 yes, I understood sparql webfinger right after the end of the conf 13:08:27 ... Any objections to approving last week's minutes? 13:08:51 +1 meet again 13:09:10 Zakim, agenda+ General Organization and Task Forces 13:09:10 agendum 6 added 13:09:18 Zakim, next agendum 13:09:18 agendum 5. "Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z" taken up [from hhalpin] 13:09:20 ... Moving swiftly on: general organisations. Still not completed my action on OSLO/geolocation 13:09:38 http://www.w3.org/2002/09/wbs/43434/USECASES/results 13:09:42 ... Focus today on discussing use cases and results of poll. Move onto that? 13:09:46 Zakim, agenda+ User stories 13:09:46 agendum 7 added 13:09:56 Zakim, next agendum 13:09:56 agendum 5 was just opened, hhalpin 13:09:58 +MIT-G631 13:10:01 Harry: that sounds fine. 13:10:13 http://www.w3.org/2002/09/wbs/43434/USECASES/results 13:10:21 Zakim, open agendum 6 13:10:21 agendum 6. "General Organization and Task Forces" taken up [from hhalpin] 13:10:31 Zakim, close this agendum 13:10:31 agendum 6 closed 13:10:32 I see 2 items remaining on the agenda; the next one is 13:10:33 5. Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z [from hhalpin] 13:10:38 Zakim, open agendum 7 13:10:38 agendum 7. "User stories" taken up [from hhalpin] 13:10:58 zakim, who's making noise? 13:11:09 tinkster, listening for 10 seconds I heard sound from the following: 13 (36%) 13:11:15 http://www.w3.org/2002/09/wbs/43434/USECASES/results 13:11:48 Harry: Most productive to continue from last meeting, walking through use cases. 13:12:00 http://www.w3.org/2002/09/wbs/43434/USECASES/results?view=compact 13:12:58 ... Most use cases have a champion. Some can clearly be dropped - bidirectional; drag and drop; etc. Some have almost unanimous support. Some more mixed. 13:13:26 Zakim, who's making noise? 13:13:39 hhalpin, listening for 10 seconds I heard sound from the following: DKA (95%), hhalpin (11%) 13:13:42 MacTed has joined #swxg 13:13:52 DKA: CRUS is on a much lower level than the others; can't really be argued against. 13:13:58 s/CRUS/CRUD/ 13:14:14 +OpenLink_Software 13:14:24 Harry: Last time we got up to "Adding new features to Social Networks" case. 13:14:29 http://www.w3.org/2002/09/wbs/43434/USECASES/results#xq6 13:14:31 Zakim, mute OpenLink_Software 13:14:31 OpenLink_Software should now be muted 13:14:43 Zakim, OpenLink_Software is temporarily me 13:14:43 +MacTed; got it 13:14:44 Developers should be able to expose existing data in new and interesting ways. But at the same time, people should be made aware of how their data is being used, and updated when this changes 13:14:44 ... To me this is talking mostly about widgets. 13:15:01 +??P36 13:15:17 Maybe we should separate those out 13:15:21 DKA: There's widgets as in browser-widgets, but also those that live on the page, and APIs, etc. This encompasses both of those aspects. 13:15:21 ? 13:15:30 Harry: should separate out? 13:15:32 ??P36 is me 13:15:43 DKA: Not so sure they should be separate. They seem related. 13:15:45 q? 13:15:45 The issue with this usecase is needs a champion 13:16:21 i think there should be an opt in policy about newly added functionality 13:16:26 beuler 13:16:27 I'll champion this one if no one wants to 13:16:28 hhalpin: Anyone want to champion it? 13:16:55 DKA: yay for melvster championing. 13:17:31 To find the original source of a meme or piece of information. 13:17:33 hhalpin: Tracking of sources use case. We want to find the original source of the information. 13:17:52 tinkster: am happy to champion this use case. 13:18:25 i just disagree with christine 13:18:38 hhalpin: Multiple identities / anonymous identities - merge? 13:18:58 To provide information without being the attributed source or “whistle blower”. 13:19:01 Anonymous information usecase 13:19:27 Provenance is effectivelzy blocked or unknown, i.e. anonymous, or anonymous identity. 13:19:29 q+ 13:19:31 hhalpin: this could also be considered to be merged with source tracking / provenance. 13:19:35 yeah provenance is an anonymous node 13:19:48 DKA: curious to understand the argument against. 13:20:32 i want to share it, just not have it attributed to me 13:20:43 oshani: there could be a set of people you are comfortable with sharing information; other people not so much; so have two identities - a real one and a pseudononymous one. 13:20:50 anonymous could also be wikileaks-style, i.e. truly anonymous 13:20:51 ack me 13:21:18 DKA: Not sure this answers the whistleblower use case completely anonymously. 13:21:34 this can be accomplished technically via messages sent out over mixminion for example 13:22:24 yeah someone on my street put up a sign saying the water wasnt safe. im sure it made him a target 13:22:31 q? 13:22:31 DKA: Whistleblower use case more interesting if we look at it from a gov't agency point of view. 13:22:35 ack osch 13:22:40 what is the problem with having identifiers for people with no info linked to that person? 13:22:48 s/person/id/ 13:22:58 then you get id, and anonymity 13:23:08 +1 bblfish 13:23:13 hhalpin: if rreck wants to champion it, we should keep it around, but note its links to related use cases. 13:23:21 +1 bblfish 13:23:24 I think if Ronald wants to champion if Ronald making sure its suitable, especially if we can track back to merging source... 13:24:08 oshani: From a social net point of view, what does this encompass? How does it relate to e.g. Webcams. 13:24:16 i want to protect my friends from something, but i dont want it tracked to me 13:24:18 lkagal has joined #swxg 13:24:44 hhalpin: there exists technical infrastructure that can provide pretty good anonymity. 13:25:02 i think its null provenance 13:25:32 ill talk to oshani offline 13:25:47 hhalpin: should champions be rewriting use cases, cleaning up, fleshing out? 13:25:50 DKA: yes/ 13:25:54 +1 13:26:00 ACTION: rreck to flesh out anonymous usecase connecting to multiple identies and null provenance 13:26:00 Created ACTION-71 - Flesh out anonymous usecase connecting to multiple identies and null provenance [on Ronald Reck - due 2009-09-09]. 13:26:29 "Removing Data or Changing Data permission" Use-case 13:26:53 hhalpin: next use case is removing data / changing permissions use case. Most people not in favour of keeping. Perhaps use case is too abstract? 13:27:13 there really is not much text at http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Removing_Data_or_Changing_Data_permission 13:27:22 ... relates to the more concrete 10 year and takedown cases. 13:27:36 ... Merge these three use cases? 13:27:42 Document Takedowns Propagators" Use-case 13:27:46 are all of them really related to the life cycle management of data? 13:27:56 DKA: Seems sensible to me. 13:28:22 i think all this case could be solved with obligatory metadata stating time to life 13:28:38 hhalpin: 10 year use case had a lot of support, no champion. Would oshani like to incorporate this into document takedown? 13:28:43 oshani: yes, I can do that. 13:28:51 q+ 13:29:00 hhalpin: 10 years is just a time-related document takedown. 13:29:23 ack bbl 13:29:38 bblfish: if you do everything by reference (rather than by copying) then you only need to take down the original. 13:29:49 ACTION: Oshani to merge document takedown with time-related takedown "forget this in ten years" and more general concept of data removal. 13:29:50 Created ACTION-72 - Merge document takedown with time-related takedown "forget this in ten years" and more general concept of data removal. [on Oshani Seneviratne - due 2009-09-09]. 13:30:50 DKA: example is a photo that I've taken, which includes bblfish's face, and bblfish annotates it. Someone else in the photo asked DKA to take down the photo. 13:31:18 ... DKA should be able to remove photo. What happens to annotation? What is bblfish's right to the image vs DKA's right? 13:31:27 DKA's example happened to me 13:31:28 bblfish: it's complicated - that's true. 13:31:51 "Last Will" usecase 13:31:52 hhalpin: last will and testament use case. 13:31:56 time to life for information 13:32:01 obligatory metadata 13:32:03 ... very popular, but lacking a champion. 13:32:28 ... perhaps should be merged with takedowns? but it's a very special case. 13:32:33 i will champion that but solve it with obligatory metadata 13:32:35 everybody's gonna... :-) 13:32:44 DKA: this is something we'll all end up facing! 13:32:50 Zakim, unmute me 13:32:50 MacTed should no longer be muted 13:32:55 +q 13:33:13 ... worth keeping on its own. volunteer champion? 13:33:17 Ron? 13:33:39 ack rr 13:33:40 zakim, who's making noise? 13:33:51 tinkster, listening for 10 seconds I heard sound from the following: hhalpin (5%), MacTed (60%) 13:34:17 MacTed: this could be solved by including a time-to-live (TTL) for every piece of content. 13:34:20 is an option on time-to-life? 13:34:39 yes, but it is weird. I think that removing information is problematic. 13:34:39 everyone: "if you know the exact time of your death". 13:34:51 MacTed: copyright is based on death date. 13:35:13 it also happens that one's parents/friends want to see his/her history 13:35:14 tinkster: it's based on the author's death date, but calculated *after* death. (currently) 13:36:09 Ah, so MacTed above is rreck. (Note to editor!) 13:36:24 (Or maybe not?) 13:36:30 Hmmm...it seems like what we need to do next is move to group permissions 13:36:44 is some of that regarding permissions of access versus time of life? 13:36:49 Someone: TTL could be fragmented by different groups. 13:37:07 that is an awesome point, its much more complicated than i had appreciated 13:37:15 s/Someone/MacTed 13:37:36 unix like permissions? 13:37:52 DKA: Death use case needs a champion, even if nobody wants to be the "champion of death". 13:38:00 ... I'd be happy to take it on myself. 13:38:32 one of my FB passed, and i wondered what will happen to his page 13:38:50 ACTION: DKA to take on "Last Will and Testament Usecase", referencing it as both a legal issue and with regards document takedown 13:38:50 Created ACTION-73 - Take on "Last Will and Testament Usecase", referencing it as both a legal issue and with regards document takedown [on Daniel Appelquist - due 2009-09-09]. 13:38:51 Zakim, mute me 13:38:51 MacTed should now be muted 13:38:56 ... What happens right now on social networks when people die? What happens if someone is believed dead, their account deleted, and it turns out they're alive? 13:39:16 (de-lurking) 13:39:19 mostly someone finds their username/password, and assumes ownership of the account ... 13:39:24 tinkster: there exist facebook memorial pages (I'm told) 13:39:29 i'd like to spend some time chasing up this issue, seems a useful kind of thing for w3c to investigate 13:39:50 if that doesn't happen, most accounts I've known have just sat there untouched (sometimes years) like any other inactive 13:40:04 hhalpin: multiple identities use case. champion bblfish? 13:40:06 "Multiple Identities" Use-case 13:40:36 Social network for the dead Respectance crosses the ocean http://thenextweb.com/2008/10/03/social-network-for-the-death-respectance-crosses-the-ocean/ 13:40:37 Sort of built from multiple identities over multiple networks to metadata about the management of data over multiple networks to access control. 13:40:49 ... Maybe this could be the starting point for other use cases. 13:41:01 demerits for me, I found no window to review/restructure :-( 13:41:04 ... e.g. identities on mutiple networks. 13:41:23 bblfish: Multiple identities seems like a good idea - easy to do. 13:41:35 acceptable use is a problem, i dont think FB let's you do it 13:41:45 hhalpin: Could you maybe merge this with no-password use case? 13:41:50 "Using a web service should not involve password or account name creation" Use-case 13:42:02 but these seem kinda of technically separate 13:42:17 so keep them separate? 13:42:33 tons of cross talk 13:42:38 Zakim, mute me 13:42:38 hhalpin should now be muted 13:42:47 bblfish: the user not needing to have a password doesn't mean they can't identify themselves. It's a question of ease-of-use. A bit technical. 13:42:49 zakim, mute me 13:42:49 DKA should now be muted 13:42:59 no 13:43:02 zakim, unmute me 13:43:02 DKA should no longer be muted 13:43:06 think its henrys line 13:43:07 Zakim, unmute me 13:43:07 hhalpin should no longer be muted 13:43:22 ... repeated setting up of accounts is unnecessary and tedious. 13:43:38 are we losing bblfish? 13:43:48 ... data portability problem? 13:44:18 hhalpin: so bblfish wants to keep multiple identities and passwordless use cases separate? 13:44:43 bblfish: yes. latter is about ease of use. 13:44:47 sounds like OpenID? 13:45:06 sorry have to leave, see you. 13:45:15 -jsalvachua 13:45:16 tough to hear agreed 13:45:27 another use case that this makes me think of is: Identifiers on SN should not be resold to other people, as this would mess up the web of relations on the web. Eg: people saying they are firends of http://facebook.org/joe#me and then this being reassinged to Joe BadGuy 13:45:33 DKA: problem with zakim 13:45:36 -bblfish 13:46:02 ... let's move on; for now Henry as champion for multiple identities. 13:46:04 yes better 13:46:06 yes, the point is that the DataPortability group have mentioned that loggin in to every web site is a big problem 13:46:15 This is solved by OpenId, Passport, foaf+ssl 13:46:44 hhalpin: next use cases are all about group access control. 13:46:58 the data portability video: http://blogs.sun.com/bblfish/entry/data_portability_the_video 13:47:16 ... first is more abstract; second is the concrete example of family-access for a resource. 13:47:24 agreed kinship is cultural 13:47:33 ... Most comments suggest merging these. 13:47:33 Distributed Group Access Control" Use-case 13:47:38 hm. 13:47:39 +bblfish 13:47:54 DKA: who would agree on what a family is? link identity to genome? 13:48:07 hhalpin: who will champion this/these use cases? 13:48:45 ACTION: bblfish to merge Family and Group access usecases 13:48:45 Created ACTION-74 - Merge Family and Group access usecases [on Henry Story - due 2009-09-09]. 13:49:19 bblfish: yes, I'm championing this. Don't need to link in genome (scribe notes that FOAF does have an appropriate property) - just need to link to your family. 13:49:29 Intransitivity of Policies Applied to Social Network Data" Use-cas 13:49:36 but family markedness is cultural 13:49:42 hhalpin: intransitivity use case. 13:49:50 q+ 13:49:51 some cultures mark siblings but not gender 13:49:56 (tinkster - new foaf properties can be had for as little as 5 euros... send me mail :) 13:50:02 Current social networking platforms implement very rudimentary data usage policies. These mostly focuses on the immediate individuals concerned and do not have much consideration about the data transfer beyond them. Policy conflicts are also not properly handled. If the policies applied to social networking data are made to be transitive, we can make sure tha 13:50:10 ... if your data moves from one SN to another, your privacy policy can accompany it. 13:50:56 oshani: facebook quizzes - I'm not just giving out my own data, but my friends' data. This is a problem. 13:51:06 yeah that is a problem 13:51:25 (ah, i read "doesn't" :) 13:51:40 (yeah, dnachecksum started as a joke, but i think a few folk would like a real one!) 13:51:54 can the friends choose not to have their data being taken from one website to another? 13:52:32 q? 13:52:33 DKA: oshani, could you find a link to quizzes example? 13:52:35 ack osh 13:53:14 ACTION: oshani to flesh out "Intransitivity of Policies Applied to Social Network Data" 13:53:15 Created ACTION-75 - Flesh out "Intransitivity of Policies Applied to Social Network Data" [on Oshani Seneviratne - due 2009-09-09]. 13:53:28 hhalpin: bidirectional use case - everyone agreed to drop it. too vague? 13:53:49 ACTION: hhalpin to drop bidirectional use case 13:53:49 Created ACTION-76 - Drop bidirectional use case [on Harry Halpin - due 2009-09-09]. 13:53:50 peer pressure 13:54:39 ... virtual private organisation use case - create a temporary internal (or cross-organisation) network. 13:54:44 "Virtual Private Organization" Use-case 13:54:48 No champion 13:54:48 ... make sure it doesn't leak data. 13:54:54 I thought it came from joaquin... 13:55:05 DKA: Isn't this the corporate SN use case? 13:55:15 hhalpin: related to that heavily. 13:55:17 I suppose this is also very similar to "Distributed Group Access Control" 13:55:21 q+ 13:56:02 it is very similar to distributed group access contol. 13:56:09 Adam: I can champion this use case. Can look at this two ways - internally, people could create their own groups, which they could make private (even within the company) or not. 13:56:14 ... Or is this more complicated. 13:56:52 DKA: It's pretty bare-bones right now. It seems to point more to organically-growing networks. 13:58:25 sorry, I have to leave 13:58:27 groove does what you are describing 13:58:34 take care pchampin! 13:58:45 Adam: if you were to create one of these private virtual organisations, people would need to agree to its terms. Right now, our IT dept can create private organisations like this, and use the group to post some specific public content too. 13:59:10 maybe add links to Distributed Access control? 13:59:12 DKA: Can you add this as a sub-usecase? 13:59:43 -pchampin 13:59:49 tinkster: if what Adam describes could also take in people and departments at other organisations too. 14:00:00 pchampin has left #swxg 14:00:33 bblfish: related to distributed access control, which would be an enabling technology for it. 14:00:52 DKA: we're at the end of our slot. 14:00:55 Chair: hhalpin 14:01:06 we did pretty well getting through them 14:01:07 -DKA 14:01:09 bye DKA 14:01:10 hhalpin: three more use cases to go through. Should we go through them now? 14:01:22 so keep geo is clear 14:01:31 +1 for talking about these now 14:01:43 +1 14:01:43 +1 14:01:44 +1 14:02:18 ACTION: Adam to work on fleshing on "Virtual Private Organisation Use Case" reference distributed data access control policy 14:02:18 Created ACTION-77 - Work on fleshing on "Virtual Private Organisation Use Case" reference distributed data access control policy [on Adam Boyet - due 2009-09-09]. 14:02:53 did we doo the Too Many Channels? 14:03:18 hhalpin: geo use case. Inferences on location-based contextual data. We should have privacy controls on this, but should be able to share it if we want. Relates to portability and access control. 14:04:02 oshani: happy to champion this. can't see anything to merge with. 14:04:29 "Too many channels" can be move across different channels 14:04:51 ACTION: hhalpin to drop "too many channels" 14:04:51 hhalpin: "too many channels" use case - allow data to move across between different SNs. Pretty much covered by other portability and access use cases. We should drop. 14:04:51 Created ACTION-78 - Drop "too many channels" [on Harry Halpin - due 2009-09-09]. 14:05:25 ... Data protection use case. This is not easy. 14:05:30 hhalpin, nope, I am not a champion for that 14:05:48 bblfish: the question is very interesting, but I don't know what the answer is. 14:05:50 Alice is not a member of a given walled-garden social network and Bob tags her in an image from an event they were both at. Given that Alice finds out about this image, through word of mouth or by whatever means, should she be able to ask for her depiction to be removed? If she somehow manages to confirm that indeed it was a picture of her, should she be abl 14:06:13 hhalpin: similar to document takedown perhaps, but also need to look at legal requirements. 14:06:26 I think I M 14:06:29 data protection to me infers controlled access 14:06:39 controlled access 14:07:00 s/I M/I am 14:07:50 Could be kept separate there... 14:07:53 is this use case more about Alice's right to have the image removed? 14:08:00 Could be an intro to a number of use cases 14:08:01 oshani: this is different fron document take down in that it's initiated by an outsider. 14:09:00 hhalpin: perhaps it needs a bit of rephrasing. 14:09:10 bblfish: I'll think about that. 14:09:14 ACTION: bblfish to relabel data protection use case to be about controlled access and takedown to data "about" you 14:09:14