[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Re: Object usage payments
- To: uu@total-knowledge.com
- Subject: Re: Object usage payments
- From: "Alexey Parshin" <alexeyp@gmail.com>
- Date: Fri, 29 Jun 2007 08:45:53 +1000
- Delivered-to: mailing list uu@total-knowledge.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:in-reply-to:mime-version:content-type:references; b=fe4lYu9itB4LVex+mbtCZBi85xosgfIUaDMNF1N8fKDqC4tRG7/8en05veDrBiU3wylvC0bgTfyV5hkY5+7FyFOm3jrF8qsynn9ZLfdcXwgy/3OYYg1hYRQo1Je1tvOAieVGDcILsfafc31B9+QDCfeYpl/mn1EM37srKB/z6wg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=sNkTkOtjLqL2Ic6aeFDsDIrOsEfmetEK1IsE45diKUr6gsI9aa6y0VRJQJhoj6WyNn270lmw7onRYAn7HM/dkmHwymkz9275BKIlJ8hcHBsZg9YBChQI8kqvyW3bWTlVMK3hJ7lHr5VX7Qz4iu5Kx48kvHJdFtb6JPZk1j228tg=
- In-reply-to: <468436CC.2010202@total-knowledge.com>
- Mailing-list: contact uu-help@total-knowledge.com; run by ezmlm
- References: <a75bc3cf0706261633p264e0cadib122e97584c7d35b@mail.gmail.com> <468436CC.2010202@total-knowledge.com>
Ok, the question is, then:
If any UMO is included into any other freely, how do the authors of the UMO get paid? In my understanding, every UMO has a price of usage (one way or another, including price = 0). In turn, if a particular UMO of one author includes some UMO(s) of other authors - the payment for that UMO should get to other authors somehow..
2007/6/29, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:
Alexey Parshin wrote:
> Gentlemen,
>
> It's time to discuss - how do authors may define the payment policy
> for their UMOs. I came up with the following potential policies:
>
> 1) Fixed payment. Once an author pays a UMO, he can use it in as many
> other UMOs as he needs. I doubt that is what the author of this UMO
> wants.
> 2) Fixed payment for any including of the UMO in one's UMO.
> 3) Periodic payment: same as 1) but with lease period.
> 4) Periodic payment: same as 2) but with lease period.
> 5) ?
From the original proposal:
---------------------------------------------
10. Following class creation rules are available:
- Fully open, accept donations: anyone can create class, if donation
of minimum
is given to author, teacher has an option to show a stamp on his
course. Not
giving a donation will show up on course as well.
- Fully open, don't care about money: anyone can create class, no
donation absence
marker will be shown.
- Payment required, perpetual: Fixed payment is made, and class
exists indefinitely
- Payment required, periodic: Flat rate payments for defined period
of time.
- Payment required, percentage: Percentage of teacher's income from
this class
---------------------------------------------
>
> These policies, of course, should be implemented as stored procs, so
> we can always define more. But I need to estimate at least the general
> requirements for them.
One important thing is: we do not bind payment to an UMO. Any UMO can be
included
into another one without limitations (except for limitations imposed by
kinds - can't make
a topic a part of a problem). With this in mind, you'll realize it makes
no sense to assign
payment to any UMOs besides course (which is the only non-shareable UMO
- you can't
include the course itself into anything else).
>
> It is more or less clear, that every non-free UMO should have an
> account. Such accounts would be created simultaneously with the
> payment policies. The absence of the payment policy indicates free
> object.
>
> A separate issue is a distribution schema. A payment(s) made to a UMO
> account, eventually (or periodically) should lead to author's payments.
> After some money paid to UMO's account, how do we distribute this
> money among the authors? We can, of course, just distribute the money
> among the author(s) of top-level object. But, is it the only schema?
The issue is not distributing money between authors of UMOs (for reasons
stated above), but between authors of a course.
We need to come up with a way to let authors come up with proper
distribution of funds between each other.
>
> --
> Alexey Parshin,
>
http://www.sptk.net
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
--
Alexey Parshin,
http://www.sptk.net