Hi, that is a truly secondary concern to me. It is outright illegal to transfer items, creator information or not, unless the creator agrees and cooperates. In this rare case, the creator would register on the destination grid and then have a name and profile. A means of preserving SL creator identification would just foster the belief that copying things from SL is legal "because the creator stays the same". Most content in SL is not released under a Creative Commons/BSD/Share-attribution license, it is released under much more restrictive licenses. No maingrid content is allowed to leave the maingrid unless the creator or legal copyright holder transfers it.
Melanie James Stallings II wrote: > There are some strong ideas here for the future, but I think that the > original problem has been lost in the mix (or perhaps I missed something in > the thread, not entirely out of the question ;) > Unless I am mistaken, the real problem is older content imported from SL - > how to preserve the creator ID of such content? > > The scenario, I am sure, is not unfamiliar: > > OS user purchases full rights content on the Linden Grid; OS user, through > hook or crook, imports said content, because he has no intention of ever > using it on the Linden Grid; creator of said content discovers that the > content has been relocated and cries foul because his/her creator > identification has been 'removed'. > > While the foregoing discussions itt address the potentiality of this > scenario as it would occur when the content originates on an OS grid, what > do we do about preservation of the ID of the creator of content from that > distant but arguably compatible foreign grid we all know and love so well? > > Cheers > James/Hiro/daTwitch > > On Mon, Mar 30, 2009 at 7:08 AM, Sean Dague <[email protected]> wrote: > >> Melanie wrote: >> > I am absolutely sure that I would not went HG to ever, EVER, insert >> > user records or profile records into my database. I strongly favor >> > the "URL" approach, which is neutral as far as my database goes. >> >> Ok, so then hash those urls for UUIDs to present to the viewer? We >> still need a UUID in the object definitions for the viewer so that >> people can see the creator. >> >> -Sean >> >> -- >> Sean Dague / Neas Bade >> [email protected] >> http://dague.net >> >> >> >> _______________________________________________ >> Opensim-dev mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/opensim-dev >> >> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
