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

Add support for reading RDF* #39

Open
csi-amolpawar opened this issue Oct 21, 2022 · 2 comments
Open

Add support for reading RDF* #39

csi-amolpawar opened this issue Oct 21, 2022 · 2 comments
Labels

Comments

@csi-amolpawar
Copy link

As a serd api user, Need a support for RDF* data present in the turtle/trig file

  << <person3> <dislike> "jazz" >> <weight> 9 .
  << <person3> <dislike> "theatre" >> <weight> 5 .
  << <person3> <dislike> "opera" >> <weight> 10 .

See Reference https://www.w3.org/2022/08/rdf-star-wg-charter/

@drobilla
Copy link
Owner

Not likely unless somebody funds it, to be honest. I have little to no incentive for this personally, and RDF* seems like it raises a lot of questions that would require design changes, especially in a library designed around streaming that exploits the relatively simple structure of RDF data, has no concept of statement identification, and so on.

Perhaps it's doable without too much trouble, but would certainly be for the next-next major version at least.

@drobilla drobilla changed the title Add read support for RDF* format data present in the turtle/trig dataset Add support for reading RDF* Oct 25, 2022
@drobilla
Copy link
Owner

I am reworking the statement storage for the next version, and there's other reasons why having statement IDs might be the way to go internally, so I'll at least have an idle think about whether RDF* is another reason to do so.

That's as far as it will go in terms of things actually in releases until the specs are finalized, but a long-lived branch might be possible until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants