Protecting content in an open grid
Revision as of 02:58, 25 September 2007 by Tao Takashi (talk | contribs) (tried to summarize the discussion on sl-dev about DRM, IP etc.)
Discussion on the mailing list
Unfortunately the archive messed up and the permission thread is all over the place, but here are some link from which you might want to follow downwards the stream: (probably also happens due to keyword juggling in the subject)
- https://lists.secondlife.com/pipermail/sldev/2007-September/004637.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/004652.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005065.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005086.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005104.html (a content creator's view)
- https://lists.secondlife.com/pipermail/sldev/2007-September/005128.html (cont'd)
- https://lists.secondlife.com/pipermail/sldev/2007-September/005144.html (cont'd)
Basically it's the September archive.
Summary
- I think all participants are more or less agreeing on the fact that a strong(er) DRM is not possible to be implemented
- permissions are here to stay
- new permissions migth be needed such as
* allow an asset only to be used inside one region domain * allow an asset only to be used inside one grid (= list of trusted region domains) * allow an asset only to be used inside a set of region domains with certain security certificates (sort of an implemention though though)
- it should also made sure that full-perm assets stay full perm, such as a GPL-style license.
- it should be possible to make your intent more clear. One way is due permissions but a more detailed way might be an additional license field (for e.g. CC licenses)