Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make config file configuration merge with that one from the ontology #699

Open
psiotwo opened this issue Apr 30, 2024 · 1 comment
Open

Comments

@psiotwo
Copy link
Contributor

psiotwo commented Apr 30, 2024

Is your feature request related to a problem? Please describe.
I must use either the config file or the configuration from the ontology header itself. This results in many duplicated attributes in both files (title, license, etc...)

Describe the solution you'd like
To let ontology header values be picked in case they are not present in the config file - on per-property basis.

Describe alternatives you've considered
An ideal alternative would be to have everything representable in the ontology header and avoid the config file.

@dgarijo
Copy link
Owner

dgarijo commented Apr 30, 2024

Hello,
I am not sure I understand the issue very well. What is the ontology header? Ontology annotations?

According to https://github.com/dgarijo/Widoco/blob/master/doc/metadataGuide/guide.md all the metadata properties are supported in both the config and ontology metadata file. What are the metadata fields you are missing from the ontology annotations?

I agree that it is easier to maintain only the ontology file, with its metadata

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants