From b0419acfafbf5dae3b698b33cf017736b89900e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michal=20M=C4=9Bchura?= <michmech@lexiconista.com>
Date: Tue, 19 Dec 2023 20:47:11 +0100
Subject: [PATCH 1/3] issue 52: cardinality of core objects

---
 dmlex-v1.0/specification/core/objectTypes/entry.xml    | 10 ++++++++++
 .../core/objectTypes/lexicographicResource.xml         |  6 ++++++
 2 files changed, 16 insertions(+)

diff --git a/dmlex-v1.0/specification/core/objectTypes/entry.xml b/dmlex-v1.0/specification/core/objectTypes/entry.xml
index 56a38f03..cb06e279 100644
--- a/dmlex-v1.0/specification/core/objectTypes/entry.xml
+++ b/dmlex-v1.0/specification/core/objectTypes/entry.xml
@@ -80,6 +80,16 @@
       the English words "colour" and "color". </para>
   </note>
 
+  <note>
+    <para> DMLex allows entries to contain zero senses. An entry with zero senses is an entry which
+      declares the existence of its headword and, optionally, gives some information about the
+      headword's morphosyntactical properties (part of speech, inflected forms etc.) but does not
+      say anything about its semantics, about its meaning. Such entries can exist as entries which
+      are work in progress, or as entries whose only purpose is to serve as members in
+      entry-to-entry relations (defined in the <olink targetptr="linking">DMLex Linking
+        Module</olink>) such as spelling variants (example: <xref linkend="ex15"/>).</para>
+  </note>
+  
   <note>
     <para>Entries in DMLex do not have an explicit listing order. An application can imply a listing
       order from a combination of the headword and the homograph number, such that the headword is
diff --git a/dmlex-v1.0/specification/core/objectTypes/lexicographicResource.xml b/dmlex-v1.0/specification/core/objectTypes/lexicographicResource.xml
index 21b3c8bf..cd01bec1 100644
--- a/dmlex-v1.0/specification/core/objectTypes/lexicographicResource.xml
+++ b/dmlex-v1.0/specification/core/objectTypes/lexicographicResource.xml
@@ -64,6 +64,12 @@
 	  detailed metadata about the lexicographic resource, implementers are advised to refer to
 	  the properties in the <link linkend="DublinCore">Dublin Core <code>elements</code> namespace</link> as for basic metadata. </para>
     </listitem>
+    <listitem>
+      <para>DMLex allows lexicographic resources to contain zero entries. This is to enable the
+        existence of lexicographic resources which are work in progress, and lexicographic resources
+        whose only purpose is to contain relations (defined in the <olink targetptr="linking">DMLex Linking Module</olink>)
+        that link entries from other lexicographic resources.</para>
+    </listitem>
   </itemizedlist>
 
   <example>

From ef89e6f9e6e4767302353f02c9b658ed99fa4358 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michal=20M=C4=9Bchura?= <michmech@lexiconista.com>
Date: Tue, 19 Dec 2023 21:55:52 +0100
Subject: [PATCH 2/3] issue 54: soundFile

---
 .../specification/core/objectTypes/pronunciation.xml | 12 +++++++++++-
 dmlex-v1.0/specification/dmlex.xml                   |  9 +++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/dmlex-v1.0/specification/core/objectTypes/pronunciation.xml b/dmlex-v1.0/specification/core/objectTypes/pronunciation.xml
index 39e88133..23f0526e 100644
--- a/dmlex-v1.0/specification/core/objectTypes/pronunciation.xml
+++ b/dmlex-v1.0/specification/core/objectTypes/pronunciation.xml
@@ -30,7 +30,9 @@
       <itemizedlist>
         <listitem>
           <para><literal>soundFile</literal>
