Re: [ogpx] URI schema for virtual world locations?

the seondlife URI scheme is a hack used to automagically launch the SL
viewer based on web interaction like with the map @ slurl.com. as i
read it, the point of a location URI in the protocol is to provide a
mechanism for carrying information in a point in a virtual world.
instead of abusing URIs like we have in the past, maybe we should
define a LLIDL map for containing information about a location, then
use more traditional URLs to point to the location of these services.

so rather than have something like:

   secondlife://example.com/Levenhall/128/128/32

we would define a LLIDL map like:

{
  region_name : string,
  location : [ int, int, int ]
}

and then serialize it as:

<?xml version="1.0" encoding="utf-8"?>
<llsd>
  <map>
    <key>region_name</key>
    <string>Levenhall</string>
    <key>location</key>
    <array>
      <integer>128</integer>
      <integer>128</integer>
      <integer>32</integer>
    </array>
  <map>
</llsd>

and maybe make them available at a traditional URL like:

http://example.com/regions/3F05D047-B5AF-4332-938E-675A1EA1D784

this would have the advantage that implementers could easily stuff
experimental new parameters into the serialization. if we used the
mime types in the client application launch message draft (
http://tools.ietf.org/html/draft-hamrick-ogp-launch-00 ) then we could
hack our web browsers to recognize the application/ogpcal+xml content
type and pass it to a client application of our choice.

so.. to recap.. secondlife style URIs should be deprecated (or at
least not used in VWRAP.) we should use URLs that use a well known
protocol (like https) that describe a protocol endpoint for retrieving
an LLSD blob with the information we're interested in.

-cheers
-meadhbh

On Wed, Jan 20, 2010 at 1:24 PM, Hurliman, John <john.hurliman@intel.com> wrote:
> I’ve seen a few places in the I-Ds and OGP wiki documents that refer to a
> URI schema for a location in a virtual world (home location, requested login
> location, etc). Has this been defined or discussed yet? I see the SLURL
> format of:
>
>
>
> secondlife://region%20name/x/y/z
>
>
>
> How would this change to accommodate a location in any region domain?
>
>
>
> John
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>