Jakob Voß

Support inclusion of configuration

4

## Reasons for creating this PR This adds repeatable configuration property `skosmos:includeConfig` to include configuration from file or URL. The configuration is cached as usual, based on modification time of...

Extend list of vocabularies at front page

1

The current plain list of vocabularies, optionally grouped in flat categories should be extended. This needs some brainstorming on existing ideas and requirements mentioned in discussion before such as: -...

Include API documentation

2

## Description of the enhancement Skosmos should display a nice API documentation such as https://api.finto.fi/doc/ by default at `/rest/v1/`. This can hopefully be generated from existing Swagger JSON. This might...

Merge full vocabulary configuration into vocabulary information

1

## Description of the enhancement The *vocabulary information* page shows genera information about a vocabulary. Its data comes from two sources: - [vocabulary configuration](https://github.com/NatLibFi/Skosmos/wiki/Configuration#vocabulary-specific-configuration) (set in Skosmos configuration) - vocabulary...

Create, collect and publish statistics

1

## Description of the enhancement There should be a general statistic page with information such as - number of vocabularies - date issues / modified of each vocabulary, ordered by...

Fix and extend mapping of vocabularyStatistics to RDF

1

## Description of the enhancement Extend the [JSON-LD Context document of vocabularyStatistics](https://github.com/NatLibFi/Skosmos/blob/master/controller/RestController.php#L275-L291) to fully encode vocabulary statistics in RDF. By now - `deprecatedCount` and `conceptGroups` are not included - subTypes...

Feature request: include configuration from URL

6

## Description of the enhancement Support reading content of `config.ttl` from a SPARQL endpoint. This would require to add two new properties in `config.ttl`, such as `skosmos:configEndpoint` and `skosmos:configGraph` to...

The page https://jsoncanvas.org/ should list known implementations. I guess by know it's - [Obsidian](https://obsidian.md/) - [unnamed reference implementation used in this repository](https://github.com/obsidianmd/jsoncanvas/blob/main/assets/canvas.js) - ...? People should be encouraged to use...

The web application should list some example URLs of files to try out. These files could also be hosted in this repository so they won't disappear. The `examples` directory can...

The JSON Canvas format ~is~ should be based on well-defined data standards: - The JavaScript Object Notation (JSON) Data Interchange Format ([RFC 8259](https://tools.ietf.org/html/rfc8259)) - RFC 3986 on URIs (see #17)...