You will have some challenges with multiple relations/edges between same person and org. In such case, each edge is an occurrence, not a triple. See: w3c.github.io/rdf-star/cg-sp…
1
In my opinion modelling the occurrence as a blank node does not improve over the current Schema.org approach and introduces dependence on something which is not yet standardized. How would this work in microdata?
1
What do you mean with “current schema.org approach”? Not entirely sure what you’re saying here 😅
1
Please refer back to earlier in this thread where you both talk about using EmployeeRole which works nicely for @jdevalk only the double worksFor is weird. I referenced the section from RDF-star draft where they describe the difference between an RDF-star triple and occurrence.
2
In case of <jdevalk> <worksFor> <yoast> but you want to describe he held different roles at different times, you cannot just say << <jdevalk> <worksFor> <yoast> >> :started "2002-01-01" as all those qualifying statements would be about *the same* triple, so it'd be nonsense.
1
to complement: 1) You need to introduce a *node* -- it does not have to be blank. 2) The example in the RDF-star spec presents a patter, that can be generalized: different relations between a quoted triple and its occurrences/realizations/roles...
Jun 24, 2022 · 1:13 PM UTC
1
2


