Lady’s Gitweb - Vocab/blob - data/named_individuals/_FOAF_

   1 <?xml version="1.0"?>
   2 <!--
   3 SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
   4 SPDX-License-Identifier: CC0-1.0
   5 -->
   6 <!DOCTYPE NamedIndividual SYSTEM "../../DTD">
   7 <NamedIndividual name="http://xmlns.com/foaf/spec/">
   8         <label xml:lang="en">F·O·A·F</label>
   9         <comment xml:lang="en">
  10                 <p>
  11                         F·O·A·F is an early and widely‐used vocabulary which grew some·what organically within the R·D·F·Web community.
  12                         It is not necessarily weldesigned in all respects, but it has been commonly deployed as a vocabulary for modelling <ref target="foaf:Agent">Agents</ref>, and is often used alongside <ptr target="(DCMI)"/> (which models the things they <ref target="foaf:made">make</ref>).
  13                         D·C·M·I and F·O·A·F have a <ref target="https://www.dublincore.org/collaborations/foaf/good_neighbour_agreement/">good neighbour agreement</ref> formalizing the fact that the two vocabularies often go hand‐in‐hand.
  14                 </p>
  15                 <p>
  16                         Due to its organically‐developed nature, terms in F·O·A·F were given a <ref target="vocabstatus:term_status">status</ref>, meant to indicate how stable their definitions ought to be considered.
  17                         These statuses have not been updated in over a decade, and are not preserved here; however, a status of at least <value datatype="xsd:string">testing</value> was deemed a criterion for inclusion.
  18                 </p>
  19                 <p>
  20                         Otherwise, this ontology provides definitions for the bulk of F·O·A·F, wilfully excluding the following properties :⁠—
  21                 </p>
  22                 <list>
  23                         <item>
  24                                 <p>
  25                                         <resource name="foaf:interest"/>, <resource name="foaf:schoolHomepage"/>, and <resource name="foaf:workplaceHomepage"/> are roundabout terms which indicate <ref target="foaf:Document">Documents</ref> which <ref target="foaf:primaryTopic">have a primary topic</ref> of a thing, rather than just indicating the thing itself.
  26                                         This was a pragmatic choice by the authors of F·O·A·F because it was assumed these documents would have more welknown, and thus easily-queryable, I·R·I¦s.
  27                                         But R·D·F tooling and understanding has significantly matured in the years since these properties were introduced, and they are far from bestpractice now.
  28                                         (Just make a bloody blank node!)
  29                                 </p>
  30                         </item>
  31                         <item>
  32                                 <p>
  33                                         <resource name="foaf:mbox"/> and <resource name="foaf:mbox_sha1sum"/> are properties for identifying the original, not current, owner of an internet mailbox, and thus not useful for the actual sending of messages.
  34                                         Originally, these properties were conceived as a means of determining <ref target="foaf:Agent">Agent</ref> identity; in the case of <resource name="foaf:mbox"/>, this intent is much better served by just using a <code>tag:</code> U·R·I, which can be email‐derived.
  35                                         <resource name="foaf:mbox_sha1sum"/> is of questionable utility in practice.
  36                                 </p>
  37                         </item>
  38                         <item>
  39                                 <p>
  40                                         <resource name="foaf:PersonalProfileDocument"/> is a subclass of <ref target="foaf:Document">Document</ref> which is used for R·D·F documents whose <ref target="foaf:primaryTopic">primary topic</ref> is their <ref target="foaf:maker">maker</ref>.
  41                                         But this relationship is more useful stated explicitly (i·e, with properties), and the class offers little.
  42                                 </p>
  43                         </item>
  44                         <item>
  45                                 <p>
  46                                         A number of properties (<resource name="foaf:aimChatID"/>, <resource name="foaf:icqChatID"/>, <resource name="foaf:jabberID"/>, <resource name="foaf:msnChatID"/>, <resource name="foaf:skypeID"/>, <resource name="foaf:yahooChatID"/>) are tied to specific online platforms; these are better served by the generic properties surrounding <ref target="foaf:OnlineAccount">Online Accounts</ref>.
  47                                 </p>
  48                         </item>
  49                         <item>
  50                                 <p>
  51                                         <resource name="foaf:myersBriggs"/>, for lack of any strong argument for inclusion.
  52                                 </p>
  53                         </item>
  54                 </list>
  55                 <p>
  56                         F·O·A·F also makes use of a single class in the <code>geo:</code> name·space, <ptr target="geo:SpatialThing"/>.
  57                         This ontology like·wise adopts this term.
  58                 </p>
  59         </comment>
  60         <type>
  61                 <resource name="dcterms:BibliographicResource"/>
  62         </type>
  63         <type>
  64                 <resource name="dcterms:Standard"/>
  65         </type>
  66         <type>
  67                 <resource name="foaf:Document"/>
  68         </type>
  69 </NamedIndividual>