Support traversal profiles for metadata graphs
Sometimes it is necessary to generate a metadata graph consisting of several merged metadata graphs. One of many use cases is the generation of a full DCAT-AP description that originates from serveral entries. A traversal profile determines which predicates are followed for fetching other entries.
A traversal profile is to be pre-defined in the EntryStore configuration and should consist of a short name (e.g. "dcat") and a list of predicate URIs.
The request to the REST API should look like follows:
Example using numeric IDs:
Example using names instead of IDs:
It should also be possible to provide a comma-separated list of profiles, mixed with plain predicates.
Namespace expansion should be performed.