Not really TBC questions but I guess you can give the best answer. I see popularity of json-ld rising a lot (as optimal compromise between webdev and ld/sw world) where people might just forget about the (for them) complex RDF conceptuals above….
In that sense I see more and more projects that go json-ld (iso rdf/xml, turtle etc.) also involving storage options like mongodb iso triple/quad stores. At the same time people like graphql(-ld) over sparql. These trends gives rise for me to some issues: 1. If RDF* evolves bringing us better metadata options (treating statements as objects again) on LD side would that also give rise to a JSON-LD* next to Turtle*? Or is json-ld already by itself more flexible here so that no change is needed? (ie is the current use of json-ld as RDF serialization an already restricted usage?) I am trying to find out if turtle and hence Turtle* will have advantages over json-ld… 2. I know graphQL-LD approach as defined/demonstrated etc. by Ghent university (https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/). Is your prefixes graphql schema extension doing (functionaly) the same? If so isn’t there room for a standard graph-ql-ld variant having those extensions in a standard way? Or… is such a GraphQL update already in the making (much a like json to json-ld)? 3. What will happen in future: shacl or graphql schema or both? (knowing slide no. 20 from: https://www.topquadrant.com/project/graphql_json_rdf/) 4. Why is there a graphql schema language anyway? Why not use json-ld schema definitions for that (because it is not powerful enough)? (like in schema.org if I am right) Sorry if these questions are out of scope. It’s just that I need some story when people ask “why do we have shacl/sparql, graphql schema/graphql, json-ld for schemas (and also json schema)….can’t you make up your mind?”😊 Thx for your views Michel Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locations/DTS> [cid:[email protected]]<http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5402dc770eb948068fe971f523d7879e%40tno.nl.
