Java Specification Request on Community Currencies
bernfast writes "I've submitted a Java Specification Request on complementary currencies to the Java Community Process. This specification will allow to implement arbitrary units of exchange as Java currencies. Examples are timedollars and other community currencies.
This JSR is still in need of an expert group and will probably not receive too much industry suppport, so any help from the open source community is welcome."
Why is this being made a java-specific thing? I would much rather see this generalized. Making it language-specific limits its use, especially in the industry... as much as most of us hate MS, we have to admit that being able to use something in C# as well as other languages is a big selling point.
Disconnect and self-destruct, one bullet at a time.
or does anyone else find it funny that a slashdot comment is linked to in a JSR?
BSD is for people who love UNIX. Linux is for those who hate Microsoft.
Doesn't seem like a spec, a process or anything you would package or get certified. Just sounds like someones idea?
How about you signup at http://www.sourceforge.net and launch your program there and use the available j2ee protocols to design your application?
Mostly true.
If you have a currency that is bought and sold, in the US, it must be pegged against the US dollar, and it must be reported as income.
However, if your currency is strictly tied to time (something like "1 fanastibuck = 10 minutes"), and you prohobit trading for money, then you do not have to pay taxes on it.
(If I understand correctly.)
Most serious groups doing this stuff know about the rules, and abide by them.
The only problem is, it is written in C so you may not like it. ;)
Seastead this.
See for example Margrit Kennedy's 140-page book Interest and Inflation free Money - you'll never look at money the same way again after reading the first chapter.
Trusted Computing FAQ | Free Dawit Isaak!
FWIW, many large organizations use fake monetary units in their accounting systems, often because the conversion rate to real currencies depends on factors that are not easy to control.
For example, supposing you buy (for a fixed price) a share of the total compute time on a supercomputer. How many minutes of CPU time is that a month? Well, that really depends on how much unscheduled down-time there is (ideally none, but this is the Real World here) and you won't know how much that is until the end of the month, and hence you won't know (for reselling purposes) how much each of those minutes of CPU time actually cost you. The easiest way to do that is to charge CPU minutes in a fake currency and reconcile that to real money every so often. You could try monetarizing up front, but that's very tricky to get right and likely to end up with either your customers cross for overcharging or your management furious for undercharging...
"Little does he know, but there is no 'I' in 'Idiot'!"
There is a more general proposal alreay out there:
... units package supports programatic unit handling via an abstract Unit class, run-time checking and conversion, unit arithmetic, unit parsing and formatting, and a units database.
http://jcp.org/en/jsr/detail?id=108
108 Units Specification
The