A document that this thing is the primary topic of.
Linked data distinguishes between a thing and the page about it. A painter has a URI; the biography page about her has another. foaf:isPrimaryTopicOf is the FOAF property that joins the two with a specific promise: the document is primarily about this thing. That promise turns out to have useful consequences.
A sub-property with an extra claim
The FOAF page properties form a small hierarchy:
| Property | Says about the document |
|---|---|
| foaf:page | it is about the thing, perhaps among other topics |
| foaf:isPrimaryTopicOf | its main topic is the thing |
| foaf:homepage | it is the thing’s own homepage |
Each property is a sub-property of the one above. A statement using foaf:homepage therefore implies the two broader ones, and a statement using foaf:page implies neither of the narrower ones.
The inverse of foaf:isPrimaryTopicOf is foaf:primaryTopic, which a document can use to point at its subject. Publishers of RDF profiles often place foaf:primaryTopic in the document’s own metadata, and data consumers read it in either direction.
Why inverse functional matters
FOAF declares foaf:isPrimaryTopicOf as an owl:InverseFunctionalProperty. In plain terms: one document, one primary topic. If dataset A says its URI for a composer is the primary topic of a given Wikipedia article, and dataset B says the same about its own URI, an OWL reasoner may conclude that the two URIs denote the same composer.
That is powerful, and it is also a trap. A collection landing page that is really about two things (a pair of related manuscripts, say) should not be claimed as the primary topic of both, or the two manuscripts will merge in any system that applies the inference. In that case foaf:page is the safer statement for each.
The same caution applies to pages that change subject over time. A URL that described one exhibition in 2015 and was reused for another in 2020 has had two primary topics, and data harvested at different times will disagree about which one it was. Stable, never-reused landing page URLs avoid the problem entirely.
Practical use in collections
Archives and libraries that mint URIs for entities (people, places, works, formats) usually also maintain a human-readable page for each. foaf:isPrimaryTopicOf is a clean way to connect them. The entity URI stays stable and machine-oriented; the landing page can be redesigned without affecting identifiers. Content negotiation often sits on top of this: a request for the entity URI from a browser is redirected to the landing page, while an RDF client receives the data, and foaf:isPrimaryTopicOf states the link explicitly for both.
The pattern is visible at scale in DBpedia, where each resource points to its English Wikipedia article this way. Pages that merely mention a thing (a news item, an exhibition announcement) are better linked with foaf:page, as the example shows. If the entity also has an image, foaf:depiction adds it, and a label comes from foaf:name.
Getting it right
A few checks keep the property honest:
- The object should be a document (an HTML page, a PDF), not another entity URI. Pointing it at a person’s URI declares that person to be a document.
- Do not reuse one landing page as the primary topic of several entities.
- When a page moves, update the link or keep a redirect; a dead primary-topic document weakens the main reason to use the property.
For identifiers in Dublin Core terms, dcterms:identifier records a string or URI that identifies the resource itself, which is a separate statement from pointing to a document about it.
Example in RDF
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:foaf="http://xmlns.com/foaf/0.1/">
<rdf:Description rdf:about="https://example.org/id/collection/county-maps">
<foaf:name>Scanned county maps, 1880–1910</foaf:name>
<foaf:isPrimaryTopicOf rdf:resource="https://example.org/collections/county-maps.html"/>
<foaf:page rdf:resource="https://example.org/news/2024-03-map-launch.html"/>
</rdf:Description>
</rdf:RDF>
Questions about foaf:isPrimaryTopicOf
What does foaf:isPrimaryTopicOf mean?
It links a thing to a document whose primary topic is that thing. A biography page about a person, a Wikipedia article about a city, or a collection landing page are typical objects. It is the inverse of foaf:primaryTopic.
Why is foaf:isPrimaryTopicOf inverse functional?
A document has at most one primary topic. If two resources both claim the same document as the one they are primarily about, a reasoner concludes that the two resources are the same thing. That makes the property useful for merging data.
How does it differ from foaf:page?
foaf:page links a thing to any document about it, including pages that merely mention it among other subjects. foaf:isPrimaryTopicOf is a sub-property of foaf:page and adds the claim that the document is mainly about this one thing.
Is foaf:homepage a kind of isPrimaryTopicOf?
Yes. In FOAF, foaf:homepage is a sub-property of foaf:isPrimaryTopicOf. A homepage is a document whose primary topic is the thing, and it is also inverse functional, so a shared homepage identifies a single entity.
Where is foaf:isPrimaryTopicOf commonly used?
DBpedia uses it to connect each resource to the Wikipedia article it was extracted from. Library and museum data sets use it to point from an entity URI to its human-readable landing page.