Introducing ID+, a very early networking concept

12 May 2005 - 3:39pm
9 years ago
2 replies
992 reads
Ben Hunt
2004

Hi group.

I'm posting after quite a long absence to give you early sight of a very
*very* new networking concept that I've invented in the last few weeks.

For now, I'd ask you not to promote this outside your immediate
contacts, because the infrastructure on the site is not quite ready (I'm
building a new forum to manage community discussions, which is almost
finished). You *can* sign up and post on the forums, but there's more
functionality to come.

I'm just showing this to a few select colleagues on this list and
elsewhere to gather some early expert opinions.

Please have a look through the site below, and let me know what you think!

It's codenamed ID+, and you can find a complete description of the shape
of the idea to date at http://www.idplus.org

Here are a few clues as to what it is and does:

* *It lets individuals store their "information" on a central account*
When you set up an account on an ID+ server (which anyone could
run), you and your friends and contacts can get access to your
information at any time from anywhere (think Plaxo but better).

* *It's a P2P web of trust*
ID+ uses reciprocal links to measure the strength of trust or
value in (real) interpersonal relationships. Fundamentally, ID+
aims to recreate digitally the real interpersonal networks we use
every day, and use the power of computer networks to take the pain
out of simple tasks (like contact management) and enable some
entirely new functions (like being able to request information
from friends of friends of friends with a high degree of
reliabilty). Please see the concept section
<http://www.idplus.org/concept.cfm> for more insight.

* *It's truly extensible*
The architecture is very high-level at the moment, but I'm clear
that user accounts will be use XML, to enable any kind of data to
be stored. The ID+ server can also be extended with (public or
commercial) modules that add new functionality that I haven't yet
dreamed of.

* *It's open source*
In sharing the idea with the global community I'm hoping that
individuals will come together to carry forward the conceptual and
technical development more quckly and successfully than a
commercial enterprise could ever achieve.

I look forward to hearing your thoughts about what all this may mean.

Best wishes,

Ben Hunt
Scratchmedia <http://www.scratchmedia.co.uk>

Comments

14 May 2005 - 5:15pm
Nick Ragouzis
2004

Ben,

Are you thinking of this at the infrastructure level, the
autonomous services to direct and transport the application's
transactions and maintain and sustain the state and control
required of sessions? Or at the application level, where we
would be talking about interface representation and user
interaction?

A bit of your concept.cfm seems to approach the topic as if
from the infrastructure level. But that confuses me, b/c I'd
guess that you're familiar with Liberty Alliance's [1] ID-WSF
technology which provides a highly-extensible solution in the
same domain.

* Defines a data services template that is extensible to any
kind of data, including publishing, notifications, as well as
query, for e.g., changing contact details, adding work skills.
* Defines a discovery service, so that from a variety of narrow
starting points (connectivity or semantically, and dynamically
adjustable) you can locate services for the various information
*types* or *entities* ... and the path of discovery can exhibit
variable gradients for access and inquiry/update.
* Defines a core contact book service, fully extensible. There's
also personal and employee profiles.
* Defines services that integrate (and allow conditioning on)
attributes such as geolocation (who can see me now, as compared
to when I'm in town), and presence (the usual IM/SIMPLE/XMPP
etc).
* Includes an autonomous service for conditioning any or all of
the above on my say-so at any moment ... which directs
an interaction with me without letting any of the requestors
or remote or intermediate parties learn how I was reached or
even that it was b/c I directly intervened.
* Possibly needless to say: within the context of how ever much
of a full message integrity, confidentiality, and authentication
service might be desired for an application. And, as well, is
treatable as a mature web service (metadata and wsdl).

The question of open source for the infrastructure is a valid
question. We haven't yet seen an open source implementation
of WSF announced. And although the specifications are open to
all, there is some potential for RAND aspects (in particular,
Sony's disclosures, some of which are declared but the patent
application remains unpublished). We'd have to judge how big a
problem that actually is, compared to the likelihood that any
other random architecture is *also* highly likely to run afoul
of similar (if not the same) claims ... and after much blood,
sweat, and tears.

As to applications ...

Applications of some of this are long out there. Fidelity
uses, widely, the employee profile to offer personalized services
through and at companies it serves. AOL/Radio uses personal
profile to offer a really cool phone- (how ever networked-) based
radio service ... real-time selection of music based on play
lists (in your profile).

But many more applications are needed. At the application level
your concept seems interesting. But for me, I immediately turn
to questions that derive from wanting these other services
integrated ... and that loops back to infrastructure.

Open source for the applications would be cool. And the ability
to treat application modules as discoverable and composeable ...
that would be great too.

A really serious need is dealing with how users cope with these
information flows and the permission issues they create. For
some time into the future, as well, there's an unavoidable time-,
use/purpose-, location-conditioning of context and modality
overhead as well. Both for permitting and retaining, and further
sharing.

If I had to characterize it overall: the infrastructure is the
easiest ... and very much more mature than current applications
being conceived and developed. The interaction dimensions,
however, are the ultimate limiters, and the least developed.

I would say: conceive the interaction models and interfaces,
mock up the infrastructure as if it existed like you wanted it
to.

A step further in service to enabling more folks to experiment
with interaction and interface would be to build an
infrastructure that is a completely virtual strata ... all
requests to the infrastructure must also characterize the
action desired, including state and failure, which the
virtual i/s serves up where/how commanded. Such a modeling
environment would be really really useful.

--Nick
Nick Ragouzis
Enosis Group
Sponsor, Liberty Alliance
Member, OASIS Security Services Technical Committee (SAMLv2.0)

[1] <http://projectliberty.org/resources/specifications.php>

> -----Original Message-----
> From:
> discuss-interactiondesigners.com-bounces at lists.interactiondesi
> gners.com
> [mailto:discuss-interactiondesigners.com-bounces at lists.interac
> tiondesigners.com] On Behalf Of Ben Hunt
> Sent: Thursday, May 12, 2005 01:40 PM
> To: IxD
> Subject: [ID Discuss] Introducing ID+, a very early networking concept
>
>
> [Please voluntarily trim replies to include only relevant
> quoted material.]
>
> Hi group.
>
>
> I'm posting after quite a long absence to give you early
> sight of a very
> *very* new networking concept that I've invented in the last
> few weeks.
>
> For now, I'd ask you not to promote this outside your immediate
> contacts, because the infrastructure on the site is not quite
> ready (I'm
> building a new forum to manage community discussions, which is almost
> finished). You *can* sign up and post on the forums, but there's more
> functionality to come.
>
> I'm just showing this to a few select colleagues on this list and
> elsewhere to gather some early expert opinions.
>
> Please have a look through the site below, and let me know
> what you think!
>
> It's codenamed ID+, and you can find a complete description
> of the shape of the idea to date at http://www.idplus.org
>
> Here are a few clues as to what it is and does:
>
> * *It lets individuals store their "information" on a
> central account*
> When you set up an account on an ID+ server (which anyone could
> run), you and your friends and contacts can get access to your
> information at any time from anywhere (think Plaxo but better).
>
> * *It's a P2P web of trust*
> ID+ uses reciprocal links to measure the strength of trust or
> value in (real) interpersonal relationships. Fundamentally, ID+
> aims to recreate digitally the real interpersonal
> networks we use
> every day, and use the power of computer networks to take the pain
> out of simple tasks (like contact management) and enable some
> entirely new functions (like being able to request information
> from friends of friends of friends with a high degree of
> reliabilty). Please see the concept section
> <http://www.idplus.org/concept.cfm> for more insight.
>
> * *It's truly extensible*
> The architecture is very high-level at the moment, but I'm clear
> that user accounts will be use XML, to enable any kind
> of data to
> be stored. The ID+ server can also be extended with (public or
> commercial) modules that add new functionality that I
> haven't yet dreamed of.
>
> * *It's open source*
> In sharing the idea with the global community I'm hoping that
> individuals will come together to carry forward the
> conceptual and
> technical development more quckly and successfully than a
> commercial enterprise could ever achieve.
>
>
> I look forward to hearing your thoughts about what all this may mean.
>
> Best wishes,
>
> Ben Hunt
> Scratchmedia <http://www.scratchmedia.co.uk>
> _______________________________________________
> Welcome to the Interaction Design Group!
> To post to this list ....... discuss at ixdg.org
> (Un)Subscription Options ... http://discuss.ixdg.org/
> Announcements List ......... http://subscribe-announce.ixdg.org/
> Questions .................. lists at ixdg.org
> Home ....................... http://ixdg.org/
>

31 May 2005 - 10:55am
Ben Hunt
2004

Nick, I apologize for the incredibly long delay in my replying to you.

I came to the idplus concept from a totally naive point. I wasn't
previously aware of Liberty Alliance <http://www.projectliberty.org/>,
the Augmented Social Network <http://asn.planetwork.net/>, mIDm
<http://www.downes.ca/idme.htm>, or Identity Commons
<http://www.identitycommons.net/> etc. I've discovered all these since
first publishing idplus.

On one level, I'm totally happy to have reinvented the wheel. This kind
of thing happens all the time. Good ideas get themselves spawned all
around the globe, with uncanny synchronicity (Google: morphic resonance
<http://www.google.co.uk/search?q=%22morphic+resonance%22&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official>).
I'd be more than content to think that I can add my ideas into the mix,
and possibly help shift something forward.

My problem just now is that I simply don't have the time to review the
existing state of the art, in order to evaluate where idplus may sit in
relation to it. I'll have to leave that to others who are already more
knowledgeable about the subject.

To answer your question, I've approached the whole system design
holistically: both infrastructure and interaction. Infrastructure is
nothing without applications, and vice versa. I conceived a high-level
platform to support applications that 'feel' like they ought to exist.

I'd love to visualize some applications. A few are in my head already.
Having said that, there are existing apps that reflect an aspect of what
this could be: LinkedIn and Plaxo are two obvious ones. Another one I
came across today is "Where are you now? <http://www.wayn.com/>" An
idplus client could be desktop software, server software, or a web site.
See the Applications section <http://www.idplus.org/forums.cfm?f=1> of
the Forum for some more recent ideas.

I would be interested to know whether any of the other approaches out
there are anywhere near the flying stage. Jan Hauser (of ASN) ntold me
that the biggest barrier they face is getting real people to take up the
concept. I don't anticipate that being such a big problem for idplus.
There are so many compelling potential applications, and the technology
is so easily achievable, that it could easily gain tipping-point, but
perhaps the open-source aspect is key?

As I see it, my only route forward right now is to put the concept out
to the likes of computer science postgrads to see if anyone would care
to firm up the tech part and prototype it. Any other ideas are very welcome!

Best regards,

Ben

Nick Ragouzis wrote:

>Ben,
>
>Are you thinking of this at the infrastructure level, the
>autonomous services to direct and transport the application's
>transactions and maintain and sustain the state and control
>required of sessions? Or at the application level, where we
>would be talking about interface representation and user
>interaction?
>
>A bit of your concept.cfm seems to approach the topic as if
>from the infrastructure level. But that confuses me, b/c I'd
>guess that you're familiar with Liberty Alliance's [1] ID-WSF
>technology which provides a highly-extensible solution in the
>same domain.
>
>* Defines a data services template that is extensible to any
> kind of data, including publishing, notifications, as well as
> query, for e.g., changing contact details, adding work skills.
>* Defines a discovery service, so that from a variety of narrow
> starting points (connectivity or semantically, and dynamically
> adjustable) you can locate services for the various information
> *types* or *entities* ... and the path of discovery can exhibit
> variable gradients for access and inquiry/update.
>* Defines a core contact book service, fully extensible. There's
> also personal and employee profiles.
>* Defines services that integrate (and allow conditioning on)
> attributes such as geolocation (who can see me now, as compared
> to when I'm in town), and presence (the usual IM/SIMPLE/XMPP
> etc).
>* Includes an autonomous service for conditioning any or all of
> the above on my say-so at any moment ... which directs
> an interaction with me without letting any of the requestors
> or remote or intermediate parties learn how I was reached or
> even that it was b/c I directly intervened.
>* Possibly needless to say: within the context of how ever much
> of a full message integrity, confidentiality, and authentication
> service might be desired for an application. And, as well, is
> treatable as a mature web service (metadata and wsdl).
>
>The question of open source for the infrastructure is a valid
>question. We haven't yet seen an open source implementation
>of WSF announced. And although the specifications are open to
>all, there is some potential for RAND aspects (in particular,
>Sony's disclosures, some of which are declared but the patent
>application remains unpublished). We'd have to judge how big a
>problem that actually is, compared to the likelihood that any
>other random architecture is *also* highly likely to run afoul
>of similar (if not the same) claims ... and after much blood,
>sweat, and tears.
>
>As to applications ...
>
>Applications of some of this are long out there. Fidelity
>uses, widely, the employee profile to offer personalized services
>through and at companies it serves. AOL/Radio uses personal
>profile to offer a really cool phone- (how ever networked-) based
>radio service ... real-time selection of music based on play
>lists (in your profile).
>
>But many more applications are needed. At the application level
>your concept seems interesting. But for me, I immediately turn
>to questions that derive from wanting these other services
>integrated ... and that loops back to infrastructure.
>
>Open source for the applications would be cool. And the ability
>to treat application modules as discoverable and composeable ...
>that would be great too.
>
>A really serious need is dealing with how users cope with these
>information flows and the permission issues they create. For
>some time into the future, as well, there's an unavoidable time-,
>use/purpose-, location-conditioning of context and modality
>overhead as well. Both for permitting and retaining, and further
>sharing.
>
>If I had to characterize it overall: the infrastructure is the
>easiest ... and very much more mature than current applications
>being conceived and developed. The interaction dimensions,
>however, are the ultimate limiters, and the least developed.
>
>I would say: conceive the interaction models and interfaces,
>mock up the infrastructure as if it existed like you wanted it
>to.
>
>A step further in service to enabling more folks to experiment
>with interaction and interface would be to build an
>infrastructure that is a completely virtual strata ... all
>requests to the infrastructure must also characterize the
>action desired, including state and failure, which the
>virtual i/s serves up where/how commanded. Such a modeling
>environment would be really really useful.
>
>--Nick
> Nick Ragouzis
> Enosis Group
> Sponsor, Liberty Alliance
> Member, OASIS Security Services Technical Committee (SAMLv2.0)
>
>
>
>[1] <http://projectliberty.org/resources/specifications.php>
>
>
>
>

Syndicate content Get the feed