Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]

[Meadhbh Siobhan <[e-mail]>]

if you implement an agent domain, you may choose to do this, but in
the same way that RFC822 and it's successors didn't require your email
address to be first initial + last name + @ + fqdn, i don't think it's
appropriate for a protocol to require a naming structure for the
virtual world.

we SHOULD definitely try to create a system by which you can publish a
URL for your agent (like http://example.org/Oh/Meadhbh or
http://example.com/MeadhbhOh) that is memorable and will yield a HTML
page with info about the agent, but also accepts LLSD messages for
things like "give me the user's public profile in LLSD" or "i'm a
trusted region domain, give me a capability i can use to return items
to the user's inventory". Further, i would add, that client
applications SHOULD respond to redirects when accessing these
resources. That way, if my agent domain _really_ wanted to export
something as http://example.org/a/BDFB8691-9FD5-444A-B601-4075E7226242
and then expose multiple URLs like http://example.org/Oh/Meadhbh and
http://example.org/Hamrick/Meadhbh, they COULD do that. (thought it
wouldn't be required that an agent domain do that.)

On Mon, Jun 29, 2009 at 7:04 AM, Christian Scholz<[e-mail]> wrote:
> Mike Dickson wrote:
>> I have to agree with Carlo on this.  This is a case where virtual life
>> needs to model real life.  Lots of people with the same name in the
>> world.  The protocol needs to support some other way to uniquely
>> identify a "user" other than FN/LN.
>
> I would also go further and say that it would be great to reuse
> identities on non-3D social networks. As we see with OpenID this usually
> is done via URLs (like myspace.com/mrtopf and now also
> facebook.com/mrtopf) and I don't see why this shouldn't be used here as
> well.
> firstname/lastname should be provided as well of course (e.g. via
> reading it over an OpenSocial REST API) but the real identity is then
> defined via the URL. I am not sure where to display it though, if
> directly over an avatar or inside the profile page but that needs some
> experimentation I guess. At least some means need to be given to find
> out which person it actually is.
>
> -- Christian
>
>> When crossing into a new region it seems highly possible that a region
>> owner may want to require a re-authentication also.
>>
>> I'm not suggesting a solution becaus this isn't my personal area of
>> expertise.  Simply stating I see the problem and agree a good solution
>> needs to be found.
>>
>> Mike
>>
>> On Mon, 2009-06-29 at 11:45 +0000, Carlo Wood wrote:
>>> On Mon, Jun 29, 2009 at 04:13:08AM -0700, Meadhbh Siobhan wrote:
>>>> On Mon, Jun 29, 2009 at 3:51 AM, Carlo Wood<[e-mail]> wrote:
>>>> as mentioned in the draft, deployers MAY choose to identify users via
>>>> account ids rather than first+last.
>>> But that is local to the deployers.
>>>
>>> What is used to ID an agent in the server-server protocol
>>> when a user walks from one region into another, or teleports
>>> to a different region?
>>>
>>> Firstname Lastname should be merely payload, not interesting
>>> to the servers, not being used for anything except passing
>>> it on the the viewers so they can use it to put in the tags.
>>>
>>> There must be some other string, that is globally unique,
>>> that is used to ID the agent. I was missing that string
>>> in the first post that started this.
>>>
>>
>> _______________________________________________
>> ogpx mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/ogpx
>
>
> --
> Christian Scholz                          Homepage: http://comlounge.net
> COM.lounge GmbH                              blog: http://mrtopf.de/blog
> Hanbrucher Str. 33                                       Skype: HerrTopf
> 52064 Aachen                             Video Blog: http://comlounge.tv
> Tel: [phone]                           E-Mail [e-mail]
> Fax: [phone]                               IRC: MrTopf, Tao_T
>
> neuer Podcast: Der OpenWeb-Podcast (http://openwebpodcast.de)
> new podcast: Data Without Borders (http://datawithoutborders.net)
>
>