You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
foaf:homepage is an inverse functional property (IFP) which means that it SHOULD be unique and precisely identify the catalog. This allows smushing various descriptions of the catalog when different URIs are used.
The point is that the foaf:homepage is the canonical webpage for a Catalog. This is implied by the fact that foaf:homepageis defined (in FOAF) as an inverse-functional-property. The 'smushing' text is just a commentary or interpretation of the implication of IFP in the DCAT context, as there might be more than one web-page for a dcat:Catalog (or any other dcat:Resource for that matter).
I propose adjusting the usage note to the following:
foaf:homepage is an inverse functional property (IFP) which means that it SHOULD be unique and precisely identify the web-page for the catalog. This property indicates the canonical web-page, which might be helpful in cases where there is more than one web-page about the catalog.
The text was updated successfully, but these errors were encountered:
@smrgeoinfo a reasoner will infer that if there are two subjects for the inverse functional property, they are the same and raise a conflict if that is not possible due to other axioms
Respond to comment from @smrgeoinfo - https://lists.w3.org/Archives/Public/public-dxwg-comments/2018Nov/0007.html
This text was copied from DCAT-2014:
The point is that the
foaf:homepage
is the canonical webpage for a Catalog. This is implied by the fact thatfoaf:homepage
is defined (in FOAF) as an inverse-functional-property. The 'smushing' text is just a commentary or interpretation of the implication of IFP in the DCAT context, as there might be more than one web-page for adcat:Catalog
(or any otherdcat:Resource
for that matter).I propose adjusting the usage note to the following:
The text was updated successfully, but these errors were encountered: