https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&feedformat=atom&user=Jeckman 2026-07-28T01:19:37Z User contributions MediaWiki 1.43.6 https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3672 2009-10-13T18:37:41Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> <br /> # Excel download of sleep features<br /> # OpenAPI - access your sleep data from anywhere on the web (data export) (Read, Write, or Both)<br /> # Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> # Open up the data real time - data comes out of the serial port, do we publish the format<br /> # Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. <br /> <br /> A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3671 2009-10-13T18:37:12Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> <br /> # Excel download of sleep features<br /> # OpenAPI - access your sleep data from anywhere on the web (data export) (Read, Write, or Both)<br /> # Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> # Open up the data real time - data comes out of the serial port, do we publish the format<br /> # Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3670 2009-10-13T18:36:54Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> # Excel download of sleep features<br /> # OpenAPI - access your sleep data from anywhere on the web (data export) (Read, Write, or Both)<br /> # Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> # Open up the data real time - data comes out of the serial port, do we publish the format<br /> # Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3669 2009-10-13T18:35:40Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> 1 - Excel download of sleep features<br /> 1 - OpenAPI - access your sleep data from anywhere on the web (data export) (Read, Write, or Both)<br /> 1 - Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> 1 - Open up the data real time - data comes out of the serial port, do we publish the format<br /> 1 - Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3668 2009-10-13T18:35:19Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> # - Excel download of sleep features<br /> # - OpenAPI - access your sleep data from anywhere on the web (data export)<br /> Read, Write, or Both<br /> # - Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> # - Open up the data real time - data comes out of the serial port, do we publish the format<br /> # - Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3667 2009-10-13T18:34:47Z

<p>Jeckman: </p> <hr /> <div>Creating an Open Zeo ecosystem session<br /> <br /> Attendees:<br /> * John Eckman<br /> * Tom Stites<br /> * Ben Rubin<br /> * Keith Hopper<br /> * Doc Searls<br /> * Robbin Lubbock<br /> * Bob Wayland<br /> * Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> 1 - Excel download of sleep features<br /> 2 - OpenAPI - access your sleep data from anywhere on the web (data export)<br /> Read, Write, or Both<br /> 3 - Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> 4 - Open up the data real time - data comes out of the serial port, do we publish the format<br /> 5 - Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=Creating_an_Open_Zeo_ecosystem_-_how_open_should_we_be&diff=3666 2009-10-13T18:23:01Z

<p>Jeckman: New page: Creating an Open Zeo ecosystem John Eckman Tom Stites Ben Rubin Keith Hopper Doc Searls Robbin Lubbock Bob Wayland Alan Hoving Where we have been - you use the SD card to upload your da...</p> <hr /> <div>Creating an Open Zeo ecosystem<br /> <br /> John Eckman<br /> Tom Stites<br /> Ben Rubin<br /> Keith Hopper<br /> Doc Searls<br /> Robbin Lubbock<br /> Bob Wayland<br /> Alan Hoving<br /> <br /> <br /> Where we have been - you use the SD card to upload your data to the web site. <br /> <br /> What are the various ways we could open this data?<br /> 1 - Excel download of sleep features<br /> 2 - OpenAPI - access your sleep data from anywhere on the web (data export)<br /> Read, Write, or Both<br /> 3 - Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep<br /> 4 - Open up the data real time - data comes out of the serial port, do we publish the format<br /> 5 - Make it an open application platform - let other people write apps on it. <br /> <br /> We’re leaning towards the open platform, but we have to make sure we do it responsibly. <br /> <br /> How many users? Largest sleep database in the world, well over 30,000 points of data. <br /> <br /> Reach out along social media space - FB group (300 fans), twitter account (600 followers). <br /> <br /> To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo) <br /> <br /> People are talking about their ZQ score - we’re seeing the 1% of that online, but people are having the conversation. <br /> <br /> Doc recommends registering the OtherThird.com - for the other third of your life which is sleep. A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep. <br /> <br /> B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data. <br /> <br /> C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?<br /> <br /> <br /> ---<br /> <br /> At the end of the day, the building of a commuity around what you’re doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data. <br /> <br /> Reaching out to existing communities - where can we find folks who are already having this issue. <br /> <br /> Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question. <br /> <br /> ---<br /> <br /> Forum recomendations - Vanilla, Ning, BBPress, <br /> <br /> ---<br /> <br /> What about data owership:<br /> <br /> We’re right at the beginning of this and we don’t know what’s around the curve. We’ve got the folks who are zealots, and folks who don’t care at all, and not much in between. <br /> <br /> You need to be able to redraw the picture as you go - drawing your picture in pencil as you go. <br /> <br /> You’ve bitten off a market corner that’s really large but focused. <br /> <br /> You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road. <br /> <br /> What kinds of policy make sense for data usage? What should you allow or not allow? <br /> <br /> Difficulty of traditional challenges - the default corporate culture today would be to keep the data private. <br /> <br /> Keith - the key value here is going to be the community, which will require honestly. Also, you’re going to get a lot more exposure by being open. Finally you’re also going to get some interesting results coming out of the research. <br /> <br /> Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data? <br /> <br /> ----<br /> <br /> What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?<br /> <br /> When people impersonate you, that’s a sign you’ve won. Don’t worry about Elvis impersonators - you’ll always be better at it than you. <br /> ---<br /> <br /> Devil’s Advocate positions:<br /> - let people access their data, but only through a web API<br /> - let people access their data off the SD card but decrypt it if you use an app where you’ve accepted a developer version. <br /> <br /> What’s wrong with that?<br /> <br /> Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?<br /> <br /> What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them. <br /> <br /> The shift from “you give us ownership” to “you give us a right to use a copy” in photo sharing services - there are steps beyond this you can explore. <br /> <br /> Example: you can use this data for non-commercial, aggregate level research studies. <br /> <br /> What you want ultimately is a trusted relationship with your community of users - that’s a huge value if they know that they trust. That’s more important than the cheap opportunity you’d miss out on from selling the user’s data. <br /> <br /> You have to be the shining example of safeguarding the users data. <br /> <br /> What’s the benefit to the consumer of interacting with you? The most important thing is to build trust with the community. <br /> - you’re gonna sleep better <br /> - you’re gonna become part of a community <br /> - you’ll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)<br /> <br /> What will build trust?<br /> - a user data covenant is one part of a broader picture<br /> - accurate results, helpful results<br /> - transparency into the data<br /> - contest type stuff - the X prize for sleep<br /> <br /> Open is horizontal, closed is vertical - you can do either, you can even play at both. <br /> <br /> Apple as the prime counter example - they manage to do things but stay closed. <br /> <br /> Be ready to jump - let the market tell you.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=VRooM_Boston_2009&diff=3665 2009-10-13T18:22:38Z

