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

On using extended ASCII / UTF-8 (?) for catalog resource IDs #96

Open
robknapen opened this issue Dec 16, 2024 · 1 comment
Open

On using extended ASCII / UTF-8 (?) for catalog resource IDs #96

robknapen opened this issue Dec 16, 2024 · 1 comment
Assignees

Comments

@robknapen
Copy link

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?

Screenshot 2024-12-16 at 09 48 27
@robknapen
Copy link
Author

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)?

Screenshot 2024-12-16 at 10 39 23

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