Read the first post in our new series of blog posts focusing on major Ontotext’s webinars and how they fit in the bigger picture of…
This post continues our series in which we want to provide an overview of what we do and how our webinars fit into it. In the previous post, we talked about data virtualization and how Ontotext’s RDF database for knowledge graphs GraphDB provides the tools for the full journey from graphs to relational tables and back. All of our webinars are available on demand, so if we pique your interest with any of these posts, you can request a free recording.
Here, we want to draw your attention to two webinars that focus on how GraphDB levels the field between RDF and LPG stacks with the help of RDF-star support and the Graph Path Search plug-in. Given all the advantages of the RDF model regarding enterprise data management, one no longer has good arguments why to bother with LPG at all.
Read on and watch the webinars to get convinced.
As we’ve said again and again, we believe that knowledge graphs are the next generation tool for helping businesses make critical decisions, based on harmonized knowledge models and data derived from siloed source systems. Due to the huge value generated by their data standardization and semantic modeling capabilities, knowledge graphs are most often associated with data integration, linking, unification and information reuse. But these tasks are only part of the story. As more and more organizations are turning to knowledge graphs for better enterprise knowledge management, data and content analytics, search and graph exploration become key tools for successfully utilizing knowledge graphs.
In this age of graphs, there are two main graph data models, each of them with distinct characteristics:
These models originate from different use cases: distributed knowledge representation and open data publishing on the web vs graph analytics designed to be as easy to start with as possible. There have been many comparisons of the strengths and limitations of knowledge graphs vs property graphs (this is our take on it).
Long story short, RDF is recognized as the better option (if not the only one) for knowledge graphs, because its web-native syntax supports data exchange and sharing and because its formal semantics allows for easy alignment of meaning and structure across sources, unified views and unambiguous interpretation.
On the other hand, LPGs lack many features that are an absolute must for enterprise data management, e.g., standard schema language. Still, for many years, two main advantages of property graphs have been pointed out: they can deal with properties on edges in the graph and they are good for graph traversal.
In two of its 9.x releases, GraphDB has eradicated these two limitations by upgrading its modeling expressivity with RDF-star/SPARQL-star and by enabling key graph analytics within SPARQL queries with the Graph Path Search plug-in. Both these new features have already been adopted in partner tools:
Now, let’s dive in and look into each of these webinars.
In our first webinar GraphDB 9.2 Supports RDF-Star to Match the Expressivity of Property Graphs,our CTO Vassil Momtchev demonstrates the various options of modeling complex relationships that have multiple attributes with plain RDF, e.g., reification and singleton properties. He walks you through what you need to know about RDF, the different modeling challenges we’ve seen over the years and how to address them. RDF-start overcomes all these challenges. It also goes beyond the expressivity of property graphs, where you can attach key-value pairs to relationships and allows a more efficient representation of scores, weights, temporal restrictions and provenance information.
You will learn more about statement level metadata, the pros and cons of RDF-star, how SPARQ-star works and how different RDF engines implement RDF-star. Vassil introduces the new GraphDB features related to RDF-star/SPARQ-star and goes over some practical examples and performance results. He shows how RDF-star brings the simplicity and usability of property graphs without sacrificing the essential semantics that enables correct interpretation and efficient management of the data.
Interesting attendee question: Should I model my data, such as start and end date, as metadata with embedded triples or as N-ary concepts?
Ontotext Answer: If we take again the example of Abraham Lincoln being the President of the United States (see the visual above), our recommendation is to model the President of the United States in the ontology model in order to enable inference and other interesting things. This is a N-ary relationship concept that would be very clear for every user of the model – that “president” is a type of position with a “start date” and “end date”. And we would recommend to model other metadata (such as the reference and where this information comes from) as RDF-star embedded triples because maybe this is something that doesn’t need to be exposed for every user but only to the people who are interested in the statement.
The second webinar in focus is Graph Path Search with GraphDB 9.9 and metaphactory 4.3. It demonstrates how Ontotext and its technology partner metaphacts can generate great value on top of knowledge graphs in analytical use cases through graph path search and interactive visualization.
In the first part of the webinar, our speaker from Ontotext, Tomas Kovachev, explains why graph path search is a computationally expensive task and presents our graph path search implementation. He also provides a comparison of how different RDF and property graph databases implement it and how GraphDB extends the SPARQL 1.1 standard to fully support all significant graph path search use cases. On top of that, he tests GraphDB and other engines against LDBC’s Semantic Network Benchmark to give you a feeling for the scalability and the efficiency of our implementation.
In the second part, our guest speaker Sebastian Schmidt, CEO at metaphacts (the first one to adopt our new implementation), demonstrates how the graph path search algorithm available in GraphDB 9.9 is exposed to end users with the metaphactory 4.3 release. He shares a specific use case taken from the clinical trial domain: How a researcher can find connections between study investigators and various other resources such as targets and diseases, which will allow them to further investigate discovered studies or medications
You will learn more about graph path search fundamentals, the features in the “vanilla” SPARQL 1.1 limiting the exploration of paths in a graph and how the new extension in GraphDB 9.9 enables complex graph pattern search in full compliance with the SPARQL specification. You will also see a demonstration of how graph path search is exposed to non-techie end users in the metaphactory 4.3 release.
Interesting attendee question: How does this search for the shortest path work when there is a cyclic relation in the graph? Do you try breaking the cycle first?
Ontotext answer: Graphs can represent limitless relationships between resources, therefore cycles have to be taken into account in order to avoid endless graph traversals. Our path finding algorithm is based on the level-by-level adjacent node traversal of Breadth First Search but, unlike the original algorithm, it keeps track of all the visited nodes (at all depths) and the relations leading to them. This allows us to not only avoid cyclical relationships but also to find whether a given resource can be reached via other resources and relationships.
That covers the two webinars that we wanted to present to you today.
Take home summary:
In a nutshell, given all the advantages of RDF, and GraphDB in particular, regarding knowledge graph applications, one has no longer any reasons to bother with property graphs, which are not fit for efficient enterprise data management. Managing your data and analyzing it can go hand in hand. You can use the same knowledge graph platform that lets you put your data together in a sustainable way for analytics purposes as well.
We hope you’ve heard enough to want to dive straight into one of these webinars or why not both?
Watch out for our next post in this series At Center Stage: Ontotext’s Webinars or visit our Webinars directly to check out what is upcoming!