Fix links to U·R·L¦s

[Vocab] / data / classes / foaf¦Image

diff --git a/data/classes/foaf¦Image b/data/classes/foaf¦Image
index 827500f4eb9d485616599a41ef3eb33f3f5082fb..7311884110621f3b54d504465d55be4fca1c4de7 100644 (file)
--- a/data/classes/foaf¦Image
+++ b/data/classes/foaf¦Image
@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <!--
-SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
+SPDX-FileCopyrightText: 2024, 2025 Lady <https://www.ladys.computer/about/#lady>
 SPDX-License-Identifier: CC0-1.0
 -->
 <!DOCTYPE Class SYSTEM "../../DTD">
@@ -8,10 +8,14 @@ SPDX-License-Identifier: CC0-1.0
        <label xml:lang="en">Image</label>
        <comment xml:lang="en">
                <p>
-                       A <ref target="foaf:Document">Document</ref> which is conveyed as a (still?) image.
+                       A <ref target="foaf:Document">Document</ref> which has a primarily static, visual rendering intent.
                </p>
                <p>
-                       This class is <em>not</em> equated with <ptr target="dcmitype:StillImage"/> because it <em>can</em> encompass images of text, where·as the latter <em>should not</em>.
+                       “Primarily static”, in this definition, implies only that the Document is not intended to show the passage of time, as a video would.
+                       Allowances can be made for atemporal motion.
+               </p>
+               <p>
+                       This class is <em>not</em> equated with <ptr target="dcmitype:StillImage"/> because it <em>can</em> encompass “images” of text, where·as the latter <em>should not</em>.
                        This leaves open the question of what exactly constitutes an “image” in the physical world, but thankfully this class is mostly only ever used for digital images.
                </p>
        </comment>