https://github.com/deftio/mosla
https://github.com/deftio/mosla
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/deftio/mosla
- Owner: deftio
- Created: 2019-08-22T06:03:40.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2025-05-24T00:48:09.000Z (about 1 year ago)
- Last Synced: 2025-05-24T01:24:20.371Z (about 1 year ago)
- Language: HTML
- Size: 284 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[](https://opensource.org/licenses/BSD-2-Clause)
# MOSLA - Modular Open Services License Agreement
Navigating legal agreements for online services can be complex, often involving dense, custom-written documents that are difficult to understand and standardize. MOSLA (Modular Open Services License Agreement) addresses this challenge by providing an open, **standardized**, and **component-based framework**. It allows for the construction of clear, predictable contracts—such as End User License Agreements (EULAs) and service agreements—by selecting from a library of pre-defined, community-vetted clauses. This modular approach simplifies agreement creation and comprehension, with the added benefit of agreements being easily shareable and embeddable via a simple URL.
## Features
* 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.
## Prototype / Demo
A demo is hosted here: [MOSLA Demo](./MOSLA.html?terms=demo)
All source code, including this documentation is hosted on github here: [MOSLA](https://github.com/deftio/mosla)
## Usage
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.
## FAQ / Questions
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.
## Acknowledgements
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.
We also thank our [Contributors](contributors.md).
## License
(OSI Approved BSD 2-clause)