- From: Aldo Gangemi <aldo.gangemi@gmail.com>
- Date: Sat, 9 Nov 2019 13:56:22 +0100
- To: hans.teijgeler@quicknet.nl
- Cc: Semantic Web <semantic-web@w3.org>
- Message-ID: <CAO4q9KEP5E1A83wWPakrxqTOEgq9hLQgVejFHipKM8gEQ+6qTA@mail.gmail.com>
Hello Hans there quite a literature on n-ary relations, reification, etc. What you call Relationships are usually called Frames or Knowledge Patterns. You may have a look at the Framester semantics [1] for a formal treatment of frames across data, linguistic resources, and more, with a large knowledge graph integrated under the hood of frames. Ciao Aldo [1] https://github.com/framester/Framester On Sat 9 Nov 2019 at 13:32 <hans.teijgeler@quicknet.nl> wrote: > Hi, > > > > I would like to hear your opinion about the following. > > > > I propose to make a distinction between the terms ‘Relationship’ an > ‘Relation’ (‘Property’), not for linguistic reasons but to avoid > reification when that is not necessary. > > I know that I am on thin ice, so be it. > > > > Right now we have something like > > - Pete isHusbandOf Mary > - Mary isWifeOf Pete. > > But these *Relation*s/Properties actually are Roles in a missing > *Relationship* called Marriage. > > > > We can also state: > > - MarriagePeteMary hasHusband Pete > - MarriagePeteMary hasWife Mary > > where MarriagePeteMary is Relationship and an instance of the owl:Class > ‘Marriage’, or rather its specialization ‘Hetero Marriage’. > > As a consequence we can easily represent information about that > Relationship. > > > > It appears to me that there are many such Relationships that qualify for > being an owl:Class in their own right. > > Think about Parenthood, Composition, Employment, etc. > > > > Please concur or shoot. > > > > Regards, > > Hans > > 15926.org > > >
Received on Saturday, 9 November 2019 12:57:06 UTC