Comparing Semantic Web Technologies to TypeDB

Semantic Web technologies enable us to represent and query for very complex and heterogeneous datasets. We can add semantics and reason over large bodies of data on the web. However, despite a lot of educational material available, they have failed to achieve mass adoption outside academia.

TypeDB works at a higher level of abstraction and enables developers to be more productive when working with complex data. TypeDB is easier to learn, reducing the barrier to entry and enabling more developers to access semantic technologies. Instead of using a myriad of standards and technologies, we just use one language - TypeQL.

In this talk:
- We look at how TypeQL compares to Semantic Web standards, specifically RDF, SPARQL RDFS, OWL and SHACL.
- Cover questions such as, how do we represent hyper-relations in TypeDB? How to use rdfs:domain and rdfs:range in TypeDB? And how do the modelling philosophies compare?

Speaker: Tomás Sabat

Tomás is the Chief Operating Officer at Vaticle. He works closely with TypeDB's open source and enterprise users who use TypeDB to build applications in a wide number of industries including financial services, life sciences, cyber security and supply chain management. A graduate of the University of Cambridge, Tomás has spent the last seven years founding and building businesses in the technology industry.

[bartkl]

Does my memory serve me well in noticing that the James Dean and vessel examples comes from the "Semantic Web for the Working Ontologist" book? ;)

Great stuff. I'm looking for ways to bring this kind of thinking and technology to the dev teams, and TypeDB might really help.

[scottmeredith]

That's interesting about roles vs. multiple inheritance. It certainly works well for an active relation like employ. How about in a product catalog, where you might want to have static (descriptive) multiple category superclasses of certain product instances, like galoshes as under rainwear and also under footwear? Or should that kind of thing just be done with properties/attributes?