[Opensim-dev] Legal Issues was RFC Profiles

[Andrew Yourtchenko]

On Tue, Mar 31, 2009 at 11:22 AM, Frisby, Adam <adam at deepthink.com.au> wrote:
> Well, you /could/ use hashing to define the license text, but honestly? A URI works better. Really, just making it complicated in order to have a UUID really isn't ideal.
>
thought more - and my hashing idea was pretty bad in a sense that it
did not solve the problem completely.

but i think what might be happening is that everyone has different
class of the problem in mind, in which case we could discuss for quite
a long time ;)

is the problem:

a) "thank you for making your purchase. Oh by the way - if you don't
wipe your butt with this texture, would be awesome".
b)  "why are they suing me ? these textures chased me themselves!
honest! which textures you are talking about ?"
c) { c = malloc(5); strcpy(c, "sale"); give_to_user(c); strcpy(c,
"rent"); go_to_court(c); }
d) "oh Ms. $Hollywood[rand()], we are sorry our user giving out your
nude photo, no, if you sue we are bankrupt"
e) "hmmm did this guy _really_ build this texture he is selling? looks
too good compared with the rest"

A couple of those I made from theoretical examples in the paranoid
head, the rest I tried to summarize my understanding of others'
posts... and those have varying requirements, so would it be useful to
give a 160-character description per each one that is missing in he
above list ? then we could see what's the scope of the "Licensing
support" issue and how it could be chopped down into chewable pieces ?

Of course, if all everyone wants is the extra field in the DB and
firing up the browser with that URL each time the asset crosses
"hands", that's would be my last mail on the subject :)

cheers,
andrew