Thought's on Location?
David Recordon
has become a larger part of social networking. Brightkite obviously
is focused on this, Facebook sort of achieves it at the scale of
"status" though also makes privacy choices based on your physical
network, I integrate it with my blog via FireEagle which is populated
from Dopplr, etc. Should one component of a DiSo enabled site be the
ability to know where someone is should they wish to make that
available? I think this is a little more dynamic than just a hometown
profile field, but the ability to have location as a core component of
a DiSo profile? so that other features, services, permissions, etc can
build atop it?
--David
Writing this makes me think a discussion on what does it mean to be
"DiSo Enabled" or is there such a thing as "core components of DiSo"?
Josh Patterson
data is used, given that it creates another layer of context by
framing the current data in the real world. A lot of distributed /
open / linked data systems at some point will want to have some type
of geo-location aspect to them so I wouldn't think it would be a
function of if DiSo would employ that, more a matter of when (although
I'm not one of the core developers / designers on the project, so
thats just my opinion.).
In terms of how, it looks like the pattern of message pumping from
node to node is becoming a hop topic, from RSS syndication to XMPP.
Looks like the spirit of smtp is alive and well. Is location something
that is broadcast out, or queried for at runtime, etc? Right now I'm
really interested in seeing what proprietary services become the
framework for open data interchange standards, because I'm really
interested in how we're evolving the "internet OS" from the bottom up.
How is location going to be wired into that? I'm really liking
Oreilly's metaphor of the loosely coupled parts, and really an
operating system is that, so I think there is lots of design idea re-
use there to be had in terms of ideas on how to get data around.
Since designing a product or concept requires the right sequence of
layers or building blocks, Chris Messina might want to produce a
roadmap showing about where location would start to be wired in.
Josh Patterson
Steven Livingstone-Perez
from the search engine folk (I listened to Brad Goldberg last night) is
around location so yes, I think this would be very useful.
In fact, when it comes to mobile GPS services could allow a device to supply
location as a transparent part of a profile. So when you say core, yes, I
can see this being a lot more than location - the interesting part I see is
that is we get a street address such as "34 Main Street" this actually
translates into say "St. John's Monument" which socially is probably better
understood by the user community ... but most map api's don't give you
access to place *names* as such - really just addresses etc (and in most
social apps I suspect would say the name of something well known rather than
it's typically obscure street address).
Steven
Steve Ivy
1) LOD, or Level Of Detail. Sometimes I'm not going to want to let
people know that I'm at 123 Main in Anytown USA, but I might (like
with Dopplr) be willing to let them know that I'm in Anytown USA. This
tie into...
2) Permissions: I may not want *everyone* to know that I'm at 123
Main, but, I might want my friends to know, or I might want my
"friends who are also located in Anytown" to know. *That* would be
cool.
2a) Then, of course, you have the idea of basing other profile
permissions of of location as well, but I haven't thought of any
interesting applications yet. Perhaps sharing my phone number with any
friends in the same town? I don't know.
On Mon, Jun 16, 2008 at 2:44 AM, Steven Livingstone-Perez
<web...@hotmail.com> wrote:
>
> There is also plazes which I have been using for some time now. All I hear
> from the search engine folk (I listened to Brad Goldberg last night) is
> around location so yes, I think this would be very useful.
>
> In fact, when it comes to mobile GPS services could allow a device to supply
> location as a transparent part of a profile. So when you say core, yes, I
> can see this being a lot more than location - the interesting part I see is
> that is we get a street address such as "34 Main Street" this actually
> translates into say "St. John's Monument" which socially is probably better
> understood by the user community ... but most map api's don't give you
> access to place *names* as such - really just addresses etc (and in most
> social apps I suspect would say the name of something well known rather than
> it's typically obscure street address).
This is where something like the Google Maps / Wikipedia mashup works well.
>
> Steven
>
> -----Original Message-----
> From: diso-p...@googlegroups.com [mailto:diso-p...@googlegroups.com]
> On Behalf Of David Recordon
> Sent: 15 June 2008 20:29
> To: diso-p...@googlegroups.com
> Subject: [diso-project] Thought's on Location?
>
>
> At GSP last week I got to thinking more around how where someone is
> has become a larger part of social networking. Brightkite obviously
> is focused on this, Facebook sort of achieves it at the scale of
> "status" though also makes privacy choices based on your physical
> network, I integrate it with my blog via FireEagle which is populated
> from Dopplr, etc. Should one component of a DiSo enabled site be the
> ability to know where someone is should they wish to make that
> available? I think this is a little more dynamic than just a hometown
> profile field, but the ability to have location as a core component of
> a DiSo profile? so that other features, services, permissions, etc can
> build atop it?
>
> --David
>
> Writing this makes me think a discussion on what does it mean to be
> "DiSo Enabled" or is there such a thing as "core components of DiSo"?
>
>
>
>
>
> >
>
--
Steve Ivy
http://redmonk.net // http://diso-project.org
This email is: [ ] bloggable [x] ask first [ ] private
Steven Livingstone-Perez
There is (2a) for permissions, but in a social aspect a lot of social interaction could also be driven be the intersection of location profile information under some context. I looked into such a project with some friends this time last year. An extended example ... "where's hot for parents with young kids in your area on a Sunday morning" (how I wish such a service existed!).
Cheers,
Steven
http://livz.org
David Recordon
granular, but ultimately you don't want to manage your social network
within FireEagle (nor is it designed for you to do so). I'd thus
imagine that your DiSo Enabled site would know your exact location and
know what you want to share with whom.
--David
unodewaal
interestingly that you mention that, we've got a company started that
might be doing exactly that (and a couple of other things as well).
It's happening in the next couple of months, so hopefully by the end
of the year there should be a beta.
Cheers,
Uno.
On Jun 16, 5:03 pm, "Steven Livingstone-Perez" <webl...@hotmail.com>
wrote:
>
> There is (2a) for permissions, but in a social aspect a lot of social interaction could also be driven be the intersection of location profile information under some context. I looked into such a project with some friends this time last year. An extended example ... "where's hot for parents with young kids in your area on a Sunday morning" (how I wish such a service existed!).
>
> Cheers,