Re: [mmox] Permissions (Gareth Nelson)

Essentially, you'd need to look at each sub-component and then
evaluate what the restrictions are, applying the restrictions on
sub-components to the collected whole (since they're part of the
whole).

Or you could ignore it. Ask your own sense of ethics and your lawyer
what the right thing to do is.

I'll restate again that this proposal was NOT aimed at a solid
implementation of something which can actually be enforced, but as a
very expressive means of indicating the license terms in a
machine-readable form. Following discussions, it appears that the
general attitude is that there is other previous work in this area so
i've actually withdrawn my proposal.

On Mon, Feb 23, 2009 at 8:25 PM, William George
<wjgeorge@dceo.rutgers.edu> wrote:
> Nice first step, but it's not clear how this would handle composite objects:
> objects that have two different creators and/or permissions settings. The SL
> convention of using the root prim's permission for the entire object leads
> to restrictions concerning the reuse of "no mod" sub assemblies in a larger
> assemblies.
>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>
>