not sure what an ambient interface is
This gets back to the idea of headless services driven by devices and
infrastructure. The use cases you've been concentrating on are user-driven
and real-time. The ones I've been focusing on are device or infrastructure
driven, real-time or batch. Phil's infrastructure accommodates both models
although his statement suggests he sees the device/infrastructure side as
being more prevalent in CloudOS. Both are important and if XDI can span
them, so much the better.
-- T.Rob
-----Original Message-----
Sent: Thursday, September 12, 2013 12:33 PM
To: Phil Windley
Cc: Doc Searls; ProjectVRM list; 'Drummond Reed'
Subject: Re: [projectvrm] CloudOS
It will work either in an XDI enabled browser or in an XDI enabled app
with
an ambient interface (not sure what an ambient interface is). We have an
XDI enabled mobile browser so naturally it gets my vote for the
transmission of data and also a really simple interface. You can come up
with an app tomorrow and we can replicate everything inside the browser
overnight - versus trying to build a cross platform app which requires too
much investment.
After watching your video the interaction takes place inside the browser,
why? Because it's a simple interface. IMO why confuse the consumer with
something new to learn on other devices. For VRM to work you have to
have a high adoption rate, changing interfaces introduces friction into
that,
and from the stats I've seen the (real world data) the usage drops off
incredibly quickly.
Remember all of this has to integrate into existing vendor infrastructure
- in every meeting I've been in Network Admins are not receptive to new
protocols or opening up additional ports in to their networks. VRM will
not
have a single answer - VRM is a concept that can be implemented using
various approaches - the customer and vendor will ultimately decide who
has picked the right approach and the right interface.
Peter
On 9/12/13 10:19 AM, "Phil Windley" <
">
> wrote:
>
>I don't think that the browser is the place where this will get the
>most use. In fact, I envision most of the interactions with CloduOS
>being done by other services and devices on the user's behalf. The user
>will use a browse or mobile app to configure that system, but I want
>the interactions to happen away from the device. Ambient interfaces, if
>you will.
>
>On Sep 12, 2013, at 10:05 AM, Peter Cranstone
>> On second thoughts after watching the video etc., you can do this
>>without an XDI enabled browser. All you need to do is build XDI
>>enabled applications, although IMO that's more complicated and comes
>>with the risk of figuring out how to extract real value with the app
>>(i.e. give it away for free but charge for the service). Scaling it
>>across multiple OS's is also more complex but certainly doable with
>>the right investment.
>>
>>
>>
>> Peter
>>
>>
>>
>>
>> On 9/11/13 3:37 PM, "Peter Cranstone"
>>wrote:
>>
>>> Looks like a perfect fit for an XDI enabled browser.
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> On 9/11/13 5:22 AM, "Doc Searls" <
">
>
wrote:
>>>
>>>> Phil Windley has put up an excellent short site on CloudOS, an open
>>>>
>>>> Check it out. And help out too. As you can see from missing future
>>>>links in the site, CloudOS is still new and needs more programmers
>>>>working on it.
>>>>
>>>> Doc
>>>
>>
>
>
