Amir S.

every problem/data that i have encountered which is encoded in/via graphs can also be addressed with traditional relational databases. What are the characteristics of problems/data that are best suited for graphs ? Example: "use-cases involving measuring length of relationships when the records have hierarchical parent/child relationships". Concrete toy example "how long is the longest family tree in a large database of family trees" is more expensive to compute using relational databases. Do you know of more concrete examples for when graphs are advantageous ?

how can i encode relationships that are not binary (node -- relation --- node) using labeled property graphs ? for example consider cases where a relationship becomes true/activated when more than 1 relationship is present. For example a dish is macaroni and cheese only if it has all 3 ingredients as shown in the figure. What's the best practice in encoding such data in a LPG ?

still not sure the process of accessing KGC 2022 airmeet or conference virtually on Monday, do we need to generate a username and password prior to attending ?