W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > September 2018

Re: [dxwg] foaf:homepage vs. dcat:landingPage

From: Dan Brickley via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Sep 2018 18:37:20 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-423289011-1537468639-sysbot+gh@w3.org>
@makxdekkers is correct, the idea in FOAF/RDFWeb was to facilitate (rather than require) "reference by description". If you know for example that there is a company whose name is Apple, whose homepage is https://www.apple.com/, ... that is a pretty strong referring expression. So we made part of the concept of "homepage" the idea that there's a single thing whose homepage it is. It is not a particularly odd or obscure constraint, e.g. see @rvguha's [paper](https://ai.google/research/pubs/pub44679) on related theoretical issues.

In FOAF we then generalized this pattern to cases where you wouldn't intuitively want to call it a "homepage". The FOAF name for this was [isPrimaryTopicOf](http://xmlns.com/foaf/spec/#term_isPrimaryTopicOf). In Schema.org, we can used the less verbose "http://schema.org/sameAs" relationship, but the idea is similar: a relationship between something and a (relatively well known) page primarily about it. Another related relation is https://schema.org/mainEntityOfPage which drops the expectation that the page/document is well known. Some notes on these overlaps are at https://schema.org/docs/datamodel.html#mainEntityBackground

GitHub Notification of comment by danbri
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/352#issuecomment-423289011 using your GitHub account
Received on Thursday, 20 September 2018 18:37:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:45 UTC