You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We often want to provide more information about the relationships between resources:
Say I want to describe the friendship between two people. I could create a friendship Property that simply points from one Person to the next Person. But what if I want to describe details about this friendship, such as when it started?
Alice is a Manager at AcmeInc. Her role is what connects her relationship to the organization.
In labeled property graph databases, you'd probably model these in an edge. In Atomic Data (and RDF), relationships can't have their own properties.
This means we need a pivot model.
The friendship, for example, could have a from and to attribute, as well as a startDate.
The role could have an person, organisation, roleType, and startDate
Some questions about this:
How do we deal with relationships where the from and to are really no different? Using two different properties is confusing, and makes it harder to perform queries (we need to run queries in both directions to answer any question). Do we us a links property that is a resourceArray containing a maximum of two resources?
Should these relationships be instances of new Classes? In our examples, a Friendship and Role class would probably make a lot of sense. But maybe a more constrained model is more appropriate for these pivot type models?
The text was updated successfully, but these errors were encountered:
To me, a friendship is a a social concept.
In one RDF ontology that model is expressed only indirectly as the existence of two agents mutually "knowing" each other (this is how e.g. FOAF models it), whereas another ontology can choose to express it as an explicit Friendship requires ties to exactly two agents.
Through reasoning, data of the former model can be resolved as matching
the latter model.
I don't really understand
How do we deal with relationsships where the `from` and `to` are really no different?
Your question makes no sense to me: Assuming you a talking about
FOAF-like modelling, as I see it a friendship *only* exist when it is
mutual - i.e. if I know you but you don't know me then it is a case of a
fan of a hero.
We often want to provide more information about the relationships between resources:
friendship
between two people. I could create afriendship
Property that simply points from one Person to the next Person. But what if I want to describe details about this friendship, such as when it started?role
is what connects her relationship to the organization.In labeled property graph databases, you'd probably model these in an
edge
. In Atomic Data (and RDF), relationships can't have their own properties.This means we need a
pivot model
.friendship
, for example, could have afrom
andto
attribute, as well as astartDate
.role
could have anperson
,organisation
,roleType
, andstartDate
Some questions about this:
from
andto
are really no different? Using two different properties is confusing, and makes it harder to perform queries (we need to run queries in both directions to answer any question). Do we us alinks
property that is aresourceArray
containing a maximum of two resources?Class
es? In our examples, aFriendship
andRole
class would probably make a lot of sense. But maybe a more constrained model is more appropriate for these pivot type models?The text was updated successfully, but these errors were encountered: