YES - this is a separate and VERY involved discussion!<br><br>As a content creator and retired IP lawyer I share <span dir="ltr">mysticaldemina's concerns</span>.<br><br>However, lets not lose sight of the fact that the underlying legal issues are far from settled!<br>
<br>Is a "virtual good" an "object" of some sort which is bought and sold, or is it a "work" which must be licensed, or is it some other animal entirely?<br><br>There are courts which have found aspects of all three!<br>
<br>Concepts like "fair use" and "scholarly use" are nowhere near settled for either software or virtual goods.<br><br>There have even been recent attempts to use "copyright infringement" as a from of censorship!<br>
<br>In the US, the Library of Congress (who administer many aspects of US copyright law) has issued a policy allowing legal "DRM circumvention" in certain cases.<br><br>The real life fashion industry has totally abandoned the concept of copyright and accepts "knock offs" as part of their business model. The economics work out to be very similar to virtual fashions with very much smaller numbers for both originals and copies.<br>
<br>Finally I note that many new bands are abandoning the "sell copies of our music" business model and depending on their concert revenues to pay for their art. Are they any good? Will this work? Who knows? I certainly don't<br>
<br>My point is that any DRM must exist within a framework of laws and must reflect those laws or it is totally useless.<br><br>This issue is far more than "lock the doors firmly to keep the bad guys out"!<br><br>
It does need to be discussed (extensively!) but as Melanie points out this belongs to HG V2.0 planning NOT HG V1.5!<br><br>Karen<br><br><div class="gmail_quote">On Tue, Aug 31, 2010 at 6:23 AM, <span dir="ltr"><<a href="mailto:mysticaldemina@xrgrid.com">mysticaldemina@xrgrid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi,<br>
<br>
As a content creator this concerns me. I believe if I license my content to<br>
an avatar, and then they go to another grid that any content pulled should<br>
be from the grid that I have the content loaded into. I think I should be<br>
in control of my content. I also think I should be able to block grids that<br>
my content is being accessed from. If you don't always maintain the<br>
original content location there will be no control. If I give someone a<br>
copy of my content, then that is something else, they are now the owner of<br>
it and are free to do as they please with it, at least within any license I<br>
give them. But that is a legal stuff not a technically programmed one. At<br>
least I don't expect all situations to be programmed.<br>
<br>
Also when asset services start happening this will become more of an issue.<br>
I will have XRMarketplace.com live soon and plan to start selling content<br>
and provide that content as an asset server. How will I maintain any kind<br>
of control over the use of my content if people don't have to pull copies<br>
from me?<br>
<br>
I also think, and haven't seen in the new hypergrid, if someone goes to a<br>
new grid I may not allow any of my content to go there unless that avatars<br>
gets an authorization from me which should be attached to his proxy profile<br>
for access into my grid/asset server.<br>
<br>
The other thing to think about is how updates or corrections are propagated.<br>
SL has a terrible system of only supporting copies so any updates or copies<br>
have to be sent to everyone. Seems content replacement needs to be<br>
supported and if content is all over the place this will get even crazier.<br>
Also to support dynamic content there needs to be a ways to refresh or<br>
update content. I suggest there needs to be an expiration date on the<br>
content just like how images and HTML pages on the web work so that cached<br>
content will know to pull a new copy. And if the expiration date is 0, at<br>
the time it was pulled, it will always get refreshed.<br>
<br>
This is maybe should have its own discussion thread but seems to be part of<br>
how this is all going to work.<br>
<br>
M.<br>
<div class="im"><br>
-----Original Message-----<br>
From: <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a><br>
</div><div class="im">[mailto:<a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a>] On Behalf Of Ai Austin<br>
Sent: Tuesday, August 31, 2010 4:17 AM<br>
To: <a href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
Subject: Re: [Opensim-dev] Global identifiers<br>
<br>
</div><div><div></div><div class="h5">myticaldemina makes a lot of good points... one thing that could be<br>
problematic though relates to this comment...<br>
<br>
>From: <<a href="mailto:mysticaldemina@xrgrid.com">mysticaldemina@xrgrid.com</a>><br>
>...I would suggest any<br>
>proxies would give the external system and identifier and not chain proxy<br>
to<br>
>proxy unless there is a reason to do it, and the assets should be copied<br>
>from the original source.<br>
<br>
<br>
I agree with the first half... no chains, just hand over the external<br>
system "authority" and its given identifier pair for the identity involved.<br>
<br>
But I don't agree at all with the idea that you then have to get the<br>
asset from that original authority. The permissions could have<br>
changed, corruptions could have occurred or much more likely the<br>
authority simply will no longer be there. The asset "as is" (with<br>
its textures, scripted content and what not) should be provided to<br>
the destination location/grid if the object permissions allow it,<br>
with proper transfer of the permissions to next owner exactly as if<br>
an avatar to avatar transfer or rez in world took place on the local<br>
grid, without trying to reload the asset from an original source.<br>
.<br>
<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br>