-
Notifications
You must be signed in to change notification settings - Fork 5
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
jsonld-context-autogen missing the base IRI #88
Comments
Update: The issue is in the JSON-LD file. So, there is no need to update the context file. In current, i.e., rapid release file: We do not have any prefix and also no base IRI causing the aforementioned issue. I suggest to make use of prefix, explicitly rather than having base, as is the best practice.
In old JSON-LD file: We have NIMP prefix so everything's fine.
|
@tekrajchhetri - I took a look at the library_generation model and the NIMP prefix is already set to While we did not explicitly define the prefix in the spreadsheet; linkml automatically fills in any missing prefix (that is why it is not missing from the .yaml file). |
@puja-trivedi Yes, there exist NIMP prefix but in the JSON-LD files that you've shared with me, they're missing the NIMP prefix as I've pointed out in the earlier example (#88 (comment)). The same is shown in the image below, which is a snapshot of a JSON-LD file. Also, you can see from the image blow that not in all cases NIMP prefix is missing. It could be the issue with the translator that you're using to generate JSON-LD files. Also a suggestion, I think it would be better to add some automated checks to ensure there's always a prefix associated. |
@puja-trivedi @djarecka I noticed the context file is missing the default IRI.
Issue:
Whenever you do the conversion of JSON-LD to ttl file, the file path is taken as base IRI, while it should be something like
http://example.org/NIMP/<ID>.
.In the previous version, it's not the case.
The text was updated successfully, but these errors were encountered: