[Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db

[Stefan Andersson]

Last time this was up for discussion, I suggested we have a 'BinaryItem' with a 'BinaryId' that could well be a sha-1 and be used for de-duplication. This would be hashed on the binary data only, and would not have anything like 'name' or 'owner'.
 
then an 'AssetItem' would have a unique 'AssetId', context information like 'CreatedDate' and 'CreatedBy' and then a binaryId pointing to the common binary data.
 
If this feels difficult to handle, it would be a simple thing to create a combined 'view' in the database.
this is akin to the case of 'InventoryItem' with unique 'InventoryId' where several users can have the same asset, but under different name (and with different permissions)
 
Also note that the binaryId probably would be a local reference only, ie, never shared over any trust boundary.
Best regards,Stefan AnderssonTribal Media AB Join the 3d web revolution : http://tribalnet.se/ 



> Date: Mon, 23 Jun 2008 18:13:13 +0100> From: melanie at t-data.com> To: opensim-dev at lists.berlios.de> Subject: Re: [Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db table> > Hi,> > Sean Dague wrote:> > Let's seperate the use case you have, from the way you would implement> > it on top of the existing system, which is wasteful in a bunch of ways.> > The use case is to track inventory generations of the same asset. I> > think that would be much better done by adding a field to inventory> > which is seeded on a new upload. Inventory transfers/copies keep that> > seed.> > That would only handle agent inventory. It would not handle textures > applied to prims, or used in clothing, or audio files referenced by > UUID from a script. Basically any asset that gets detached from > inventory becomes untraceable.> > The problem is this:> > User A uploads a texture. She creates a skin, which she sells.> > User B uses a ripper to clone the appearance of a person wearing > that skin. They extract the texture, and download it.> > They then proceeed to reupload the texture, create a skin from it, > and sell that.> > Person A files a DMCA complaint, which results in a takedown order. > If upload coalescing were in effect, those skins would use the same > UUID. There would be no way to destroy the skins that were created > from the copy and leave the ones created by the original creator > unharmed.> > If one upload = one asset, all I need is to replace the image data > with a "missing image", or, as Neb suggested, "Missing Ethics" > bitmap. All items created from it are instantaneously unwearable.> > All builds a stolen building texture is used on would then show that > replacement image, e.g. be unusable. The DMCA takedown would be > compiled with.> > With coalescing, there is no way that can be done, I would have to > remove the asset, which will destroy all builds/items created by the > legitimate creator as well. She would have a lot of very angry > customers.> > For those who want coalescing to save space, by all means, put it > in, but please leave the option for one upload = one asset. The > legal implications or business could be tremendous if that option is > taken away, negatively impacting all commercial grids.> > Melanie> > _______________________________________________> Opensim-dev mailing list> Opensim-dev at lists.berlios.de> https://lists.berlios.de/mailman/listinfo/opensim-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080623/74861ac6/attachment-0001.html>