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

Consider operating on quads/datasets for IOService #592

Open
acoburn opened this issue Dec 1, 2019 · 0 comments
Open

Consider operating on quads/datasets for IOService #592

acoburn opened this issue Dec 1, 2019 · 0 comments
Labels

Comments

@acoburn
Copy link
Member

acoburn commented Dec 1, 2019

The I/O service currently operates only on Triple and Graph objects. This makes sense for triple-based RDF serializations, but it excludes any possible support for quad-based serializations (TriG, N-Quads or JSON-LD (with dataset support)). Elsewhere, we have successfully converted interfaces from Triple/Graph objects to Quad/Dataset objects, and this would, arguably, make this more consistent across the various services.

@acoburn acoburn added the area/api Core API module label Dec 1, 2019
@acoburn acoburn added this to the 0.9 Release milestone Dec 1, 2019
@acoburn acoburn modified the milestones: 0.9 Release, 0.10 Release Dec 7, 2019
@acoburn acoburn modified the milestones: 0.10 Release, 0.11 Release Feb 11, 2020
@acoburn acoburn modified the milestones: 0.11 Release, 0.12 Release Mar 7, 2020
@acoburn acoburn modified the milestones: 0.11 Release, 0.12 Release Mar 27, 2020
@acoburn acoburn removed this from the 0.12 Release milestone Apr 23, 2020
@acoburn acoburn added this to the 0.17 Release milestone Sep 28, 2020
@acoburn acoburn modified the milestones: 0.17 Release, 0.18 Release Feb 16, 2021
@acoburn acoburn removed this from the 0.18 Release milestone Apr 2, 2021
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

1 participant