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

Repository suggestion for services #242

Open
alko-k opened this issue Apr 26, 2023 · 2 comments
Open

Repository suggestion for services #242

alko-k opened this issue Apr 26, 2023 · 2 comments
Labels
DataRepository enhancement New feature or request

Comments

@alko-k
Copy link

alko-k commented Apr 26, 2023

Hi all,

thanks for the great work with the Repo description.
I was looking at the repository diagram and thought of the following:
Currently the Data Repository offers Datasets, Data Catalogs and Services, via hasOfferCatalog and availableChannel respectively.
My suggestion is to group them all under the OfferCatalog which can then offer itemListElements that are of any type e.g. Services, CreativeWork etc.
This is because if you want to add new types in the future, you will not have to keep changing the current schema and software tools will be able to harvest new items.
I have written the json-LD required.
Many thanks
Alexandra

@ashepherd
Copy link
Member

thanks @alko-k! We'll put this issue on the next agenda

@ashepherd ashepherd added enhancement New feature or request DataRepository labels Apr 26, 2023
@alko-k
Copy link
Author

alko-k commented Apr 27, 2023

Thanks @ashepherd much appreciated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DataRepository enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants