Until now the OntologiesService had a persistRegistry setting which saved all registered ontologies to the settings dataset, including their JSON-LD context.
This added a lot of data that is not very useful, since most ontologies are core ontologies. This option is only for Pod providers which want to accept custom ontologies.
So I changed the API of the service with a persist param that can be passed to the ontologies.register service. Only those ontologies are persisted. And only the prefix and namespace can be persisted.
Until now the OntologiesService had a
persistRegistrysetting which saved all registered ontologies to the settings dataset, including their JSON-LD context.This added a lot of data that is not very useful, since most ontologies are core ontologies. This option is only for Pod providers which want to accept custom ontologies.
So I changed the API of the service with a
persistparam that can be passed to theontologies.registerservice. Only those ontologies are persisted. And only the prefix and namespace can be persisted.