Skip to content
Property · FOAF

The foaf:page property: meaning, usage and related FOAF page terms

Published Formatory editorial team
http://xmlns.com/foaf/0.1/page

A page or document about this thing.

When a thing in a linked data set needs a link to “more information”, foaf:page is often the property doing the work. The definition is plain: a page or document about this thing. It promises only that the document is about the subject in some way, which is what makes it so flexible, and also what makes it the wrong choice when a stronger statement is true.

The page family in FOAF

foaf:page is the broadest of a small set of related properties:

  • foaf:page: a document about the thing.
  • foaf:isPrimaryTopicOf: a document mainly about the thing (sub-property of page).
  • foaf:homepage: the thing’s homepage (sub-property of isPrimaryTopicOf).
  • foaf:weblog: a blog belonging to an agent (sub-property of page).

Because of the sub-property chain, a statement using foaf:homepage automatically counts as a foaf:page statement for any consumer that applies RDFS reasoning. A query for “all pages about X” therefore picks up homepages and primary-topic documents too.

The inverse of foaf:page is foaf:topic. The range of foaf:page is foaf:Document, so its object is classified as a document by inference, which is correct for a web page, a PDF report or a scanned leaflet.

Choosing between page and isPrimaryTopicOf

The choice turns on one question: is this document mostly about this thing? A survey of audio formats that discusses WAVE alongside a dozen others is a foaf:page for WAVE. A landing page devoted to WAVE is better linked with foaf:isPrimaryTopicOf.

The difference has consequences. foaf:isPrimaryTopicOf is inverse functional, so a reasoner may merge two resources that claim the same primary-topic document. foaf:page carries no such inference, which makes it the safe default whenever the document covers more than one subject.

When in doubt, the weaker statement is the better one. Nothing breaks if a page that is in fact mainly about the thing is linked with foaf:page; a consumer just knows a little less. A wrong foaf:isPrimaryTopicOf, by contrast, can merge two unrelated resources in someone else’s triple store.

Use in collections and registries

Format registries and catalog systems typically hold a structured record for each entity and link out to documentation: specifications, guidance, test reports. foaf:page suits those outbound links well. The documents can be described in their own right with Dublin Core properties (dcterms:title, dcterms:issued, dcterms:publisher) once they are typed as foaf:Document.

For a broad, unspecified connection between two resources, dcterms:relation exists, but it says less. If the related resource is a document about the thing, foaf:page says that directly and lets clients build a “further reading” list from it. Images are a separate case and use foaf:depiction.

What goes wrong with foaf:page

Pointing foaf:page at another entity (a person or an organization) instead of a document is the error with the widest consequences, because inference will retype the entity as a document. Another is linking to search result URLs or session-specific addresses that stop working within days. And link rot affects foaf:page more than most properties, since the targets are usually on other sites; periodic link checking over all foaf:page objects is cheap and catches dead references before users do.

A smaller point: FOAF does not provide a way to say what kind of page it is (specification, review, news item). Projects that need that distinction add dcterms:type on the document, using a small local vocabulary or the DCMI Type terms such as Text.

Example in RDF

@prefix foaf:    <http://xmlns.com/foaf/0.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .

<https://example.org/id/format/wave>
    foaf:name "WAVE audio" ;
    foaf:page <https://example.org/guides/audio-preservation.html> ,
              <https://example.org/reports/2023-format-survey.pdf> ;
    foaf:isPrimaryTopicOf <https://example.org/formats/wave.html> .

<https://example.org/reports/2023-format-survey.pdf> a foaf:Document ;
    dcterms:title "Format survey 2023" .

Questions about foaf:page

What does foaf:page mean?

It links any thing to a page or document about it. The relation is broad: the document may be entirely about the thing or only discuss it in part. Its range is foaf:Document, and a thing can have any number of pages.

What is the inverse of foaf:page?

The inverse is foaf:topic, which goes from a document to something it is about. Stating foaf:page from the thing implies foaf:topic from the document, so publishers use whichever direction their data naturally starts from.

How is foaf:page related to foaf:homepage?

foaf:homepage is a narrower property. FOAF makes it a sub-property of foaf:isPrimaryTopicOf, which is itself a sub-property of foaf:page. So every homepage is a page, but most pages are not homepages.

Can foaf:page point to a PDF?

Yes. A foaf:Document is any document, not only a web page. A report, a scanned leaflet or a specification in PDF can all be the object of foaf:page. Typing the file as foaf:Document, and describing it with Dublin Core, helps clients present it sensibly.

When should I use dcterms:relation instead of foaf:page?

dcterms:relation links two related resources without saying how they relate. foaf:page says specifically that the document is about the thing. When that is the relationship, foaf:page carries more meaning, and clients can use it directly to build a list of further reading about the thing.

More from FOAF

All 6 in this group