You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These functions in rdflib are the way I have done the bulk of the data to day working with RDF data.
Tim Berners-Lee @timbl 10:34
You don’t have each() and any() ???
This is supposed to be the thing which corresponds to the thing rdflyib.js used to call IndexedFormula and now calls Store?
@timbl scrolls back to "@timbl the idea is, like in the representation task force, to find a minimal interface we all agree on. additional custom methods can be added by datafactories, like rdflib. that's why there is no .any() or .each()."
Sorry I want every RDFJS implementation to be able to support my code. Having different implementations implement different methods is called lack of interop.
You can have two-level spec where the minimal interface is really the only methods whcih cannot be implemented in terms of other methods, and then the second level with the convenience functions is implemented everywhere and the spec people depend on.
My worry is that I have seen a lt of new developers writing everything in terms of match() and just concluding that RDF is a pain, when if they had used any() and each() then it would have been a simpler and more natural experience.
We should keep the mandatory functions simple, dataset is still a low-level spec. Your functions would be in the "optional" group according to #4 IMHO.
These functions in rdflib are the way I have done the bulk of the data to day working with RDF data.
Tim Berners-Lee @timbl 10:34
You don’t have each() and any() ???
This is supposed to be the thing which corresponds to the thing rdflyib.js used to call IndexedFormula and now calls Store?
@timbl scrolls back to "@timbl the idea is, like in the representation task force, to find a minimal interface we all agree on. additional custom methods can be added by datafactories, like rdflib. that's why there is no .any() or .each()."
Sorry I want every RDFJS implementation to be able to support my code. Having different implementations implement different methods is called lack of interop.
You can have two-level spec where the minimal interface is really the only methods whcih cannot be implemented in terms of other methods, and then the second level with the convenience functions is implemented everywhere and the spec people depend on.
My worry is that I have seen a lt of new developers writing everything in terms of match() and just concluding that RDF is a pain, when if they had used any() and each() then it would have been a simpler and more natural experience.
Discussed at https://gitter.im/rdfjs/public?at=5c069e8e43c68b3727fba1b9
The text was updated successfully, but these errors were encountered: