- To: email@example.com
- Subject: UMO' license
- From: "Alexey Parshin" <firstname.lastname@example.org>
- Date: Wed, 27 Jun 2007 17:47:49 +1000
- Delivered-to: mailing list email@example.com
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=tZncG2YG3RvBHlGHjEpMA8h7b9ERHY54R85o30xqXYR24Yc1dZM/7mOFvyyUsX6qKfrUlToGl7glUeIii3jEVtNbP9NGQlM0U564jkvc8KJW4Um7G9WsjzxI87t7gEVGpicks91VZQtFxs21WATXvIKQDmI190EcNzYLxcJ7B4c=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=oPcUQwPVpZFxyTo4kIZki8Bpb0iNgYWn+5HvZL+nNNBbDC8CaDWCnLBtRBMwHXQpj6ulBiWKarvTQXrvRoM9iQrJRG5GjIzYEFqA9WsI6Zs/jl+/HiTUmtgxmQEKUkBHE4PVkLF1xdJB/z4fo8RIp1ojz2wjdYUc1ec1lOVD/iw=
- Mailing-list: contact firstname.lastname@example.org; run by ezmlm
I'm thinking about new entity, 'license_type' that would cover the current UMO license algorithm. This is similar to subscription mechanism, and also accompanied with license_parameter_template (for constructing a Web page) and object_license_parameter (that contains actual object parameters).
For a free license, the license uses a simplified algorithm that does nothing :)
For other types of licenses, the license algorithm will use the same approach, as we use for subscription. As result, the funds from author's account would move to the UMO' account he's trying to use.