MOSLA is a compentized framework for End User License Agreements and some similar standardized agreement contracts which has compentized the different types of clausese that the two parties agree to.
- Each clause contains a set of fixed attributes which are meant to be human readable in a very short period of time.
- Allows each party to completely describe full MOSLA as a URL. e.g. posla.org/posla?clauses=A1.02&C14.02&D01.11&party1=John.Smith&partry2=ABCorp
- Traceability - as different clauses are litigatated or updated the legal reasoning and outcomes can be shared with the community and information attached to the clauses in the publicly available distribution.
A demo is hosted here: MOSLA Demo
All source code, including this documentation is hosted on github here: MOSLA
MOSLA is designed to be used by any company wishing to have a standardized license agreement. When displaying a EULA or service terms page a link to the MOSLA site (with party names) can be used and also emailed to the client so they have a stable copy.
Q: Why can't we just use an existing EULA or similar agreement A: You can - nothing in this prevents that - the purpose is to create a rigid standardized framework for agreeing to very common web and application clauses.
Q: I can use 90% of the clauses but I need to add a couple custom clauses. Why isn't this supported? A: By design a committee process is used to add new approved clauses or to updated existing ones. This insures that users of the MOSLA always get standardized clauses which have been vetted by large audience. If you wish to have a new clause added then submit this and the reasoning to the community process for future inclusion.
Q: How is existing named clause changed? A: As long as the clause addresses the same type of contractual issues, then the new update is submited as a change number (once approved). For example: A17.01 becomes A17.02. While the change is not yet approved you will see draft forms such as A17.02x1 (x means experimental) A17.02x1 and finally A17.02c (candidate for final review). Once a new version of the clause is finalized it is published as A17.02 without any suffixes. Note that the old version A17.01 is still valid and is still available to the community in its unchanged form.
Much work has been done on standardizing various agreements in industry. Please visit the Open Source foundation (www.opensource.org) for how this has been done for copy left software.
(OSI Approved BSD 2-clause)
Manjirnath A Chatterjee
Kona F Pance