N-ary relationships

The classes and properties involved in the guidance for Indentity are the followings:

  • rdftm:subject-role

The rules are as follows:

Comments and reviews


Adhere to [Noy 05]?

In the new editor's note http://smi-web.stanford.edu/people/noy/nAryRelations/n-aryRelations-2nd-WD.html about N-ary relations in RDF the patterns changed. The precedent 2 patterns collapsed in one, and there is a new pattern which uses rdf:List



  • Pattern 1:
    • this pattern allows to represent a relation with different aspects or attributes, a relation with a subject distinguished by the other participants, a relation with no distinguished subject;
    • the n-ary relation is represented by a new class and n new properties.

P rdf:type X.    P rA A .   P rB B .   P rC C .   
P rdf:type X.    A rA P .   P rB B .   P rC C .   

  • Pattern 2:
    • This pattern allows to represent those relations where all but one of the participiant do not have a specific role;
    • The n-ary relation is represented by the subject pointing to the list, where each list item points to its content and to the rest of the list.


The question is: what does an n-ary association in Topic Maps become when we convert it to RDF? And is there going to be a way to convert an RDF resource into an n-ary association when converting to Topic Maps? Those are the questions, I think. Noy's note is probably only helpful in that it has a proposal for the former, but IMHO what she calls n-ary relationship is not the same as an n-ary association in Topic Maps, so it may be best to simply ignore the note.

Revision: r1.4 - 26 Sep 2005 - 13:08 - LarsMarius
RDFTM > RDFTMMappingGuidelines > DiscussionPoints > HandlingNaryRelationships
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Fabio's Wiki? Send feedback