-
Notifications
You must be signed in to change notification settings - Fork 4
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
Consider using horned-owl's IRI type instead of strings for entity identifiers #12
Comments
Nice idea. I think it confirms to me that we should not be validating IRIs by default, but only on demand. It might save some memory but it should also simplify your code a bit -- I think you could ditch all the I guess this raises the question of code organisation. For whelk, it makes no difference, but I wonder whether IRI belongs in it's own crate. |
Slightly different question, but I'd quite like to have whelk-rs as a dependency of |
We're depending on |
Just the convenience |
Oh I see, for our simple CLI we can probably just use the parsers directly if that lets us drop the |
All the entity types in whelk have an ID that is represented by a string:
whelk-rs/src/whelk/model.rs
Lines 69 to 77 in 74e76cf
In OWL this ID is an IRI. We should think about making this more explicit and directly using IRIs for the IDs. Would this save any memory? (When we translate from OWL to the Whelk model we could pass the IRI directly). Some recent IRI discussion in horned-owl: phillord/horned-owl#56
We should probably wait for any IRI changes in horned-owl to be resolved before taking any action.
The text was updated successfully, but these errors were encountered: