Тёмный

Debunking some RDF-vs-Property Graph Alternative Facts - Dr. Jesús Barrasa, Neo4j 

Neo4j
Подписаться 51 тыс.
Просмотров 10 тыс.
50% 1

Опубликовано:

 

1 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 9   
@32to28
@32to28 Год назад
Sort of misleading how all RDF graphs are presented as relational databases at 12:00, which sets up the strawman argument that there are a lot of joins. I'd sort of expect something better from neo, but hey. Marketing is marketing.
@MrLonelyOffc
@MrLonelyOffc 4 года назад
It's really great sir. I clearly understand the difference of RDF and Neo4j. I, even, saw your blog posts and other videos. I really like to use Neo4j in my NLP related project.
@donha475
@donha475 5 лет назад
Super helpful thanks... I'm new to this area... really helped me to plan my little project...
@subhashisdas81
@subhashisdas81 3 года назад
It is very smart and like a marketing presentation while skipping some SoA or comparison with GraphDB such as ontotext graphDB. LPG is not a W3C recommendation where RDF is which makes a big difference in the open community.
@hodaslimani2945
@hodaslimani2945 2 года назад
Great thank you!
@markhall7173
@markhall7173 6 лет назад
Let’s say you’re creating an enterprise ontology to describe business processes. Doesn’t Property Graph approach risk ‘properties’ being having to be defined at each object level? Although he RDF approach creates a denser graph, it does seem to force at least some standardization of property relationships. Triples can be useful that way and domain ontologies more consistent. I understand consistency and governance might not be the primary use-case for the LPG approach, but within enterprise it’s often useful to have such constraints and structure to drive common approaches.
@jbarrasa4649
@jbarrasa4649 6 лет назад
Hi Mark, thanks for your comment. It is perfectly possible to define an enterprise ontology as an LPG, there are multiple cases of use of Neo4j for data governance. OWL and RDFS are just one way of formalising vocabularies/ontologies. I could agree (if that's what you mean) that RDFS/OWL have well-defined semantics that can be used for inferencing or consistency checking but again, there are ways to achieve the same using LPGs (if you're interested have a look at jesusbarrasa.wordpress.com/2016/04/06/building-a-semantic-graph-in-neo4j/). I'd be curious to know what RDFS/OWL primitives you use in your enterprise ontology definitions and whether these include anything beyond classes and properties definitions. Happy to continue the conversation here, but you can also join our slack channel neo4j.com/developer/slack/
@siddharthdedhia11
@siddharthdedhia11 3 года назад
@@jbarrasa4649 Hi Dr. Jesús , It might be a stupid doubt but the reasoning capabilities of neosemantics are very limited. Are there any reasoners existing that do not use ontologies/formal vocabulary that are comaptible with neo4j?
@keithvaneaton5840
@keithvaneaton5840 3 года назад
This is very helpful, especially the demo around 15:00. Question: What specific plugin(s) are you using to call the stored procedure of semantics.importRDF?
Далее
Secret Sauce of Neo4j: Modeling and Querying Graphs
38:38
Webinar: Ontology for Knowledge Graphs
1:01:05
Просмотров 10 тыс.
A Skeptics Guide to Graph Databases - David Bechberger
1:00:54
How Semantic is Your Graph?
40:20
Просмотров 21 тыс.
Battle of the Ages:  Property Graph vs Triple Store
15:17
RDF and OWL : the powerful duo, Tara Raafat
19:13
Просмотров 55 тыс.
Labelled Property Graphs, OWL and WebProtégé
1:03:21
Просмотров 3,3 тыс.
GEOMETRIC DEEP LEARNING BLUEPRINT
3:33:23
Просмотров 182 тыс.