Open Source License: AGPL

Wikidsmart is open source, licensed under the AGPL. If you have questions about both freedoms and constraints defined by AGPL, please consult your own legal counsel regarding the use of this license. The following comments do not constitute legal advice but rather offer a high-level layman’s interpretation of AGPL.  

AGPL allows you to use Wikidsmart for your own internal use. The only restriction is with respect to distribution. If you modify Wikidsmart and provide the modifications to another party, you must make your modifications publicly available under AGPL as well. Furthermore, if Wikidsmart code intermingles with other code, the other code becomes AGPL. Contact zAgile at if you wish to have a commercial license to overcome this restriction or if you are interested in exploring services such as an annual support subscription or consulting services.

Open Standards

Wikidsmart is based upon open technologies and open standards, principally developed and recommended by the W3C.

Semantic Web Technologies

Jena Framework
Wikidsmart’s Context Server is built upon the open source Jena Framework -- a Java-based framework for building semantic web applications, originally developed at HP-Labs and is now a top-level Apache project of the Apache Foundation.  

Wikidsmart’s knowledge model is expressed in ontologies based upon W3C’s OWL (Web Ontology Language) specification for the formal representation of concepts in a domain, their attributes and interrelationships. OWL is developed as an extension to RDF (Resource Description Framework) and is expressed in RDF/XML syntax.  


SPARQL is the W3C recommendation for a query language for querying OWL and RDF data sources.

Open Architecture

All aspects of Wikidsmart are open and extensible:

  • Wiki templates: wiki templates are included in Wikidsmart Solutions for software engineering use cases. More templates may be added for software engineering as well as other domains.
  • Connectors: Wikidsmart Connectors today are available for a number of ALM products (Confluence, JIRA, Fisheye) as well as Connectors can be added for any other tool or application.
  • Knowledge model: Today, WCS’s knowledge model (“ontology”) is designed specifically for concepts related to ALM and CRM.   However,  WCS architecture is model-independent and the underlying ontology may be extended or replaced to represent other domains such as Healthcare, Finance, and more. Example use cases include:
    • Major software vendors who wish to integrate their portfolio of acquired products in a deep, contextual way
    • Life sciences organizations who wish to have their processes and content organized around a catalog of well-defined, related concepts such as the human anatomy, biotechnology, pharmacology, etc.
    • Financial or insurance companies who require to have a comprehensive view of their many interrelated products and offerings.