<commit_before>
lod_manager
===============

SEE: [teamdigitale/daf](https://github.com/teamdigitale/daf) 

## instructions

1. local publish of dependencies (`kb-core`)

At the moment the wrapper for the triplestore(s) is published as a jar dependency, using the `lib` folder:

```
[lod_manager]
├───/lib
│   ├───eclipse-rdf4j-2.2.1-onejar.jar
│   └───kb-core-0.0.1.jar
```
Copy the library under `/lib` before compilation (NOTE: the libraries should be managed too by sbt).

2. compile / package

```
$ sbt clean package
```

3. run

```
$ sbt run 
```


* * * 

## TODO 

- [ ] publish `kb-core` on github / bitbucket or as sub-module
- [ ] add `kb-core` dependency on sbt 
- [ ] add `RDF4J` dependencies on sbt (if needed)
- [ ] proper configuration of JUnit for sbt
- [ ] more test coverage for simple example HTTP requests
- [ ] RDF4J connection pool, with implicit connection as curry method


### RDF4J connections (IDEA)

An idea could be rewriting methods as curried, in order to add implicit connection, such as:

```
def action(params...)(implicit conn:RepositoryConnection){
	...
}
```

this way we could avoid open/close a connection every time, instead maintaining a connection pool
<commit_msg>refactoring: removing old components, fixing bugs. TODO: more refactorization, with newver version of the RDF wrapper library<commit_after>
lod_manager
===============

SEE: [teamdigitale/daf](https://github.com/teamdigitale/daf) 

## instructions

1. local publish of dependencies (`kb-core`)

~~At the moment the wrapper for the triplestore(s) is published as a jar dependency, using the `lib` folder:~~

```
[lod_manager]
├───/lib
│   ├───eclipse-rdf4j-2.2.1-onejar.jar
│   └───kb-core-0.0.1.jar
```

~~Copy the library under `/lib` before compilation (NOTE: the libraries should be managed too by sbt).~~

**NOTE** : for simplicity the library sources have been merged into the main repository.

**TODO** : find a better way to manage the engine part as an external library: for example it could be helpful to have a specific git repository, and an sbt dependency importing the jar. This way the engine could be more easily re-used for other services such as validators, etc.

2. compile / package

```
$ sbt clean package
```

3. run

```
$ sbt run 
```


* * * 

## TODO 

- [ ] publish `kb-core` on github / bitbucket or as sub-module
- [ ] add `kb-core` dependency on sbt 
- [ ] add `RDF4J` dependencies on sbt (if needed)
- [ ] more test coverage for simple example HTTP requests


{'fraction_non_alphanumeric': 0.1312, 'fraction_numerical': 0.0096, 'mean_word_length': 3.8657587548638133, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1480227', 'n_tokens_mistral': 823, 'n_tokens_neox': 789, 'n_words': 310}