search

mff-uk / dataspecer

https://dataspecer.com
MIT License
21 stars 7 forks source link

Properly define IRIs used for internal objects and specifications #337

Open jakubklimek opened 10 months ago

jakubklimek commented 10 months ago

Currently, when I show "store info", I see IRIs like https://ofn.gov.cz/schema/1683788380842-d194-58da-b887, https://ofn.gov.cz/class/1683788421908-e253-7ed4-90b9 and https://ofn.gov.cz/attribute/1683788755493-d94e-ff77-b929. The ofn.gov.cz part should be configurable as IRI base for each specification as the current state is confusing for international or non-OFN use cases. This will become more apparent as we continue with publishing the Dataspecer project as part of the specifications.

This could be set once as part of the specification creation, or there could also be support for changing it, which may however affect referencing specifications, etc., so we need to think about this.

sstenchlak commented 5 months ago

This is an internal ID that was decided to be in this particular form. In the core@v2, this would be treated differently, and it would be possible to have custom IRIs of models and resources in them.

I am closing this issue as it is becoming part of core@v2.

jakubklimek commented 5 months ago

In this case, a corresponding issue should be created for core@v2 so that it is not forgotten that we need this.