PII 2011 Venture Forum Breakfast

November 15th, 2011

This should be an interesting kick-off to a fascinating day. Disclosure: the breakfast at PII 2011 Venture Forum is sponsored by C-PET, the Center for Policy on Emerging Technologies. I hadn’t heard of this organization before today. It’s a think tank focusing on long term, transformative effects, how things fit together.

Nigel Cameron (President and CEO) notes that the gap between regular corporate culture and policy around emerging tech is large, with disparate cultures.

Jim Dempsey, Center for Democracy and Technology: works on issues affecting the Internet. There are lots of things that DC and Silicon Valley have in common: people come from all over the country, meritocracy, attraction of talent, people who are dedicated and have a vision, rapid response. DC is all about ideas. There is a culture clash among people who should be able to understand each other. DC got it right for initial policy framework for early Internet development. Now it’s under challenge.

Rebecca Lynn, Morgenthaler Ventures: She’s a VC, every company in her portfolio has a unique relationship with DC. About a year and half ago, she realized she needed to know how this all worked (then did so). Convened business competition pitch with entrepreneurs and policy makers.

Christine Peterson, Foresight Institute (started early with nanotech policy): Current (physical) arrangement of lobbyists in DC is “kind of nauseating.” Individual people are approachable. People here needed to learn the system in order to launch a rocket that the military would not shoot down. Genetic information isn’t seen as the people’s.

David Tennenhouse, New Venture Partners: work on spin-outs from corporates, has run the gamut of systems. The key interest in common between Silicon Valley and DC is innovation. DC depends on it for competitiveness, we (SV) live and breathe it. One problem: I do see two levels of engagement: 1) fly in and lobby then fly out (doesn’t do too much for long term), and 2) really influencing the agencies, agendas in an ongoing way. They can’t form agendas without substance from Silicon Valley.

Cameron: mostly wonderful people locked into a dysfunctional corporate culture–working while the ship goes down. Two questions: creative community is represented in DC by a mega technology companies (who represent too much of the past, therefore not inclined to shift the corporate culture). Lynn: Start-ups don’t have time to do this, they need to focus on their interests. Look where the money flows; people are rational actors. Hard for a VC to get behind innovation when the money in DC flows against them. Peterson: large tech companies do some wonderful things and use the word innovation, but the real deep innovation comes from small companies, competitors. Lynn: Salesforce was busy in Congress, it can be daunting to be representing a competing interest. Tennenhouse: Sources for innovation: Universities are largely government funded for research, large corporates start inventions but then spin out, scale things up. Need to make sure the invention parts stay in tact, keep government off backs of innovators. Dempsey: if goal is to promote innovation, it’s not likely to be a big company that will support it and you can’t just get the government out of the way (they facilitate). What are values that promote innovation, the Internet ecosystem? Communities can lobby for these principles.

Questions/Statements: Marcy: There’s a very different value system between policy makers in DC and working landscape in California. Need for startups to band together, need for agile legislation. John Gerard: divide is not cultural, it’s structural. What focuses our energy? Global trademarks (e.g., Facebook pages). Gene Cavanaugh: WIPO has it’s problems but that’s where international trademarks are done. He represents small inventors (lawyer). What he finds is process is contorted: government is only interested in grassroots efforts is if you don’t need the money. If you don’t, the gov will fund you. (Irony alert). Agrees that there’s a structural disconnect: DC gives lots of lip service to innovation but funds top-down. Ernie Te: telecom policy and Continental Divide: systematically saw a government mindset vs entrepreneurial mindset. Government has an illusion of control, decides policy A or B for reality A or B. People in the valley understand there’s more uncertainty, will allow different approaches to be taken. Jacky (SAP): she represents industry bodies in cloud competing, wrote a blog (post) about data crossing borders, job growth globally; there’s an opportunity can enable start-ups.

Lynn: I’m more practical. There are reasons people live in Silicon Valley, the way business is done is different. Need to figure out how DC works. They’re doing things that are more entrepreneurial, but the system is different. Hopefully we can work together. Tennenhouse: Comment about the role of uncertainty in innovation: looking back, development and success are unevenly accomplished. Acknowledging difference in cultures, some agencies (inside beltway, DARPA) should be figuring out how to do it, suggests partnership systems. Peterson: heard this from Peter Theil first: startup companies don’t have to start here, in nanotech, in Sinapore. These decisions are invisible to DC. How to make this more visible. Example: if you give up your US citizenship, you continue to pay taxes for 10 years. Braindrain if we disabled that? Lynn: cross-pollination of cultures. Bring people out here to help with translation. Dempsey: everybody is looking for failure? Unacceptable to say that 50% of R&D investments will fail. How to turn this around, make it work? Point is that failure is a successful strategy: try things that might not work is a definition of success (a Silicon Valley perspective). Think comprehensively, act incrementally. Cautiousness, conservativeness, unwillingness to try new things is a problem (DC). Cameron: it’s all about corporate culture. There are things that could be done. Get these guys (DC) to come to conferences here, get the thinking into their bloodstreams. It’s not so much about technology or process, but in DC all conversations are about debt. Look at what the questions are. We need to reshape what questions are being asked.

 

future, history

