-
Notifications
You must be signed in to change notification settings - Fork 560
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
Issue 738: support empty publicID #1181
base: main
Are you sure you want to change the base?
Conversation
1 similar comment
If you like this contribution, please add the #hacktoberfest-accepted label |
Hi @AnjoMan I'm sorry, we are not participating in DigitalOcean's Hacktoberfest campaign. |
Hi @AnjoMan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As can be seen for the turtle example, with your fix we would introduce some inconsistency across the serializers. The fix does also not work in the same way for the current Turtle parser/notation3 parser as we call graph.absolutize()
in this case.
What is the usecase for an emptyID?
In m eyes this relative URI thing without explicitly defining a base in the file is a tough problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This issue needs to be solved for all parsers at once.
This adds support for specifying a publicID as ''; instead of evaluating the falsy-ness of the input, we want to use the provided string, even if it is ''.
7a053b2
to
3f40a00
Compare
fe59bfc
to
8125658
Compare
This adds support for specifying a publicID as '';
instead of evaluating the falsy-ness of the input,
we want to use the provided string, even if it is
''.
Fixes #738
Proposed Changes
publicID
as '', we should not trigger theNone
default behaviour