Hi!
On 6 Feb., 20:40, Julian Bond <julian_b...@voidstar.com> wrote:
> J. Trent Adams <jtrentad
...@gmail.com> Wed, 6 Feb 2008 11:04:12
> >Anyone have any objection to my going through and breaking out each
> >suggested Use Case as a separate page as a hierarchy under the current
> >single page?
> >My thinking here is that the current page becomes a Table of Contents
> >describing the overall info, then linking to each of it's "Use Case"
> >children. These pages, then would describe a separate case.
> Go for it. One thought though, the big long list of pages on the main
> page is going to become unmanageable. Perhaps we need to break out
> groups of them into the associated Action group pages.
I would second that it should be separated. That way we can later more
easily decide which use cases to implement first and
link to them on a separate page. It's also easier then to annotate the
use cases with technical ideas.
Regarding the notion of the central server we also had some discussion
yesterday on Skype what I possibly
meant with that ;-) So my basic idea there was that it's a principle
like Open ID, you decide what your main provider
is and data gets stored there. But you can choose which one this is,
sort of making one social network your base. Of course you should be
able to move that data elsewhere if you for some reason do not like
the network you are on anymore.
There were different voices aswell though, like Josh Patterson who
preferred a just a global index (service catalog)
which just points to the services you have. Thus every service which
needs data about you (e.g. your social graph) would query all those
other services and merge the data together. This might or might not be
cached, this is implementation specific.
Now I didn't have time to think about the implications of such an
approach and what it would mean to the usecases. But maybe I am alone
with my ideas of what should be done anyway and that's why I think we
first need some process in that area before thinking about
implementations.
Thus I think the technical ideas on how to implement it should be
removed from the use cases. This might also free us maybe from
limitations of thinking. After having choosen some use cases to
implement we can look out for the best technical solutions for them.
As there also seems to be some confusion about what DP actually means
to everybody we also should get clear about this first. The video is a
good thing to start and if everybody can produce any media explaining
what he/she thinks it is about than this might help, too. Additionally
it would be good if the companies in here can chime in if some use
cases turn out to never work for them or where we might need to think
about business implications a bit more.
-- Christian
PS: Tao Takashi and Christian Scholz are here interchangeable. It just
happened that I created a gmail account for my Second Life self (Tao)
and then used that as main account for all my Google stuff as you
cannot simply change users with Google (some DP problem aswell maybe).
But I might use a second browser now to get the names right. Just
wanted to clear this up shoud any confusion come out of this.
PPS: We also had very similar discussions about DP, multiple
identities, privacy etc. in Second Life regarding virtual worlds
interoperability. I might sum this up in some blog post soon.
--
http://mrtopf.de/blog
|
