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.

Sign up for GitHub

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

Jump to bottom

refactor - replace the own GraphNameMapper, by the one now provided by rdf_store #43

Open
marc-portier opened this issue Apr 15, 2024 · 0 comments
Open

refactor - replace the own GraphNameMapper, by the one now provided by rdf_store #43

marc-portier opened this issue Apr 15, 2024 · 0 comments
Milestone
0.0.3

Comments

@marc-portier
Copy link
Member

see vliz-be-opsci/py-RDF-store#49
@marc-portier marc-portier added this to the 0.0.3 milestone Apr 15, 2024
@marc-portier marc-portier changed the title refactor - replace the own GraphNameMapper, by the on now provided by rdf_store refactor - replace the own GraphNameMapper, by the one now provided by rdf_store Apr 15, 2024
@marc-portier marc-portier mentioned this issue May 3, 2024
Closed
cedricdcc added a commit that referenced this issue May 7, 2024
@cedricdcc
Added support for the following:
85bbdbe 
- Added helper.py containing functions that allow for prefix support in sparql queries and traversal harvesting paths.
- deleted call functions and refactored code in config_builder and all subsequent files that used this __call__ method.
- replaced and refactored all files that worked with the GraphNameMapper, now the maper of py-rdf-store is being used.
- refactored the config builder propery subjects so that when they are called they will get the subjects from the graph if
that is required (when SPARQL query is given instead of list of subjects).
- edited the .yml files that are used as configs to now not contain the <> anymore in the prefixes since these will now cause issues for the helper functions resolve_uri()

Issues that were affecting by the changes in this commit are:
- #35
- #43
- #48
- #34
@cedricdcc cedricdcc mentioned this issue May 7, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.0.3
Development

No branches or pull requests
1 participant
@marc-portier