August 05 2009 Conference Call

From Project VRM
Revision as of 14:18, 5 August 2009 by Joe.andrieu (talk | contribs) (→‎AOL)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Conference Call Notes

Drafted by Joe Andrieu, August 5, 2009


#vrm at

Other Calls

Category:conference call


  • Joe Andrieu
  • Dean Landsman
  • Iain Henderson
  • Judi Clark
  • Chris Carfi
  • Sean Bohan
  • Adriana Lukas



The first minotaur in the app approval process has been slain. The app is out there. Good questions being asked. Next steps are to start to nail down the open ways to get information in and out of Scanaroo. How do we get things in and out, under users control?

Discussion of IGF as possibility for data sharing, but that may be overkill.

Q: Insurance card information on the iPhone. Car accident. Then what? What would be seeable by outsiders? I'm unconscious, hospital wants the insurance info. How does this work with Scanaroo?

A: The way Scanaroo works for this. In the options, there is a passcode slider, which defaults off. In which case, the cards are open to anyone who opens the app. So, the whole app is either locked or open. So, you need the phone to access it. The data gets backed up to iTunes... using standard mechanisms.

Q: Parental rights. If I've given my kid an iphone and he has a bicycle crash, I want to be notified as the person, with specific rights.

A: Currently no special handling, whatever Apple/iTunes supports.

Q: Is this going to leak my data to the seller? As this moves to selective disclosure, this will become a more and more important issue. Especially, vis-a-vis knee jerk reactions by people to the data exposure.

When working on the MyDex, it took a lot of effort to get the programming team to break the CRM mindset where the corporation owns the data.

Similarly, there are lots of folks who will interpret it all into how to improve advertising.

From the couponing world, "we really need to make this work for the manufacture and the retailer"... and they needed an explicit reminder that it needs to work for the customer!


Interesting developments vis-a-vis an attempt to build a content business online. Hiring like mad. Maybe just another dinosaur trying to act like a small mammal, but it's a heck of an experiment.


Format/Design? Two days, open workshop. We have a room available, just not on the days we initially wanted. On the 12th/13th. That's Monday/Tuesday instead of Tuesday/Wednesday. CHECK YOUR CALENDARS

Whereas the November West Coast workshop is designed for leadership, folks who are doing stuff and want to step up. Still open to anyone, but with clear expectations about why we are there: not meant for newbies.

IIW goes through the issue with Newbies for Newbies: every cycle a new group comes in, works to put together a fac

At VRMHub, they run into similar dynamics: the never-ending stream of newbies asking "what is VRM"?


Developments? Keith is on vacation.

The Mine!

Mailing list buzzing with developers who want to help with the UI. Huge learning curve. Not a bottom line. Now in python and Django. Lots of people getting serious about wanting to see something want to do it. Running code should be in August. Just need to get the UI worked up. People are really committed to it, even though it isn't even out there yet. Proceeding as an open source project with lots of folks contributing and the related Chaos.

Terms of Service

Doc has been getting a lot of interest... what's interesting about Scanaroo is that its a great context for the place in my phone where I hold my end of the relationships: thinking about loyalty from the other way around. Where we'd like to protect ourselves from the dangerous use of our data. What are sets of defaults TOS? Has this been thought about in VPI? A set of preferences so you can "valve" your exposure, with permissions about what you are doing with the data.

VPI is very specific about data access, not the entire TOS.

Is there overlap with the AP here? They are wrapping and tracking their information. Is there something similar we can do.

There are similarities...

The AP had an interesting take, talking about it as a DRM system, so that if you use their stuff wrong, the AP can catch you. But at the heart of it, it is a bunch of microformats. An interesting approach.

One challenge is that the AP doesn't have an explicit agreement with content consumers about the use of AP data. If you're an AP customer, there's a signed contract, but for the average user, there is no agreement to the AP restrictions. VPI and UMA are working to get that contractual agreements in place to moderate that access, but to do so seamlessly.

Next Meeting