Skip to main content

Developer Friendly How to Comply Quick Guide

License
TaxisDB Platform — Simplified Compliance Guide

This guide is a practical summary for developers. It does not replace the license texts.

  • TaxisDB EngineSSPLv1
  • TaxisBase Knowledge BaseODbL v1.0 + DBCL v1.0

1. If you modify the TaxisDB engine

You must:

  • Release distributed modifications under SSPLv1
  • Keep copyright and license notices
  • Keep trademark notices intact
  • Comply with all SSPLv1 obligations

TL;DR: If you distribute a modified TaxisDB engine, your modifications must comply with SSPLv1.

2. If you build an application using TaxisDB

You may:

  • Build desktop applications
  • Build web applications
  • Build mobile applications
  • Build enterprise software
  • Build internal tools
  • Keep your application closed-source, provided you are not offering TaxisDB itself as a hosted database service

TL;DR: Applications built on TaxisDB may remain proprietary unless SSPLv1 service obligations are triggered.

3. If you provide TaxisDB as a hosted or cloud service

You must:

  • Comply with SSPLv1
  • Release the complete source code of the service required by SSPLv1
  • Keep license and copyright notices
  • Follow the Trademark Policy

This includes the software required to provide the hosted TaxisDB service.

TL;DR: Offering TaxisDB as a service requires compliance with SSPLv1 service-source obligations.

4. If you modify TaxisBase

You may:

  • Extend the ontology
  • Add new entity types
  • Add attributes
  • Add relationships
  • Add constraints
  • Add entities
  • Add facts (datoms)

If you publicly distribute an adapted TaxisBase database, you must comply with the ODbL Share-Alike requirements.

TL;DR: Private modifications are allowed. Publicly distributed adapted databases must remain under ODbL.

5. If you redistribute TaxisBase contents

You must:

  • Comply with ODbL
  • Comply with DBCL
  • Preserve required attribution
  • Preserve licensing notices

TL;DR: The database model and contents remain open under ODbL + DBCL.

6. If you want to keep a hosted service proprietary

You need a Commercial License.

Typical examples include:

  • Proprietary cloud database services
  • Closed-source managed hosting
  • Enterprise hosted platforms
  • OEM deployments
  • Embedded commercial products

TL;DR: Proprietary hosted TaxisDB services require a Commercial License.

7. If you want to use the project names or logos

You must follow the Trademark Policy.

In particular:

  • Do not imply official endorsement.
  • Do not use official branding for forks.
  • Do not use TaxisDB or TaxisBase as product or company names without permission.

TL;DR: Open-source licenses do not grant trademark rights.

8. If you want to contribute

Please:

  • Follow the project’s contribution guidelines
  • Follow the Code of Conduct
  • Sign the Contributor License Agreement (CLA), if required

TL;DR: Follow the contribution process before submitting changes.

9. If you’re unsure

Please contact the Project owner.
Email: Athanassios

TL;DR: When in doubt, ask first.

📌 Ultra-Short Summary

TaxisDB (SSPLv1)

  • Internal use is allowed.
  • Applications using TaxisDB may remain closed-source.
  • Modified distributed engines must comply with SSPLv1.
  • Hosted TaxisDB services must comply with SSPLv1 service obligations.

TaxisBase (ODbL + DBCL)

  • Use, modify, and extend freely.
  • Publicly distributed adapted databases must comply with ODbL Share-Alike.
  • Individual database contents are licensed under DBCL.

Commercial License

Required if you want to offer a proprietary hosted TaxisDB service without complying with SSPLv1 service obligations.

Trademarks

The licenses do not grant rights to use:

  • TaxisDB
  • TaxisBase
  • Official logos
  • Project branding

See the Trademark Policy for details.