FAQ

TaxisDB + TaxisBase Licensing FAQ

What does it mean that TaxisDB is licensed under SSPLv1?

The Server Side Public License (SSPLv1) is designed to ensure that if you use TaxisDB as part of a service you make available to others (e.g., in the cloud or as an API), you are required to make the source code of your complete service available under the SSPLv1 license. This is similar to GPL but extends to server use.

Can I use TaxisDB in my internal projects without open-sourcing my code?

Yes! If you’re using TaxisDB for internal purposes only, within your organization without providing it as a service to external users, you are not required to open-source your code.

Can I use TaxisDB in my closed-source project without open-sourcing the entire project?

If your closed-source project does not make TaxisDB available to external users as part of a service, you can use it without open-sourcing the rest of your code. However, if you provide TaxisDB as part of a service, the SSPLv1 requires you to open-source your codebase associated with the service.

How does the SSPLv1 license affect my commercial application that uses TaxisDB?

You can use TaxisDB commercially, but if your application provides TaxisDB as a service to users, then under SSPLv1, you must open-source the code that enables this service. For companies needing a commercial license to avoid this requirement, please contact us to discuss options.

What if I want to use TaxisDB in my product but don’t want to release my source code?

If you’re providing a service with TaxisDB and prefer not to release your source code, reach out to our team. We offer commercial licensing options that can accommodate these needs without the open-source requirement.

Can I modify TaxisDB under the SSPLv1 license?

Yes! You’re welcome to modify TaxisDB under SSPLv1. If you distribute a modified version as part of a service, however, the SSPLv1 requires that you open-source your modifications.

Can I redistribute TaxisDB in my applications without following SSPLv1?

If you redistribute TaxisDB as part of an application that does not make it available as a service, you do not need to open-source your code. But if you’re using TaxisDB as part of a public service, SSPLv1 obligations apply.

What should I do if I’m unsure whether SSPLv1 affects my use of TaxisDB?

We’re here to help! If you have questions about specific use cases or licensing terms, feel free to reach out to our team for guidance.

Is TaxisDB free to use for evaluation and prototyping?

Yes, you are free to use TaxisDB under SSPLv1 for evaluation, prototyping, and internal testing without needing to release your source code, as long as it’s not provided as a public service.

What is the difference between TaxisDB and TaxisBase?

TaxisDB is the database engine that stores, manages, and queries data. TaxisBase is the open knowledge base, database model, ontology, and initial database contents used by TaxisDB. They are licensed separately because they are different components of the platform.

Why are TaxisDB and TaxisBase licensed differently?

TaxisDB is software and is licensed under the SSPLv1. TaxisBase is an open collaborative database and is licensed under the Open Database License (ODbL), while its individual contents are licensed under the Database Contents License (DBCL). Each license is designed for the type of work it governs.

Can I use TaxisBase without using TaxisDB?

Yes, although not directly in its native form today. TaxisBase is currently stored using TaxisDB’s internal data structures on YottaDB. If you wish to use TaxisBase with another database or knowledge platform, you would first need to export it to a standard interchange format (such as RDF, OWL, JSON-LD, or another supported knowledge representation format).

The ODbL and DBCL licenses allow you to use, transform, and migrate TaxisBase to other platforms, subject to their terms.

Can I use TaxisDB without TaxisBase?

No. TaxisDB is designed to operate together with TaxisBase. TaxisBase defines the core ontology, type system, semantic model, constraints, relationships, and other metadata that TaxisDB relies on for its operation.

While additional knowledge, ontologies, and application-specific models can be added to TaxisBase, the core TaxisBase knowledge base is an integral part of the TaxisDB platform and is required for normal operation.

What is considered an adapted TaxisBase database?

An adapted database is a modified version of TaxisBase. Examples include extending the ontology, adding new entity types, introducing additional relationships, defining new constraints, or enriching the database with new entities and asserted facts.

Do I have to publish my changes if I modify TaxisBase?

No. You may keep your modified TaxisBase database private. ODbL Share-Alike obligations generally apply when you publicly distribute an adapted TaxisBase database.

Does the ODbL apply to TaxisDB software?

No. ODbL and DBCL apply only to TaxisBase as a database and its contents. The TaxisDB software engine is licensed separately under the SSPLv1.

Does the SSPL apply to TaxisBase?

No. The SSPLv1 applies only to the TaxisDB database engine. TaxisBase is licensed under ODbL and DBCL.

Who owns TaxisBase?

The ODbL grants broad rights to use, modify, and redistribute TaxisBase, but it does not transfer ownership of the project or its trademarks.