<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">If I may say, the way we're looking at
and treating assets / content is quickly becoming outdated in the
world outside of this little micro-chasm we call Virtual Worlds.
There are many sites out there that allow you to share and sell
content created in the standalone designers such as Maya, Blender,
etc. And with each, upon acquiring that content you agree to a
license which is often attached to the file itself. With some,
you own it outright. With others, you're limited to merely using
/ customizing it and are forbidden to distribute. And with
others, its just a matter of simply citing your source when using
the creation.<br>
<br>
Either way, its far more complicated and in a way more advanced
than ticking a combination of three check boxes then tossing in
some 12 page mention buried in your grid's TOS written in high
legalese explaining what the user can or cannot do. These days
there are two types of assets / inventory available. Those that
users create and use for themselves (private) - and those that are
distributed in one form or another inside, out of, or between
worlds. <br>
<br>
Surprisingly enough, this seems awfully familiar to me in dealing
with mono / .net dll libraries in that each has meta-level tags
for creator, owner, _license_, version, etc. In fact, in
watching the OpenSim commits just the other day I saw a few fly by
that included data marking libraries such as OpenSim.Core.Whatever
as created by "OpenSimulator Project", "BSD License", "(C)opyright
OpenSimulator.org". <br>
<br>
In short, a DLL is a component / library / creation that can
distributed and used in file form with whatever application the
developer needs. <br>
<br>
An asset / inventory item is a component / creation that too can
be distributed and used in whatever form that a developer (in this
case user, builder, scripter, texture artist, grid owner, etc) can
include and use as needed. <br>
<br>
It really would seem to me that its just a matter of adding in a
bit of meta data to the asset objects, then hooking in a minor bit
of drm into the system that would restrict import / export based
on a set of flags in combination with the standard copy / mod /
transfer bits such as "no export, grid only, etc." <br>
<br>
Of course, there may be an issue with existing content - hooking
all of this in system wide, etc. But all of us here are
brilliant, creative, and innovative individuals. I know that some
sort of systemic solution can be formed that would work for the
greater good and cover all use cases.<br>
<br>
Thanks, :)<br>
<br>
- Orion Pseudo / Fhang / Whatever my name is by now. @.@<br>
<br>
<br>
On 11/15/2012 10:23 AM, Mike Chase wrote:<br>
</div>
<blockquote
cite="mid:060701cdc345$2542ffc0$6fc8ff40$@alternatemetaverse.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Actually,
as the creator of an item I own it. Not the “user”. That’s
clear because I get to set the permissions under which the
next “owner” or licensee can use it. When someone acquires
an digital asset I created they get a license to use it.
The value of the creation itself usually far exceeds what
someone pays for it. I only create in grids I trust
because the grid operator must defend my rights via a DMCA
process. So no a “user” doesn’t have rights to copy items
in inventory they “own”. Because ownership of digital
assets doesn’t transfer. Only a license to use them for a
purpose.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So
in short I think some of your thinking about users “rights”
is somewhat flawed. That doesn’t meant there aren’t
protocols to do what you want to do. But yeah, I think
providing such a tool is asking to get sued. And it probably
damages the reputation of OpenSim as serious software for
serving digital assets. That’s a shame because there are a
number of closed grids trying to actually correct that
assumption by providing a more secure environment for
content creators to operate in. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Just
my 2 cents. Do what you will with it<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:opensim-users-bounces@lists.berlios.de">opensim-users-bounces@lists.berlios.de</a>
[<a class="moz-txt-link-freetext" href="mailto:opensim-users-bounces@lists.berlios.de">mailto:opensim-users-bounces@lists.berlios.de</a>] <b>On
Behalf Of </b>Snowcrash Short<br>
<b>Sent:</b> Thursday, November 15, 2012 7:51 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</a><br>
<b>Subject:</b> Re: [Opensim-users] Announcement of
inventory tool (MyInventory), mostly of interest to grid
operators/grid nauts<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Before this gets out of hand, let me
clarify, this is not a backup tool, at least no per se, one
of the features is the ability to backup content from an
existing account (a backup which is governed by a policy).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The primary goal of the project is to
move the inventory and the assets to their rightful users
and to empower the users to use the assets as they want -
within legal limits.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In an ideal world - except for special
cases, the inventory and the assets backing the inventory is
controlled by the user, and that is the goal of the project,
to bring the inventory under the control of the user.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To this purpose it currently has two
input streams supporting it (one more is planned), the first
is client side access to .iar files, the second is download
from the users existing inventory, to the extent allowed by
law and agreements made between the user and grid operators.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Knowing that only a few of the grid
operators using Open Sim has policies in place, this email
serves as an invitation to make these policies public, and
to implement - to the extent possible - these policies in
MyInventory.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The question of attribution is only
relevant when the assets are being distributed, MyInventory
has currently no functionality for distribution. The as yet
unfinished and only hinted at third input stream deals with
distribution. The current implementation does not distribute
any data, it only grants a user simpler way access to the
assets the user has rightfully access to.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Snowcrash<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Opensim-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</a></pre>
</blockquote>
<br>
</body>
</html>