<p>Jeckman: /* Sesions */</p> <hr /> <div>[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.<br /> <br /> As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. Most of the workshop will be an &quot;unconference&quot; on the open space model, which means session topics will be chosen by participants. ([http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]) The one exception will be [http://cyber.law.harvard.edu/projectvrm/VRooM_Boston_2009#Panel:_Getting_Personal_With_Data:_How_Users_Get_Control_and_What_They_Do_With_It ''Getting Personal With Data: How Users Get Control and What They Do With It''], described below.<br /> <br /> == Registration ==<br /> <br /> The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].<br /> <br /> == Possible Topics for sessions / discussion ==<br /> <br /> (These are just suggestions. The topics can be anything.)<br /> <br /> * VRM and Health Care<br /> * VRM hacks, so far<br /> * User-initiated terms of service<br /> * Where Personal informatics / self-tracking aligns with VRM (User control of data.)<br /> * Existing technologies and protocols VRM can use<br /> * [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)<br /> * The Mine! Project<br /> * MINT<br /> * VRM and search<br /> * Personal Data Stores<br /> * VRM and open source<br /> * Scanaroo (and turning loyalty cards inside-out)<br /> * ListenLog<br /> * Emancipay<br /> * VRM and Identity (Information Cards, OpenID...)<br /> * VRM and Mobile<br /> * Personal RFPs<br /> * VRM evangelism<br /> * VRM and search<br /> * VRM and Real Estate<br /> <br /> == Open Space format ==<br /> <br /> In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large &quot;spreadsheet&quot; of times and session locations, which will be posted on the side of the room.<br /> <br /> One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group. At the end of the second day everybody will discuss progress made and next steps.<br /> <br /> <br /> == Schedule ==<br /> <br /> === Monday ===<br /> <br /> ==== Setup and Sessions ====<br /> <br /> ''''Greetings and VRM overview by Doc Searls''''<br /> <br /> ''''Suggesting and choosing the day's session topics''''<br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * Issues in P2P Data Storage and Exchange<br /> * 20,000 foot view of where VRM will thrive - What areas are ripe for VRM applications?<br /> <br /> '''''Session 2'''''<br /> * Privacy Policy, Terms of Use, and anonymity (is it important?)<br /> * Real estate - the need for buyer and seller-sided VRM apps<br /> <br /> '''''Wrap-up'''''<br /> ''''' Reports from group sessions '''''<br /> <br /> ==== Dinner on Monday Night ====<br /> Monday's dinner at at 6:30 at Daedalus in Harvard Sq. (http://www.daedalusharvardsquare.com/)<br /> <br /> # Doc Searls<br /> # Keith Hopper<br /> # Dean Landsman<br /> # John Eckman<br /> # Mary Ruddy<br /> # Andy Oram<br /> # Alexander Torrenegra <br /> # Charles Andres<br /> # Sean Bohan<br /> # Someone else I forgot<br /> <br /> === Tuesday ===<br /> <br /> ==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It ====<br /> [http://www.google.com/search?hl=en&amp;q=self-tracking '''Self-tracking'''] and [http://www.google.com/search?hl=en&amp;q=personal+informatics '''personal informatics'''] are hot [http://www.selftracking.net/ new] new development categories, driven by the growing sense that primary responsibility for gathering personal data, integrating it, and putting it to use, belongs to individuals -- not to companies, governments or other organizations. Together these tools help individuals become both the [http://blog.joeandrieu.com/2007/06/14/vrm-the-user-as-point-of-integration/ ''point of integration''] for their own data, and the ''primary authority'' for what gets done with that data. <br /> <br /> ''Self-tracking'' is how individuals collect data about themselves, while ''personal informatics'' is how individuals organize that data and put it to use. Together these tools inform individuals' relationships with themselves, with their social networks, with the organizations to which they belong -- and with sellers of all kinds.<br /> <br /> Tools for self-tracking and personal informatics are new, already becoming popular, and in need of much thinkig about how personal data is gathered, stored and shared -- concerns that are near and dear to those who follow VRM.<br /> <br /> Each panelist is either developing tools in these categories or has experience with new tools and the issues involved. Doc Searls, of the Berkman Center and ProjectVRM, will moderate the panel, and we expect discussion with participants (there will be no &quot;audience&quot; here) to be lively and informative.<br /> <br /> ==== Moderator ====<br /> '''Doc Searls''' - [http://cyber.law.harvard.edu/ Berkman Center]<br /> <br /> ==== Panelists &amp; Their Projects ====<br /> '''Ben Rubin''' - [http://myzeo.com Zeo]<br /> <br /> Ben is the co-founder and CTO of Zeo Inc. Zeo has created and recently launched the world's first personal sleep coach.<br /> <br /> '''Adriana Lukas''' - [http://themineproject.org/ The Mine! Project]<br /> <br /> In addition to working on the Mine! project designed to turn individual user into a platform by helping him to capture, manage and share data on his own terms, she also runs [http://www.vrmhub.net/ VRM Hub] in London and disrupts companies [http://www.mediainfluencer.net/about/ for living].<br /> <br /> '''Tim Hwang''' - [http://www.webecologyproject.org Web Ecology Project]<br /> <br /> In addition to the Web Ecology Project, Tim Founded [http://roflcon.org ROFLCon] and [http://awesomefoundation.org The Awesome Foundation], and [http://upcoming.yahoo.com/event/2171174/ Information Superhighway]. He is working on a book on the mechanics of web culture and memes online. <br /> <br /> '''Keith Hopper''' - [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]<br /> <br /> Keith works on digital product strategy for [http://npr.org NPR]. He is the creator of [http://keithhopper.com/blog/nprbackstory NPRbackstory], was a contributing author for the book [http://www.amazon.com/Collective-Intelligence-Creating-Prosperous-World/dp/097156616X/ref=pd_bbs_sr_4?ie=UTF8&amp;s=books&amp;qid=1208206490&amp;sr=8-4 Collective Intelligence], and has done some [http://keithhopper.com/about other fun stuff].<br /> <br /> ==== Sesions ====<br /> <br /> <br /> (Wiki note takers will fill in the sessions below. The canonical session outline will be on the wall of the room during the workshop.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' [[Creating an Open Zeo ecosystem - how open should we be]]?<br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Research possibilities'''''<br /> <br /> ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ''''' Wrap-up and next steps '''''<br /> <br /> ==Space/Location==<br /> <br /> We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], &quot;“It is a step for further advance to see what has been won from chaos already.&quot;) The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue (&quot;Mass Ave&quot;) next to the big construction project. <br /> <br /> The room will have plenty of chairs and tables for group sessions.<br /> <br /> Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.<br /> <br /> [http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.<br /> <br /> == Name ==<br /> <br /> The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose &quot;VRM East Coast Workshop 2009&quot; as a way to stay sort-of in compliance with that poor naming convention. The name &quot;VRooM&quot; was chosen by suggestion from the ProjectVRM mailing list. <br /> <br /> The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=VRooM_Boston_2009&diff=3664 2009-10-13T18:22:01Z

<p>Jeckman: /* Sesions */</p> <hr /> <div>[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.<br /> <br /> As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. Most of the workshop will be an &quot;unconference&quot; on the open space model, which means session topics will be chosen by participants. ([http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]) The one exception will be [http://cyber.law.harvard.edu/projectvrm/VRooM_Boston_2009#Panel:_Getting_Personal_With_Data:_How_Users_Get_Control_and_What_They_Do_With_It ''Getting Personal With Data: How Users Get Control and What They Do With It''], described below.<br /> <br /> == Registration ==<br /> <br /> The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].<br /> <br /> == Possible Topics for sessions / discussion ==<br /> <br /> (These are just suggestions. The topics can be anything.)<br /> <br /> * VRM and Health Care<br /> * VRM hacks, so far<br /> * User-initiated terms of service<br /> * Where Personal informatics / self-tracking aligns with VRM (User control of data.)<br /> * Existing technologies and protocols VRM can use<br /> * [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)<br /> * The Mine! Project<br /> * MINT<br /> * VRM and search<br /> * Personal Data Stores<br /> * VRM and open source<br /> * Scanaroo (and turning loyalty cards inside-out)<br /> * ListenLog<br /> * Emancipay<br /> * VRM and Identity (Information Cards, OpenID...)<br /> * VRM and Mobile<br /> * Personal RFPs<br /> * VRM evangelism<br /> * VRM and search<br /> * VRM and Real Estate<br /> <br /> == Open Space format ==<br /> <br /> In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large &quot;spreadsheet&quot; of times and session locations, which will be posted on the side of the room.<br /> <br /> One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group. At the end of the second day everybody will discuss progress made and next steps.<br /> <br /> <br /> == Schedule ==<br /> <br /> === Monday ===<br /> <br /> ==== Setup and Sessions ====<br /> <br /> ''''Greetings and VRM overview by Doc Searls''''<br /> <br /> ''''Suggesting and choosing the day's session topics''''<br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * Issues in P2P Data Storage and Exchange<br /> * 20,000 foot view of where VRM will thrive - What areas are ripe for VRM applications?<br /> <br /> '''''Session 2'''''<br /> * Privacy Policy, Terms of Use, and anonymity (is it important?)<br /> * Real estate - the need for buyer and seller-sided VRM apps<br /> <br /> '''''Wrap-up'''''<br /> ''''' Reports from group sessions '''''<br /> <br /> ==== Dinner on Monday Night ====<br /> Monday's dinner at at 6:30 at Daedalus in Harvard Sq. (http://www.daedalusharvardsquare.com/)<br /> <br /> # Doc Searls<br /> # Keith Hopper<br /> # Dean Landsman<br /> # John Eckman<br /> # Mary Ruddy<br /> # Andy Oram<br /> # Alexander Torrenegra <br /> # Charles Andres<br /> # Sean Bohan<br /> # Someone else I forgot<br /> <br /> === Tuesday ===<br /> <br /> ==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It ====<br /> [http://www.google.com/search?hl=en&amp;q=self-tracking '''Self-tracking'''] and [http://www.google.com/search?hl=en&amp;q=personal+informatics '''personal informatics'''] are hot [http://www.selftracking.net/ new] new development categories, driven by the growing sense that primary responsibility for gathering personal data, integrating it, and putting it to use, belongs to individuals -- not to companies, governments or other organizations. Together these tools help individuals become both the [http://blog.joeandrieu.com/2007/06/14/vrm-the-user-as-point-of-integration/ ''point of integration''] for their own data, and the ''primary authority'' for what gets done with that data. <br /> <br /> ''Self-tracking'' is how individuals collect data about themselves, while ''personal informatics'' is how individuals organize that data and put it to use. Together these tools inform individuals' relationships with themselves, with their social networks, with the organizations to which they belong -- and with sellers of all kinds.<br /> <br /> Tools for self-tracking and personal informatics are new, already becoming popular, and in need of much thinkig about how personal data is gathered, stored and shared -- concerns that are near and dear to those who follow VRM.<br /> <br /> Each panelist is either developing tools in these categories or has experience with new tools and the issues involved. Doc Searls, of the Berkman Center and ProjectVRM, will moderate the panel, and we expect discussion with participants (there will be no &quot;audience&quot; here) to be lively and informative.<br /> <br /> ==== Moderator ====<br /> '''Doc Searls''' - [http://cyber.law.harvard.edu/ Berkman Center]<br /> <br /> ==== Panelists &amp; Their Projects ====<br /> '''Ben Rubin''' - [http://myzeo.com Zeo]<br /> <br /> Ben is the co-founder and CTO of Zeo Inc. Zeo has created and recently launched the world's first personal sleep coach.<br /> <br /> '''Adriana Lukas''' - [http://themineproject.org/ The Mine! Project]<br /> <br /> In addition to working on the Mine! project designed to turn individual user into a platform by helping him to capture, manage and share data on his own terms, she also runs [http://www.vrmhub.net/ VRM Hub] in London and disrupts companies [http://www.mediainfluencer.net/about/ for living].<br /> <br /> '''Tim Hwang''' - [http://www.webecologyproject.org Web Ecology Project]<br /> <br /> In addition to the Web Ecology Project, Tim Founded [http://roflcon.org ROFLCon] and [http://awesomefoundation.org The Awesome Foundation], and [http://upcoming.yahoo.com/event/2171174/ Information Superhighway]. He is working on a book on the mechanics of web culture and memes online. <br /> <br /> '''Keith Hopper''' - [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]<br /> <br /> Keith works on digital product strategy for [http://npr.org NPR]. He is the creator of [http://keithhopper.com/blog/nprbackstory NPRbackstory], was a contributing author for the book [http://www.amazon.com/Collective-Intelligence-Creating-Prosperous-World/dp/097156616X/ref=pd_bbs_sr_4?ie=UTF8&amp;s=books&amp;qid=1208206490&amp;sr=8-4 Collective Intelligence], and has done some [http://keithhopper.com/about other fun stuff].<br /> <br /> ==== Sesions ====<br /> <br /> <br /> (Wiki note takers will fill in the sessions below. The canonical session outline will be on the wall of the room during the workshop.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' [wiki:OpenZeo | Creating an Open Zeo ecosystem - how open should we be]?<br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Research possibilities'''''<br /> <br /> ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ''''' Wrap-up and next steps '''''<br /> <br /> ==Space/Location==<br /> <br /> We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], &quot;“It is a step for further advance to see what has been won from chaos already.&quot;) The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue (&quot;Mass Ave&quot;) next to the big construction project. <br /> <br /> The room will have plenty of chairs and tables for group sessions.<br /> <br /> Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.<br /> <br /> [http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.<br /> <br /> == Name ==<br /> <br /> The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose &quot;VRM East Coast Workshop 2009&quot; as a way to stay sort-of in compliance with that poor naming convention. The name &quot;VRooM&quot; was chosen by suggestion from the ProjectVRM mailing list. <br /> <br /> The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=VRooM_Boston_2009&diff=3663 2009-10-13T18:21:43Z

<p>Jeckman: /* Sesions */</p> <hr /> <div>[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.<br /> <br /> As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. Most of the workshop will be an &quot;unconference&quot; on the open space model, which means session topics will be chosen by participants. ([http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]) The one exception will be [http://cyber.law.harvard.edu/projectvrm/VRooM_Boston_2009#Panel:_Getting_Personal_With_Data:_How_Users_Get_Control_and_What_They_Do_With_It ''Getting Personal With Data: How Users Get Control and What They Do With It''], described below.<br /> <br /> == Registration ==<br /> <br /> The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].<br /> <br /> == Possible Topics for sessions / discussion ==<br /> <br /> (These are just suggestions. The topics can be anything.)<br /> <br /> * VRM and Health Care<br /> * VRM hacks, so far<br /> * User-initiated terms of service<br /> * Where Personal informatics / self-tracking aligns with VRM (User control of data.)<br /> * Existing technologies and protocols VRM can use<br /> * [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)<br /> * The Mine! Project<br /> * MINT<br /> * VRM and search<br /> * Personal Data Stores<br /> * VRM and open source<br /> * Scanaroo (and turning loyalty cards inside-out)<br /> * ListenLog<br /> * Emancipay<br /> * VRM and Identity (Information Cards, OpenID...)<br /> * VRM and Mobile<br /> * Personal RFPs<br /> * VRM evangelism<br /> * VRM and search<br /> * VRM and Real Estate<br /> <br /> == Open Space format ==<br /> <br /> In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large &quot;spreadsheet&quot; of times and session locations, which will be posted on the side of the room.<br /> <br /> One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group. At the end of the second day everybody will discuss progress made and next steps.<br /> <br /> <br /> == Schedule ==<br /> <br /> === Monday ===<br /> <br /> ==== Setup and Sessions ====<br /> <br /> ''''Greetings and VRM overview by Doc Searls''''<br /> <br /> ''''Suggesting and choosing the day's session topics''''<br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * Issues in P2P Data Storage and Exchange<br /> * 20,000 foot view of where VRM will thrive - What areas are ripe for VRM applications?<br /> <br /> '''''Session 2'''''<br /> * Privacy Policy, Terms of Use, and anonymity (is it important?)<br /> * Real estate - the need for buyer and seller-sided VRM apps<br /> <br /> '''''Wrap-up'''''<br /> ''''' Reports from group sessions '''''<br /> <br /> ==== Dinner on Monday Night ====<br /> Monday's dinner at at 6:30 at Daedalus in Harvard Sq. (http://www.daedalusharvardsquare.com/)<br /> <br /> # Doc Searls<br /> # Keith Hopper<br /> # Dean Landsman<br /> # John Eckman<br /> # Mary Ruddy<br /> # Andy Oram<br /> # Alexander Torrenegra <br /> # Charles Andres<br /> # Sean Bohan<br /> # Someone else I forgot<br /> <br /> === Tuesday ===<br /> <br /> ==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It ====<br /> [http://www.google.com/search?hl=en&amp;q=self-tracking '''Self-tracking'''] and [http://www.google.com/search?hl=en&amp;q=personal+informatics '''personal informatics'''] are hot [http://www.selftracking.net/ new] new development categories, driven by the growing sense that primary responsibility for gathering personal data, integrating it, and putting it to use, belongs to individuals -- not to companies, governments or other organizations. Together these tools help individuals become both the [http://blog.joeandrieu.com/2007/06/14/vrm-the-user-as-point-of-integration/ ''point of integration''] for their own data, and the ''primary authority'' for what gets done with that data. <br /> <br /> ''Self-tracking'' is how individuals collect data about themselves, while ''personal informatics'' is how individuals organize that data and put it to use. Together these tools inform individuals' relationships with themselves, with their social networks, with the organizations to which they belong -- and with sellers of all kinds.<br /> <br /> Tools for self-tracking and personal informatics are new, already becoming popular, and in need of much thinkig about how personal data is gathered, stored and shared -- concerns that are near and dear to those who follow VRM.<br /> <br /> Each panelist is either developing tools in these categories or has experience with new tools and the issues involved. Doc Searls, of the Berkman Center and ProjectVRM, will moderate the panel, and we expect discussion with participants (there will be no &quot;audience&quot; here) to be lively and informative.<br /> <br /> ==== Moderator ====<br /> '''Doc Searls''' - [http://cyber.law.harvard.edu/ Berkman Center]<br /> <br /> ==== Panelists &amp; Their Projects ====<br /> '''Ben Rubin''' - [http://myzeo.com Zeo]<br /> <br /> Ben is the co-founder and CTO of Zeo Inc. Zeo has created and recently launched the world's first personal sleep coach.<br /> <br /> '''Adriana Lukas''' - [http://themineproject.org/ The Mine! Project]<br /> <br /> In addition to working on the Mine! project designed to turn individual user into a platform by helping him to capture, manage and share data on his own terms, she also runs [http://www.vrmhub.net/ VRM Hub] in London and disrupts companies [http://www.mediainfluencer.net/about/ for living].<br /> <br /> '''Tim Hwang''' - [http://www.webecologyproject.org Web Ecology Project]<br /> <br /> In addition to the Web Ecology Project, Tim Founded [http://roflcon.org ROFLCon] and [http://awesomefoundation.org The Awesome Foundation], and [http://upcoming.yahoo.com/event/2171174/ Information Superhighway]. He is working on a book on the mechanics of web culture and memes online. <br /> <br /> '''Keith Hopper''' - [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]<br /> <br /> Keith works on digital product strategy for [http://npr.org NPR]. He is the creator of [http://keithhopper.com/blog/nprbackstory NPRbackstory], was a contributing author for the book [http://www.amazon.com/Collective-Intelligence-Creating-Prosperous-World/dp/097156616X/ref=pd_bbs_sr_4?ie=UTF8&amp;s=books&amp;qid=1208206490&amp;sr=8-4 Collective Intelligence], and has done some [http://keithhopper.com/about other fun stuff].<br /> <br /> ==== Sesions ====<br /> <br /> <br /> (Wiki note takers will fill in the sessions below. The canonical session outline will be on the wall of the room during the workshop.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' [wiki:OpenZeo Creating an Open Zeo ecosystem - how open should we be]?<br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Research possibilities'''''<br /> <br /> ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ''''' Wrap-up and next steps '''''<br /> <br /> ==Space/Location==<br /> <br /> We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], &quot;“It is a step for further advance to see what has been won from chaos already.&quot;) The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue (&quot;Mass Ave&quot;) next to the big construction project. <br /> <br /> The room will have plenty of chairs and tables for group sessions.<br /> <br /> Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.<br /> <br /> [http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.<br /> <br /> == Name ==<br /> <br /> The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose &quot;VRM East Coast Workshop 2009&quot; as a way to stay sort-of in compliance with that poor naming convention. The name &quot;VRooM&quot; was chosen by suggestion from the ProjectVRM mailing list. <br /> <br /> The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=VRooM_Boston_2009&diff=3662 2009-10-13T18:21:19Z

<p>Jeckman: /* Sesions */</p> <hr /> <div>[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.<br /> <br /> As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. Most of the workshop will be an &quot;unconference&quot; on the open space model, which means session topics will be chosen by participants. ([http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]) The one exception will be [http://cyber.law.harvard.edu/projectvrm/VRooM_Boston_2009#Panel:_Getting_Personal_With_Data:_How_Users_Get_Control_and_What_They_Do_With_It ''Getting Personal With Data: How Users Get Control and What They Do With It''], described below.<br /> <br /> == Registration ==<br /> <br /> The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].<br /> <br /> == Possible Topics for sessions / discussion ==<br /> <br /> (These are just suggestions. The topics can be anything.)<br /> <br /> * VRM and Health Care<br /> * VRM hacks, so far<br /> * User-initiated terms of service<br /> * Where Personal informatics / self-tracking aligns with VRM (User control of data.)<br /> * Existing technologies and protocols VRM can use<br /> * [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)<br /> * The Mine! Project<br /> * MINT<br /> * VRM and search<br /> * Personal Data Stores<br /> * VRM and open source<br /> * Scanaroo (and turning loyalty cards inside-out)<br /> * ListenLog<br /> * Emancipay<br /> * VRM and Identity (Information Cards, OpenID...)<br /> * VRM and Mobile<br /> * Personal RFPs<br /> * VRM evangelism<br /> * VRM and search<br /> * VRM and Real Estate<br /> <br /> == Open Space format ==<br /> <br /> In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large &quot;spreadsheet&quot; of times and session locations, which will be posted on the side of the room.<br /> <br /> One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group. At the end of the second day everybody will discuss progress made and next steps.<br /> <br /> <br /> == Schedule ==<br /> <br /> === Monday ===<br /> <br /> ==== Setup and Sessions ====<br /> <br /> ''''Greetings and VRM overview by Doc Searls''''<br /> <br /> ''''Suggesting and choosing the day's session topics''''<br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * Issues in P2P Data Storage and Exchange<br /> * 20,000 foot view of where VRM will thrive - What areas are ripe for VRM applications?<br /> <br /> '''''Session 2'''''<br /> * Privacy Policy, Terms of Use, and anonymity (is it important?)<br /> * Real estate - the need for buyer and seller-sided VRM apps<br /> <br /> '''''Wrap-up'''''<br /> ''''' Reports from group sessions '''''<br /> <br /> ==== Dinner on Monday Night ====<br /> Monday's dinner at at 6:30 at Daedalus in Harvard Sq. (http://www.daedalusharvardsquare.com/)<br /> <br /> # Doc Searls<br /> # Keith Hopper<br /> # Dean Landsman<br /> # John Eckman<br /> # Mary Ruddy<br /> # Andy Oram<br /> # Alexander Torrenegra <br /> # Charles Andres<br /> # Sean Bohan<br /> # Someone else I forgot<br /> <br /> === Tuesday ===<br /> <br /> ==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It ====<br /> [http://www.google.com/search?hl=en&amp;q=self-tracking '''Self-tracking'''] and [http://www.google.com/search?hl=en&amp;q=personal+informatics '''personal informatics'''] are hot [http://www.selftracking.net/ new] new development categories, driven by the growing sense that primary responsibility for gathering personal data, integrating it, and putting it to use, belongs to individuals -- not to companies, governments or other organizations. Together these tools help individuals become both the [http://blog.joeandrieu.com/2007/06/14/vrm-the-user-as-point-of-integration/ ''point of integration''] for their own data, and the ''primary authority'' for what gets done with that data. <br /> <br /> ''Self-tracking'' is how individuals collect data about themselves, while ''personal informatics'' is how individuals organize that data and put it to use. Together these tools inform individuals' relationships with themselves, with their social networks, with the organizations to which they belong -- and with sellers of all kinds.<br /> <br /> Tools for self-tracking and personal informatics are new, already becoming popular, and in need of much thinkig about how personal data is gathered, stored and shared -- concerns that are near and dear to those who follow VRM.<br /> <br /> Each panelist is either developing tools in these categories or has experience with new tools and the issues involved. Doc Searls, of the Berkman Center and ProjectVRM, will moderate the panel, and we expect discussion with participants (there will be no &quot;audience&quot; here) to be lively and informative.<br /> <br /> ==== Moderator ====<br /> '''Doc Searls''' - [http://cyber.law.harvard.edu/ Berkman Center]<br /> <br /> ==== Panelists &amp; Their Projects ====<br /> '''Ben Rubin''' - [http://myzeo.com Zeo]<br /> <br /> Ben is the co-founder and CTO of Zeo Inc. Zeo has created and recently launched the world's first personal sleep coach.<br /> <br /> '''Adriana Lukas''' - [http://themineproject.org/ The Mine! Project]<br /> <br /> In addition to working on the Mine! project designed to turn individual user into a platform by helping him to capture, manage and share data on his own terms, she also runs [http://www.vrmhub.net/ VRM Hub] in London and disrupts companies [http://www.mediainfluencer.net/about/ for living].<br /> <br /> '''Tim Hwang''' - [http://www.webecologyproject.org Web Ecology Project]<br /> <br /> In addition to the Web Ecology Project, Tim Founded [http://roflcon.org ROFLCon] and [http://awesomefoundation.org The Awesome Foundation], and [http://upcoming.yahoo.com/event/2171174/ Information Superhighway]. He is working on a book on the mechanics of web culture and memes online. <br /> <br /> '''Keith Hopper''' - [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]<br /> <br /> Keith works on digital product strategy for [http://npr.org NPR]. He is the creator of [http://keithhopper.com/blog/nprbackstory NPRbackstory], was a contributing author for the book [http://www.amazon.com/Collective-Intelligence-Creating-Prosperous-World/dp/097156616X/ref=pd_bbs_sr_4?ie=UTF8&amp;s=books&amp;qid=1208206490&amp;sr=8-4 Collective Intelligence], and has done some [http://keithhopper.com/about other fun stuff].<br /> <br /> ==== Sesions ====<br /> <br /> <br /> (Wiki note takers will fill in the sessions below. The canonical session outline will be on the wall of the room during the workshop.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' Creating an Open Zeo ecosystem - how open should we be?<br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Research possibilities'''''<br /> <br /> ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ''''' Wrap-up and next steps '''''<br /> <br /> ==Space/Location==<br /> <br /> We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], &quot;“It is a step for further advance to see what has been won from chaos already.&quot;) The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue (&quot;Mass Ave&quot;) next to the big construction project. <br /> <br /> The room will have plenty of chairs and tables for group sessions.<br /> <br /> Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.<br /> <br /> [http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.<br /> <br /> == Name ==<br /> <br /> The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose &quot;VRM East Coast Workshop 2009&quot; as a way to stay sort-of in compliance with that poor naming convention. The name &quot;VRooM&quot; was chosen by suggestion from the ProjectVRM mailing list. <br /> <br /> The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.</div>

Jeckman https://cyber.harvard.edu/projectvrm/?title=VRooM_Boston_2009&diff=3635 2009-10-09T19:14:04Z

<p>Jeckman: </p> <hr /> <div>[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.<br /> <br /> As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. The workshop will be run as an &quot;unconference&quot; on the open space model, which means session topics will be chosen by participants. [http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]<br /> <br /> In open space there are no speakers or panels -- just participants, gathered to get work done and enjoy doing it. Participation includes contributing to the this wiki<br /> <br /> The one exception is a panel: <br /> <br /> == Registration ==<br /> <br /> The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].<br /> <br /> == Possible Topics for sessions / discussion ==<br /> <br /> (These are just suggestions. The topics can be anything.)<br /> <br /> * VRM and Health Care<br /> * VRM hacks, so far<br /> * User-initiated terms of service<br /> * Where Personal informatics / self-tracking aligns with VRM (User control of data.)<br /> * Existing technologies and protocols VRM can use<br /> * [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)<br /> * The Mine! Project<br /> * MINT<br /> * VRM and search<br /> * Personal Data Stores<br /> * VRM and open source<br /> * Scanaroo (and turning loyalty cards inside-out)<br /> * ListenLog<br /> * Emancipay<br /> * VRM and Identity (Information Cards, OpenID...)<br /> * VRM and Mobile<br /> * Personal RFPs<br /> * VRM evangelism<br /> * VRM and search<br /> <br /> == Open Space format ==<br /> <br /> In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large &quot;spreadsheet&quot; of times and session locations, a blackboard in the front of Pound 101, which will be our main room.<br /> <br /> One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group. At the end of the second day everybody will discuss progress made and next steps.<br /> <br /> <br /> == Schedule ==<br /> <br /> === Monday ===<br /> <br /> ==== Setup and Sessions ====<br /> <br /> ''''Greetings and VRM overview by Doc Searls''''<br /> <br /> ''''Suggesting and choosing the day's session topics''''<br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 5'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ==== Dinner on Monday Night ====<br /> Put your name here if you hope to join us Monday night for dinner so we can make reservations. It will be a few blocks from Pound Hall near Harvard Square.<br /> <br /> * Doc Searls<br /> * Keith Hopper<br /> * Dean Landsman<br /> * John Eckman<br /> <br /> === Tuesday ===<br /> <br /> ==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It. ====<br /> <br /> The issue of users conrolling their data is central not just to VRM, but to parallel efforts in health care, privacy, governance and other areas. So we are opening Tuesday with a discussion among participants, led by a panel of folks who have been obsessing on the topic. More specifically, we've been thinking about this as &quot;personal informatics / self-tracking and some opportunities and projects emerging around storing, sharing, and using personal data.&quot;<br /> <br /> ==== Moderator ====<br /> * Doc Searls - [http://cyber.law.harvard.edu/ Berkman Center]<br /> <br /> ==== Panelists &amp; Their Projects ====<br /> * Ben Rubin - Founder and CTO, [http://myzeo.com Zeo]<br /> * Adriana Lukas - Creator, [http://themineproject.org/ The Mine! Project]<br /> * Tim Hwang - Founder, [http://www.webecologyproject.org Web Ecology Project]<br /> * Keith Hopper - Creator [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]<br /> <br /> ==== Sesions ====<br /> <br /> <br /> (Wiki note takers will fill in the sessions below.)<br /> <br /> '''''Session 1'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 2'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 3'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Session 4'''''<br /> * '''A:''' <br /> * '''B:''' <br /> * '''C:''' <br /> * '''D:'''<br /> <br /> '''''Research possibilities'''''<br /> <br /> ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.<br /> <br /> ''''' Reports from group sessions '''''<br /> <br /> ''''' Wrap-up and next steps '''''<br /> <br /> <br /> ==Space/Location==<br /> <br /> We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], &quot;“It is a step for further advance to see what has been won from chaos already.&quot;) The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue (&quot;Mass Ave&quot;) next to the big construction project. <br /> <br /> The room will have plenty of chairs and tables for group sessions.<br /> <br /> Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.<br /> <br /> [http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.<br /> <br /> == Name ==<br /> <br /> The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose &quot;VRM East Coast Workshop 2009&quot; as a way to stay sort-of in compliance with that poor naming convention. The name &quot;VRooM&quot; was chosen by suggestion from the ProjectVRM mailing list. <br /> <br /> The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.</div>

Jeckman