New data warehouse strategy (graph): RDF/SPARQL graph database populated with dictionaries data (experimental feature) #41
Description
- Related issues
- New exported format: Simple Knowledge Organization System (SKOS) (Basic implementation or better); RDF on Turtle New exported format: Simple Knowledge Organization System (SKOS) (Basic implementation or better); RDF on Turtle #38
- Organization strategy to deal with numeric namespace of dictionaries which are handled at administrative level Organization strategy to deal with numeric namespace of dictionaries which are handled at administrative level #39
- Another strategy
- New exported format: SQL database populated with dictionaries data (experimental feature) New data warehouse strategy [tabular]: SQL database populated with dictionaries data (experimental feature) #37
- Related software and concept
- https://en.wikipedia.org/wiki/Knowledge_graph
- https://en.wikipedia.org/wiki/Linked_Data
- https://en.wikipedia.org/wiki/Semantic_interoperability
- https://en.wikipedia.org/wiki/Triplestore
- https://en.wikipedia.org/wiki/Named_graph
- https://en.wikipedia.org/wiki/SPARQL
- https://en.wikipedia.org/wiki/OGC_GeoSPARQL (need different issue)
- Related software
- List of softwares
- Some open source software
The way we organize the dictionaries entry point for some time already is very regular, and after the #38, there's no reason to we start to do practical tests.
To Do's of this minimal viable product
Export a format easy to parse
While #38 could be used to import on some graph database, it's not as optimized for speed. So, it's better we export at least one format as easier and compact to parse than alternatives intended to be edited by hand.
Do actual test on one or more graph database
While on #37 the SQLite is quite useful for quick debug, we would need at least one or two tests actually importing to some graph database.
We also need to somewhat take in account ways to potentially allow validation/integrity tests of the entire library as soon as it is on a graph database. It would be easier do this way.