-            <glossterm>optional</glossterm> (zero or one) and <glossterm>unique</glossterm>. A pointer to a file, such as a filename or a URI, containing a sound recording of the pronunciation</para>
+            <glossterm>optional</glossterm> (zero or one) and <glossterm>unique</glossterm>. An
+            <emphasis>Internationalized Resource Identifier</emphasis> (<link linkend="bib_rfc3987">IRI</link>)
+            pointing to a file which contains a sound recording of the pronunciation</para>
         </listitem>
         <listitem>
           <para><literal><olink targetptr="core_transcription">transcription</olink></literal>
@@ -48,6 +50,14 @@
         <glossterm>optional</glossterm> (zero or more).</para>
     </listitem>
   </itemizedlist>
+  
+  <note>
+    <para>
+      The value of the <literal>soundFile</literal> property is an IRI.
+      This means, among other things, that it can be an internet URL or a relative file path,
+      and can contain non-ASCII characters.
+    </para>
+  </note>
 
   <example>
     <title>XML</title>
diff --git a/dmlex-v1.0/specification/dmlex.xml b/dmlex-v1.0/specification/dmlex.xml
index 9ccfc9be..6a1e821a 100644
--- a/dmlex-v1.0/specification/dmlex.xml
+++ b/dmlex-v1.0/specification/dmlex.xml
@@ -619,6 +619,15 @@
         <title/>
         <bibliomixed id="bcp14">
           <abbrev>BCP 14</abbrev> is a concatenation of [RFC 2119] and [RFC 8174] </bibliomixed>
+        <bibliomixed id="bib_rfc3987">
+          <abbrev>RFC 3987</abbrev>
+          Martin J. Dürst, Michel Suignard,
+          <title>Internationalized Resource Identifiers (IRIs)</title>,
+          <citetitle>
+            <ulink url="https://datatracker.ietf.org/doc/rfc3987/">https://datatracker.ietf.org/doc/rfc3987/</ulink>
+          </citetitle>
+          IETF (Internet Engineering Task Force) RFC 3987, January 2005.
+        </bibliomixed>
         <bibliomixed id="rfc2119"><abbrev>RFC 2119</abbrev> S. Bradner, <title>Key words for use in
             RFCs to Indicate Requirement Levels</title>, <citetitle>
             <ulink url="https://www.ietf.org/rfc/rfc2119.txt"

From 4437ab87382858f1a79d3d37bfbcdb0c2da2193d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michal=20M=C4=9Bchura?= <michmech@lexiconista.com>
Date: Tue, 19 Dec 2023 22:02:54 +0100
Subject: [PATCH 3/3] issue 56: remove uniquness constraint on relation

---
 .../specification/modules/linking/objectTypes/relation.xml    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dmlex-v1.0/specification/modules/linking/objectTypes/relation.xml b/dmlex-v1.0/specification/modules/linking/objectTypes/relation.xml
index 916b3109..9d804e46 100644
--- a/dmlex-v1.0/specification/modules/linking/objectTypes/relation.xml
+++ b/dmlex-v1.0/specification/modules/linking/objectTypes/relation.xml
@@ -22,7 +22,7 @@
     <title>Properties</title>
     <listitem>
       <para><literal>type</literal>
-        <glossterm>required</glossterm> (exactly one) and <glossterm>unique</glossterm> (in combination with all <literal>member</literal>) properties. Non-empty string. Specifies what type of
+        <glossterm>required</glossterm> (exactly one). Non-empty string. Specifies what type of
         relation it is, for example a relation between synonyms or a relation between a sense and a
         subsense. Optionally, <code><olink targetptr="linking_relationType"
           >relationType</olink></code> objects can be used to explain those types and to constrain
@@ -35,7 +35,7 @@
     </listitem>
     <listitem>
       <para><literal><olink targetptr="linking_member">member</olink></literal>
-        <glossterm>required</glossterm> (two or more) and <glossterm>unique</glossterm> (in combination with <literal>type</literal>).</para>
+        <glossterm>required</glossterm> (two or more).</para>
     </listitem>
   </itemizedlist>