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

   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://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.html">
   8         <label xml:lang="en">Awol</label>
   9         <comment xml:lang="en">
  10                 <p>
  11                         The Atom·Owl Vocabulary, or Awol, was originally an attempt to convert the semantics of <ptr target="(RFC4287)"/> into R·D·F.
  12                         Consequently, it was one of the first vocabularies to tackle the problem of federated blogging—and what we would today call federated social media.
  13                         The specification is full of holes and questions, but never·the·less some aspects of how it handles things are far superior to later, more protocol‐driven federated media approaches.
  14                 </p>
  15                 <p>
  16                         This ontology defines all of Awol, except for :⁠—
  17                 </p>
  18                 <list>
  19                         <item>
  20                                 <p>
  21                                         <resource name="awol:XML"/>, which does not appear in the original Awol documentation and seems to have been quietly added in the six months after publication.
  22                                         This class is of limited utility, as it is not a type of <ref target="awol:PlainText">Plain Text Content</ref>.
  23                                 </p>
  24                         </item>
  25                         <item>
  26                                 <p>
  27                                         The type‐specific properties <resource name="awol:text"/>, <resource name="awol:xhtml"/>, <resource name="awol:html"/>, and <resource name="awol:xml"/>.
  28                                         <ptr target="awol:body"/> can easily accommodate all of these use·cases, altho note that this ontology sets particular restrictions on it, depending on the <ref target="awol:type">media type</ref> of the containing <ref target="awol:Content">Content</ref>.
  29                                 </p>
  30                         </item>
  31                         <item>
  32                                 <p>
  33                                         <resource name="awol:uri"/>, as its intended meaning is conveyed using ordinary R·D·F named nodes.
  34                                         To indicate the <em>preferred</em> I·R·I for a thing, use <ptr target="contact:preferredURI"/>.
  35                                 </p>
  36                         </item>
  37                 </list>
  38                 <p>
  39                         Awol supplies restrictions on the domains and ranges of many properties, and describes many of them as functional, limiting their utility outside of its own data model.
  40                         This ontology maintains the restrictions on the ranges, which can be significant, but loosens the restrictions on the domains and cardinality.
  41                 </p>
  42         </comment>
  43         <type>
  44                 <resource name="dcterms:BibliographicResource"/>
  45         </type>
  46         <type>
  47                 <resource name="dcterms:Standard"/>
  48         </type>
  49         <type>
  50                 <resource name="foaf:Document"/>
  51         </type>
  52 </NamedIndividual>