Coexistence and Interoperability Panel "Coexistence or - PowerPoint PPT Presentation

Coexistence and Interoperability Panel "Coexistence or Competjtjon" W3C Workshop on Web Standardizatjon for Graph Data Olaf Hartjg @olafiartjg

Three Points ● Coexistence is unavoidable ● Interoperability needs well-defined approaches ● Reinventing should be avoided Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 2

Point 1 Coexistence is unavoidable

Coexistence of RDF and Property Graphs ● Too much has been invested for any one of them to get abandoned now ● Both have merits and a user base ● Not to forget SQL databases, and GraphQL Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 4

https://commons.wikimedia.org/wiki/File:COVERED_BRIDGE_AT_PERNSTEJN_CASTLE,_CZECH_REPUBLIC.jpg "Coexistence or Competjtjon" ??? ● Not an “exclusive or” ● Coexistence and competition – Gain an edge on the competition by embracing coexistence ● Consequence: we need interoperability Image source: Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 5

Point 2 Interoperability needs well-defjned approaches

Well-defjned approaches … not just implementations Image source: https://www.publicdomainpictures.net/en/view-image.php?image=253435 and ● Defining the underlying algorithm / mapping / etc. should not be an afterthought (or even skipped at all) ● Before starting up your programing environment, approach should be developed conceptually first (in detail!) https://www.flickr.com/photos/ntsb/40210711664 Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 7

Point 3 Reinventing should be avoided

Rhyme “ Why do you try to reinvent; If you can reuse and extend? ” -Olaf Hartig, 2019 ● Advantages of “reuse and extend:” – No need to learn something new from scratch – No need to build new tooling from scratch ● Two examples ... Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 9

RDF* and SPARQL* Example RDF* data (in Turtle* syntax) :bob foaf:age 23 . <<:bob foaf:knows :alice>> ex:certainty 0.9 . Example SPARQL* query SELECT ?p1 ?p2 ?c WHERE { <<?p1 foaf:knows ?p2>> ex:certainty ?c . } ● Statement-level metadata (edge properties) in RDF ● Also, abstraction for reconciling RDF and Property Graphs – Direct mappings between RDF* and RDF – Direct mappings between RDF* and Property Graphs Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 10

Property Graph Schemas with GraphQL SDL Example Property Graph schema defined using the GraphQL SDL type person { name: String! Image source: http://tinkerpop.apache.org/docs/3.4.0/tutorials/getting-started/ age: Int knows(weight:Float!): [person] @distinct @noloops created(weight:Float!): [software] @distinct @requiredForTarget } type software { name: String! lang: Language } enum Language { java javascript python } Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 11

Takeaway

Takeaway ● Coexistence is unavoidable – does not exclude having competition as well – interoperability needed ● Interoperability needs well-defined approaches – not just implementations ● Reinventing should be avoided – instead, try to reuse and extend Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 13

www.liu.se

T O D O TODO Title ● TODO: text Olaf Hartjg @olafiartjg Panel "Coexistence or Competjtjon" at the W3C Workshop on Web Standardizatjon for Graph Data 15