semantic_manager

DAF

• semantic_manager
  • semantic repository API
    • dependencies: triplestore(s)
  • semantic ontonethub API
    • dependencies: stanbol (solr)
  • semantic validator API
    • dependencies: triplestore(s)

---

HTTP API

getting a list of ontologies metadata

Using the endpoint /kb/v1/ontologies it's possible to retrieve some metadata about each ontologies, for example using the following CURL command:

curl -X GET 'http://localhost:9000/kb/v1/ontologies' \ 
	-H  "accept: application/json" -H  "content-type: application/json"

For each ontology the service will return a summarization of useful metadata, such as a brief description, the reference to the original source uploded to the catalog, as well as some general information about its usage (number of triples, number of concepts, and so on).

finds a list of standard properties, by term

The endpoint /kb/v1/ontologies/properties/find provides a list of properties from the core vocabularies and ontologies in the catalog, depending on user input terms and choosen language, as shown in the following example CURL command:

curl -X GET 'http://localhost:9000/kb/v1/ontologies/properties/find' \
	-d 'query=nome' \ 
	-d 'lang=it' \ 
	-H  "accept: application/json" -H  "content-type: application/json"

This will help during the ingestion phase, when a user need to decide how to mark a dataset field in the form provided by DAF with a standardized ontology/concept/property reference.

---

instructions

0. adjust configuration

   Currently the configurations for semantic_repository have been added into a section inside the general conf/application.conf file:

   # general configurations
   clients {
   
   	ontonethub {
   		host: localhost
   		port: 8000
   		follow_redirects: true
   		pause: 1000
   	}
   
   	...
   }
   

   At the moment the host/port configuration of external endpoints can be changed from the configurations.

1. compile / package

   $ sbt clean package

2. run

   $ sbt run 

3. (local, manual) deploy

   $ sbt clean dist
   $ unzip -o -d  target/universal/ target/universal/semantic_manager-0.0.1.zip
   $ cd target/universal/semantic_manager-0.0.1
   $ bin/semantic-repository -Dconfig.file=./conf/application.conf
   

   NOTE: if the application crashed for some reason, the pid file whould be deleted before attempting re-run

   $ rm target/universal/semantic_manager-0.0.1/RUNNING_PID 

4. release

TODO

6. preparing docker image with sbt (manually)

   $ sbt docker:publishLocal 

   after this command, will be generated an image including the deployed application, and published on the local docker system. The generated image should be used for starting a new container, exposing the ports with a command similar to the following one:

   $ sbt docker run -d -p 9000:9000 {docker-image-id}
   ``
   
   
   
   

---

TODO [2017-09-22]

• refactorization / rewrite of API for OntonetHubClient
• refactorization / rewrite of API for SemanticRepositoryClient
• alignment between API
• more test coverage!
• REVIEW of documentation (including this README!)
• automatic guessing of MIME type from RDF file
• automatic extraction of description from RDF file
• improve documentation