Difference between revisions of "Protecting content in an open grid"
Jump to navigation
Jump to search
Tao Takashi (talk | contribs) m (fixed layout) |
|||
| Line 17: | Line 17: | ||
* I think all participants are more or less agreeing on the fact that a strong(er) DRM is not possible to be implemented | * 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, but strong access guarantees can hold ''only within the walls of managed grids'' | ||
* | * 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 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 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) | ** 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) | ||
==related JIRA tasks== | ==related JIRA tasks== | ||
[https://jira.secondlife.com/browse/VWR-2571 VRW-2571 : Copyleft/share-alike permission for SL Items] | [https://jira.secondlife.com/browse/VWR-2571 VRW-2571 : Copyleft/share-alike permission for SL Items] | ||
Revision as of 05:06, 25 September 2007
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, but strong access guarantees can hold only within the walls of managed grids
- 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)