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

Support for ttl output is first stepping stone to validate using pyshex #589

Closed
dpriskorn opened this issue Jun 27, 2023 · 2 comments · Fixed by #664
Closed

Support for ttl output is first stepping stone to validate using pyshex #589

dpriskorn opened this issue Jun 27, 2023 · 2 comments · Fixed by #664
Assignees

Comments

@dpriskorn
Copy link
Contributor

We need ttl support if we want to use pyshex
e.g. get_ttl_representation()

@dpriskorn dpriskorn changed the title Support for ttl output? Support for ttl output is first stepping stone to validate using pyshex Jun 27, 2023
@LeMyst
Copy link
Owner

LeMyst commented Jul 1, 2023

ttl scope is very large, larger than what support WikibaseIntegrator today or what WBI can easily support.

Do you want a 1:1 (wbi:wikidata) ttl representation? Or partial support is enough for pyshex?

@dpriskorn
Copy link
Contributor Author

dpriskorn commented Jul 2, 2023

I was thinking we have a method that just download it as a string from Wikidata.
Example url http://www.wikidata.org/entity/Q42.ttl
Suggested name of method:
get_ttl_as_string()
For now it should throw an error if not Wikidata

@LeMyst LeMyst linked a pull request Jan 7, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants