Category: Video

Preparing for the 3D/VR future

Look in the direction that meerkatMeerkat and periscopeappPeriscope both point.

If you’ve witnessed the output of either, several things become clear about their evolutionary path:

  1. Stereo sound is coming. So is binaural sound, with its you-are-there qualities.
  2. 3D will come too, of course, especially as mobile devices start to include two microphones and two cameras.
  3. The end state of both those developments is VR, or virtual reality. At least on the receiving end.

The production end is a different animal. Or herd of animals, eventually. Expect professional gear from all the usual sources, showing up at CES starting next year and on store shelves shortly thereafter. Walking around like a dork holding a mobile in front of you will look in 2018 like holding a dial-phone handset to your head looks today.

I expect the most handy way to produce 3D and VR streams will be with  glasses like these:

srlzglasses

(That’s my placeholder design, which is in the public domain. That’s so it has no IP drag, other than whatever submarine patents already exist, and I am sure there are some.)

Now pause to dig @ctrlzee‘s Fast Company report on Facebook’s 10-year plan to trap us inside The Matrix. How long before Facebook buys Meerkat and builds it into Occulus Rift? Or buys Twitter, just to get Periscope and do the same?

Whatever else happens, the rights clearing question gets very personal. Do you want to be broadcast and/or recorded by others or not? What are the social and device protocols for that? (The VRM dev community has designed one for the glasses above. See the ⊂ ⊃ in the glasses? That’s one. Each corner light is another.)

We should start zero-basing the answers today, while the inevitable is in sight but isn’t here yet. Empathy is the first requirement. (Take the time to dig Dave Winer’s 12-minute podcast on the topic. It matters.) Getting permission is another.

As for the relevance of standing law, almost none of it applies at the technical level. Simply put, all copyright laws were created in times when digital life was unimaginable (e.g. Stature of Anne, ASCAP), barely known (Act of 1976), or highly feared (WIPO, CTEA, DMCA).

How would we write new laws for an age that has barely started? Or why start with laws at all? (Nearly all regulation protects yesterday from last Thursday. And too often its crafted by know-nothings.)

We’ve only been living the networked life since graphical browsers and ISPs arrived in the mid-90’s. Meanwhile we’ve had thousands of years to develop civilization in the physical world. Which means that, relatively speaking, networked life is Eden. It’s brand new here, and we’re all naked. That’s why it’s so easy anybody to see everything about us online.

How will we create the digital equivalents of the privacy technologies we call clothing and shelter? Is the first answer a technical one, a policy one, or both? Which should come first? (In Europe and Australia, policy already has.)

Protecting the need for artists to make money is part of the picture. But it’s not the only part. And laws are only one way to protect artists, or anybody.

Manners come first, and we barely have those yet, if at all. None of the big companies that currently dominate our digital lives have fully thought out how to protect anybody’s privacy. Those that come closest are ones we pay directly, and are financially accountable to us.

Apple, for example, is doing more and more to isolate personal data to spaces the individual controls and the company can’t see. Google and Facebook both seem to regard personal privacy as a bug in online life, rather than a feature of it. (Note that, at least for their most popular services, we pay those two companies nothing. We are mere consumers whose lives are sold to the company’s actual customers, which are advertisers.)

Bottom line: the legal slate is covered in chalk, but the technical one is close to clean. What do we want to write there?

We’ll be talking about this, and many other things, at VRM Day (6 April) and IIW (7-9 April) in the Computer History Museum in downtown Silicon Valley (101 & Shoreline, Mountain View).

Designing the VRM future at IIW

A veteran VRooMeriiwxx tells me a design fiction would be a fun challenge for VRM Day and IIW (which will run from April 6-9 at the Computer History Museum in Mountain View, CA).

He describes one as “basically a way of peeking into the near future by demonstrating an imaginary product that doesn’t exist, but could. For example, instead of talking about a possible VRM product, one instead would create a marketing brochure, screen mockups or a fake video advertisement for this imaginary product as a way to help others understand where the world is headed and possibly even further the underlying technologies or driving concepts.”

Coincidentally, the subject of VRM Day (and a focus for the three days that will follow at IIW) is a maturity model framework that will provide every VRM developer the same single sheet (or set of them) on which to show where they stand in developing VRM capabilities into their company, product, code base or whatever else they’re working on. Work has already started on it, and those doing the work will present a first draft of it on VRM Day.

You know the old saying, “all singing from the same song sheet”? The VRM maturity model framework is it. Think of it as a musical score that is starting to be written, for an orchestra will come together. When we’re done with this round, we’ll at least know what the score describes, and give the players of different instruments enough of a framework so they know where they, and everybody else, fits.

By the end of IIW, it should be ready to do several things:

  1. Provide analysts with a single framework for understanding all VRM developers and development, and the coherencies among them.
  2. Give VRM developers a way to see how their work complements and/or competes with other VRM work that’s going on — and guide future developments.
  3. Give each developer a document to use for their own internal and external purposes.
  4. Give CRM, CE. CX and other vendor-side systems a clear picture of what pieces in the VRM development community will connect with their systems, and how, so buyer-side and seller-side systems can finally connect and grow together.

While we do this, it might also be fun to work out a design fiction as a summary document or video. What would the complete VRM solution (which will surely be a collection of them) look like? How would we present it as a single thing?

All of this is food for thinking and re-thinking. Suggestions invited.

@Capgemini on #VRM: well done!

Just learned about these two new videos by @Capgemini:

The introductory copy says,

Both Customer Relationship Management and Vendor Relationship Management want to improve customer relationships but they approach this differently. Find out what are the three main factors that separate them.

Both videos not only explain VRM nicely, but illustrate it on a whiteboard:

Screen Shot 2014-10-23 at 1.03.24 PM

Screen Shot 2014-10-23 at 1.04.48 PM

Big thanks to @LarrySCohen, @NielsvdLinden, @rickmans, Nick Gill and all the other @Capgemini people behind this. (Though not mentioned in the above links, I also want to throw thanks to @VINTLabs and @Sogeti, both also of Capgemini, and who I suspect are involved too.)

And it would be great if some could come to VRM Day and IIW next week. We’ll set the stage with these videos.

VRM videos

First Retail

Here is a collection of videos about VRM and related subjects, in roughly reverse chronological order.

First, a series of well-edited excerpts from Disrupting Retail 2013, which was hosted by First Retail in New York City. Here’s an outline:

  1. What is Disrupting Retail?
  2. Amazon’s Product Recommender Systems
  3. Big Data Enabled Intention Management and the Customer Experience
  4. Moving from Personal Data to Individual Intention

The sessions were led by Gam Dias (@gammydodger) of First Retail, with Andreas Weigend (@weigend) and myself serving as sounding boards for the collection of forward-looking retailers gathered around the table. (That’s the two of us in the shot above.) Lots of excellent grist for retailers, VRooMers and everybody else who cares about the future of business (which, let’s face it, wouldn’t be business without retail). Bonus link.

Second, Phil Windley on building trillion-node networks. Within those might be your network, with your own Internet of Things in your own cloud. Bonus video: The cloud needs an operating system.

Third, from the State of the Net (#SOTN) conference in Trieste last month, four videos:

There were a number of others as well, which I’ll put up when I find them (or they find me).

Fourth, some others from the last year and more:

© 2017 ProjectVRM

Theme by Anders NorenUp ↑