You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in this case the (presumed) title in Greek of dataset in the catalog also seems to be used as its resource ID (in the URI). To me it seems a bit tricky to do this, i.e. it is hard to type (if you don't have a Greek keyboard), maybe runs into issues somewhere on a server/router along the way, and such a label might change (someone fixing a typo) while it would still be the same resource.
Since we need further processing of resources within SoilWise, e.g. for the knowledge base and knowledge graphs, do we stick to these kind of URIs as resource IDs? Or do we use something else internally?
The text was updated successfully, but these errors were encountered:
In this case a UUID seems to be used as resource ID. Are we taking the external resource IDs and mixing them in the SoilWise catalog (and do not generate any internal IDs)?
I noticed that in this case the (presumed) title in Greek of dataset in the catalog also seems to be used as its resource ID (in the URI). To me it seems a bit tricky to do this, i.e. it is hard to type (if you don't have a Greek keyboard), maybe runs into issues somewhere on a server/router along the way, and such a label might change (someone fixing a typo) while it would still be the same resource.
Since we need further processing of resources within SoilWise, e.g. for the knowledge base and knowledge graphs, do we stick to these kind of URIs as resource IDs? Or do we use something else internally?
The text was updated successfully, but these errors were encountered: