The simple subject-predicate-object data model of RDF tempts us to treat relationships and verbs as simple predicates or properties/properties.
However, this often does not do justice to reality.
For example, if we are collecting data on employment relationships or project contractors, a first approach might be:
Today I listened to the workshop "Democratize the Knowledge Graph and Concrete Tooling Requirements" by Adam Keresztes at the 2023 Knowledge Graph Conference in NYC.
Different people there emphasized the difficulty of explaining the difference between classes and instances to non-ontologists.
Which had me reflecting on how I work with this terminology, and I found that I tend to use 'set' instead of 'class'.
A current customer project has once again shown me two important advantages of the W3C standards around semantic technologies and graph data:
Why RDF? Because it protects your investment!
Es werden keine Dienste zur Analyse Ihres Verhaltens genutzt, wir tracken sie nicht.