IIW XIII: The Final Overview

October 27th, 2011
young person sitting alone, by xJason.Rogersx

Thanks xJason.Rogersx

What a head-filling event! If you’re interested, you can see notes from many of the sessions on the IIW wiki. Some of the sessions are rather technical, which is consistent with the roots of this unconference.

A few of the things I learned: people continue to amaze me by these projects: personal data projects (check out Personal–no notes from their demo; and soon The Locker Project), reputation sites (I was busy vouching for people whose work I know with Connect.me), the many stories of evented APIs (think actions: when something happens, it can trigger something else to happen, as in the “Internet of Things”), and of course the evolution of the Personal Data Ecosystem and PDEC.

Coaching moment: There are two major forces pushing forward. One is represented by Facebook: collect and manipulate, sell and distribute all of the personal data that can be found. This is a pulling, pillaging process with the “users” as the product being sold. The other force is not yet represented, but you might think of it as an opposite: individual people have access to their own data when they need it, using starter organizing, permissioning, sharing and distribution tools. What if you could say “No Facebook, you can’t plunder my own and my friends’ data–and mean it? What if advertisers came to you when you wanted? The idea is to say “yes” and “no” to data sharing when it’s appropriate for you. It’s you who is important, not a product.

history, records, tools

IIW XIII: Standard Information Sharing Agreement

October 20th, 2011

Information Sharing Work Group, a group of Kantara Initiative, is working to develop a standard information sharing agreement. Slides are in progress, will be linked to when available.

Joe offered a quick intro to Information Sharing Agreements. The point of Information Sharing Agreements is to improve services for both individuals and organizations through the right data and the right time. Services need data to operate.  Personal data is the most relevant, timely and quality data. This is what individuals bring to the table.

  • Criteria. Preferences. Requirements. Queries and Intention
  • Relationships and memberships
  • Age, Address and billing information
  • History: transactions and interactions.

Together, all of this comprises the digital context that people bring to their online experience.

If organizations can access this context, they can provide a bunch of interesting services and improve existing services. Read more…

future, records, tools

IIW XIII: Yubico

October 20th, 2011

Brief introductions. Yubico offers Yubikeys that help with authentication: low cost and simple! Acts as a keyboard, enters user password and 32 character passcode. Easier than smart cards (insert into USB port, push a button).

Lots of users: 1M users + 16k customers in 95 countries. Use cases: Google for internal staff, PayPal, Fedora, lastpass. Yubico is self-service: hardware sales on web store, free and open source server components and virtual appliance for remote access (enterprise-class VPN.

Versions of Yubikey: regular: one-time password, OATH (works with OTP – one-time passcode, not same as oAuth) standard, Static password, and Challenge response key. Secure life cycle: “trust no one.” Secure your servers.

Key is robust: sealed, simple. Accidentally went through a washing machine for several weeks and worked fine.

Future vision: one key for all Internet: YubiCloud validation service, 3rd party single sign-on and SAML. High security, Easy to use, Low cost. Plans to work with mobile phones via nearfield communications (NFC).

Demo (with keys) and questions. Here’s a video on how Yubico is working with Google Apps in Sweden. They’re working on supporting Google Apps here soon. Here’s a page where you can test your key.

tools

IIW XIII: PDEC Technical Documentation Group

October 20th, 2011

Markus pointed out that the purpose of PDEC is to help coordinate and educate, facilitate dialog in the system. Most of our current work is on the legal and business level, and also needs to happen on technical level. PDEC is trying to catalyze the ecosystem. One of the important promises of the ecosystem is the interoperability; needs some technical work/agreement/understanding. We’re not about setting standards, we’re about discovery, conversation, documentation. Technical profiles of the different projects, what exposed schemas and APIs, how it’s exposed, what strategies are in use.

Proposal to collect a set of questions that will help inform the dialog:

  • data model/schema for personal data
  • technology endpoints: API, network protocols, interface
  • what do they offer: query, import/export, update, delete
  • technology for protecting privacy/control: cryptography?
  • client support: mobiles? desktop? browser plug-ins?
  • developer resources: libraries? wikis?
  • notion of identity: un/pw?
  • architecture: centralized? open?
  • data portability

Interoperability:

  • What’s required to establish interoperability?
  • What’s in their future plans?
  • Can your project work with someone else’s project?

Documentation steps:

  1. Document technical profile — with temporal attribute (what tech now, what changes coming?)
  2. Interoperability: do you have interoperability with another member of the ecosystem? or planning to do?
  3. (TBD)

Proposal suggested that we put a set of questions up and propose member organizations post responses (RSS or other) to help “cat herding” of the information. Proposal suggested to organize info in three columns: name, tech keywords, brief description. Proposal to pre-define businesses (personal data store) then differentiate between those companies/projects. Some questions won’t apply equally to all companies in the startup circle.

Survey Examples (does this format work?):

Technology Personal.com Locker Project Gluu/SAML
appliance
Data model/schema own schema (gems) x x
Tech for sharing RDF endpoints, oAuth? x XDI, LDAP, SAML for federation
Protecting privacy/controls x x x
Client support x x x

Need to do more thinking on how to collect/organize this information.

future, history, records

Switch to our mobile site