Showing posts with label NLP. Show all posts
Showing posts with label NLP. Show all posts

Thursday, 15 October 2015

Example of using SWRL built-ins with Solar System ontology.

Introduction to SWRL


Semantic Web Rule Language (SWRL for short) is a combination of OWL DL and OWL Lite sub-languages of OWL Web Ontology. It is possible to write ontology with SWRL built-ins in Ontorion Fluent Editor. One of such example of ontology written by using Semantic Web Rule Language is Cognitum's Solar System Ontology.

To follow along open Fluent Editor, go to File -> New and type Solar System. Double click on the template to open.

Monday, 16 February 2015

Using OWL Annotation in Fluent Editor

OWL Annotations together with SKOS and DcTerms form a widely used Thesaurus standard that help the ontology modeler to give meaningful names to elements of the ontology or to relates elements in various ontology. In the latest release of Fluent Editor, we have introduced the possibility to add, remove and modify OWL annotations with full support for SKOS and DcTerms. As always this has been implemented thinking of the usability over everything. 

All actions related to the annotations are reachable from the Annotation tab that was added in the right column of the Fluent Editor window. To see how to use annotations in Fluent Editor,you can open the Book Reference template. To see the template, click on File -> New  and then Book Reference.

Sunday, 15 February 2015

Collaborative ontology editing with the use of Fluent Editor and the Ontorion Server

In the latest release of Fluent Editor, we have implemented a simple and intuitive way for multiple users to edit the same ontology at the same time. This is possible by using the functionalities of both Fluent Editor and Cognitum's scalable knowledge management system Ontorion. In this article we will try to give you a general understanding of how this concurrent editing of ontologies is working.

As a comment we would like to stress that the component that we will show you has been implemented in C# using the Ontorion API (that is part of the Ontorion Server). If thus have access to the Ontorion API and Ontorion Server, you can implement all functionalities that you see in this article in your custom program. For more information about Ontorion Server and the Ontorion API you can contact us here.

First of all open Fluent Editor, click File, Open&Import , Ontorion Server and then Connect to Ontorion.

Monday, 2 February 2015

Fluent Editor's Interoperability with Protégé

Protégé is a great tool for editing ontologies allowing deep insight into the structure of the OWL ontology. Fluent Editor allows user to focus on actual meaning of the ontology (taxonomy, vocabulary, rule set, etc) being edited.
From the R2 release, Fluent Editor enables you to view and build ontology with both applications synchronously, through which you can enjoy those great features of both applications at the same time. This is supported by two related functionalities. -  exporting ontology from one window to the other, or importing ontology from the opened window to your current window. In this post we will look through how you can utilize this feature.


Initial Settings
By default, this interoperability with Protégé is disabled. In order to enable it, first you need to edit settings of the Protégé plug-in on Tab > Options as shown below. Set "Yes" for enabling the plug-in and enter your Protégé path on the bottom.


Monday, 19 January 2015

Mixing Text Mining with Semantic Technologies - sample application.

The very broad subject of processing the natural language is incredibly hot nowadays. In many cases, a regular text mining approach is not adequate to the problems that we are facing. Therefore text mining methods are mixed with Natural Language Processing(NLP) methods, like also, with semantic technologies - what gives better results. One of such a problem is how to find out, if two sentences are semantically equal or not.

The solution for the above problem could be used on many fields. One of them is detection of an abusive clauses inside a contract. Sometimes it's really hard to understand correctly, the exact meaning of a clause inside a contract, even for a specialists. For a sake of presentation I have developed a simple application prototype which attempts to solve this problem. Application was developed in C# and it uses Ontorion SDK.

Input

Before running the application we need three files:
  1. File with contract in which we will attempt to detect abusive clauses.
  2. File with abusive clauses.
  3. File with ontology.