Twitter | Search | |
Francis Opoku Dec 23
Short comparision of and by . One SPARQL Query can go against multiple SPARQL endpoints in a natural way - that is not equal to schema stitching in GraphQL because there is no need for schema assumptions of different 's:
Reply Retweet Like
Pieter Colpaert Dec 23
Replying to @fraopo @RubenVerborgh
I would argue that SPARQL just creates a better framework for schema stitching, but schema stitching is still needed → Important to get these expectations right
Reply Retweet Like
Ruben Verborgh
That’s not right. RDF provides a global/universal schema. And indeed, not all parties use the same parts of that schema. In contrast, GraphQL has only local schemas, which can be mutually incompatible. In RDF, alignment is done by ontologies. GraphQL federation is a kludge.
Reply Retweet Like More
Pieter Colpaert Dec 23
Replying to @RubenVerborgh @fraopo
Agreed :)
Reply Retweet Like
Kingsley Uyi Idehen Dec 23
Yep! remains generally misunderstood. Too many assume: 1. it is a document content-type 2. it requires mass agreement on everything for it to work -- whereas the only agreement is that a sentence comprises a subject, predicate, object.
Reply Retweet Like
turnguard Dec 23
:-) assumption: any advocating for non-common standards or tools enabling those using common standards (e.g. english) shall be considered deeply flawed
Reply Retweet Like