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

Quads remove events #1

Open
iddan opened this issue Jan 25, 2019 · 5 comments
Open

Quads remove events #1

iddan opened this issue Jan 25, 2019 · 5 comments

Comments

@iddan
Copy link

iddan commented Jan 25, 2019

Reading through the spec I wonder: is there a way to listen to quads removal in the store? As far as I understand the Source interface is only usable for additions. Am I missing something?

@iddan
Copy link
Author

iddan commented Jan 27, 2019

Implementation proposal rdfjs/N3.js#162

@bergos
Copy link
Member

bergos commented Jan 29, 2019

If we add it, it should be optional to implement. Some backends may not list the quads which will be deleted on removeMatches (e.g. SPARQL). Also the data event of a stream is a little bit different to a remove event, as data is just the event based way of using .read().

@jacoscaz Maybe also relevant for QuadStore.

@iddan
Copy link
Author

iddan commented Jan 30, 2019

True. But generally data is when new quads are added and remove are when they are removed

@elf-pavlik elf-pavlik transferred this issue from rdfjs/data-model-spec Feb 11, 2019
@elf-pavlik
Copy link
Member

@iddan would you like to create PR which adds it to this section: http://rdf.js.org/stream-spec/#optional-events I think this will allow everyone to provide better feedback.

As far as I understand the Source interface is only usable for additions.

Store interface defines method for removals. Source only match() for reads and Sink only import() for additions.

@iddan
Copy link
Author

iddan commented Apr 8, 2019

Yes!

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

No branches or pull requests

3 participants