additions/corrections from TC meeting of 7 August

dmlex-v1.0/specification/core/objectTypes/definition.xml

@@ -14,14 +14,14 @@
   <para>Represents one of possibly several definitions of a sense.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_sense">sense</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>text</literal>
         <glossterm>required</glossterm> (exactly one). Non-empty string. A statement, in the same

dmlex-v1.0/specification/core/objectTypes/entry.xml

@@ -13,15 +13,15 @@
   <para>Represents a dictionary entry. An entry contains information about one headword.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_lexicographicResource"
           >lexicographicResource</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>id</literal>
         <glossterm>optional</glossterm> (zero or one). An unique identifier of the entry. Entries
@@ -79,8 +79,8 @@
   </note>
 
   <note>
-    <para> DMLex allows only one headword per entry. Things like variant headwords do not exist in
-      DMLex. However, the <olink targetptr="linking">DMLex Linking Module</olink> does make it
+    <para> DMLex allows only one headword per entry. Things such as  variant headwords do not exist
+      in DMLex. However, the <olink targetptr="linking">DMLex Linking Module</olink> does make it
       possible to represent the existence of variants by treating them as separate headwords of
       separate entries, and linking the entries using a type of link which will cause the entries to
       be placed together when shown to human users. See <xref linkend="ex15"/> for an example using
@@ -89,7 +89,7 @@
 
   <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
+      order from a combination of the headword and the homograph number, such that the headword is
       the primary sorting key and the homograph number (for entries that have one) is the secondary
       sorting key.</para>
   </note>

dmlex-v1.0/specification/core/objectTypes/example.xml

@@ -15,14 +15,14 @@
     used.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_sense">sense</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>text</literal>
         <glossterm>required</glossterm> (exactly one). Non-empty string. The example itself.</para>

dmlex-v1.0/specification/core/objectTypes/inflectedForm.xml

@@ -15,14 +15,14 @@
       linkend="ex01"/>.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_entry">entry</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>tag</literal>
         <glossterm>optional</glossterm> (zero or one). Non-empty string. An abbreviation, a code or
@@ -97,10 +97,11 @@
   <itemizedlist>
     <title>Comments</title>
     <listitem>
-      <para>The <code>inflectedForm</code> object is intended to model the <emphasis role="strong"
-          >inflectional morphology</emphasis> of a headword. To model derivational morphology, for
-        example feminine forms of maculine nouns, the recommended way to do that in DMLex is to
-        create separate entries for the two words, and link them using the <olink targetptr="linking">Linking Module</olink>.</para>
+      <para>The <code>inflectedForm</code> object type is intended to model the <emphasis
+          role="strong">inflectional morphology</emphasis> of a headword. To model derivational
+        morphology, for example feminine forms of maculine nouns, the recommended way to do that in
+        DMLex is to create separate entries for the two words, and link them using the <olink
+          targetptr="linking">Linking Module</olink>.</para>
     </listitem>
   </itemizedlist>
 

dmlex-v1.0/specification/core/objectTypes/label.xml

@@ -16,7 +16,7 @@
     (singular-only).</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_entry">entry</olink></literal></para>
     </listitem>
@@ -35,7 +35,7 @@
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>tag</literal>
         <glossterm>required</glossterm> (exactly one). Non-empty string. An abbreviation, a code or

dmlex-v1.0/specification/core/objectTypes/lexicographicResource.xml

@@ -12,23 +12,23 @@
   </title>
   <para>Represents a dictionary. A lexicographic resource is a dataset which can be used, viewed and
     read by humans as a dictionary and – simultaneously – ingested, processed and understood by
-    software agents as a machine-readable database.</para>
+    software agents as a machine-readable dataset.</para>
 
   <note>
     <para>The correct name of this data type in
       DMLex is <emphasis>lexicographic</emphasis>, not <emphasis>lexical</emphasis>, resource.</para>
   </note>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>title</literal>
         <glossterm>optional</glossterm> (zero or one). Non-empty string. A human-readable title of
         the lexicographic resource.</para>
     </listitem>
     <listitem>
       <para><literal>uri</literal>
-        <glossterm>optional</glossterm> (zero or one). The URI of the lexicographic resource,
+        <glossterm>required</glossterm> (zero or one). The URI of the lexicographic resource,
         identifying it on the Web.</para>
     </listitem>
     <listitem>
@@ -50,26 +50,21 @@
         <code>language</code> identifies the language of headwords, definitions and examples in this
         dictionary. DMLex is based on the assumption that all headwords in a lexicographic resource
         are in the same language, and that definitions and examples, if any are included in the
-        lexicographic resource, are in that language too. The <code>language</code> child object of
+        lexicographic resource, are in that language too. The <code>language</code> property of
           <code>lexicographicResource</code> informs potential users of the lexicographic resource
         which language that is.</para>
     </listitem>
-    <listitem>
-      <para>The main role of a lexicographic resource is to contain entries (<code>entry</code>
-        objects). The other object type that can optionally occur inside a
-          <code>lexicographicResource</code>, <code>tag</code>, is for lists of look-up values such
-        as part-of-speech labels.</para>
-    </listitem>
     <listitem>
       <para>Ideally, a lexicographic resouce should include at least one entry. However, DMLex
         specifies that <code>entry</code> is optional in <code>lexicographicResouce</code> to allow
         for the existence of lexicographic resources which are not yet complete. </para>
     </listitem>
     <listitem>
-      <para>The <code>lexicographicResource</code> data type does not contain fields for detailed metadata
-      about the lexicographic resource, such as author, editor, publisher, copyright status or publication year.
-      Describing these properties of lexicographic resources is outside the scope of DMLex. DMLex is a formalism
-      for modelling the internal structure of a lexicographic resource, not its metadata.</para>
+      <para>The <code>lexicographicResource</code> data type does not contain properties for
+        detailed metadata about the lexicographic resource, such as author, editor, publisher,
+        copyright status or publication year. Describing these properties of lexicographic resources
+        is outside the scope of DMLex. DMLex is a formalism for modelling the internal structure of
+        a lexicographic resource, not its metadata.</para>
     </listitem>
   </itemizedlist>
 

dmlex-v1.0/specification/core/objectTypes/partOfSpeech.xml

@@ -14,14 +14,14 @@
   <para>Represents a part-of-speech label.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_entry">entry</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>tag</literal>
         <glossterm>required</glossterm> (exactly one). Non-empty string. An abbreviation, a code or
@@ -45,7 +45,7 @@
     <listitem>
       <para>The way to model other grammatical properties of the headword besides part of speech,
         such as gender (of nouns) or aspect (of verbs) in DMLex is to combine them with the part of
-        speech into a single part-of-speech label, for example <code>noun-masc</code> and
+        speech into a single part-of-speech tag, for example <code>noun-masc</code> and
           <code>noun-fem</code>, or <code>v-perf</code> and <code>v-imperf</code>.</para>
     </listitem>
   </itemizedlist>

dmlex-v1.0/specification/core/objectTypes/pronunciation.xml

@@ -14,7 +14,7 @@
   <para>Represents the pronunciation of its parent. Examples: <xref linkend="ex02"/>, <xref linkend="ex03"/>, <xref linkend="ex04"/>.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_entry">entry</olink></literal></para>
     </listitem>
@@ -24,7 +24,7 @@
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para>At least one of:</para>
       <itemizedlist>

dmlex-v1.0/specification/core/objectTypes/sense.xml

@@ -14,14 +14,14 @@
   <para>Represents one of possibly many meanings (or meaning potentials) of the headword.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_entry">entry</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>id</literal>
         <glossterm>optional</glossterm> (zero or one). A unique identifier of the sense. Senses
@@ -57,13 +57,13 @@
   <itemizedlist>
     <title>Comments</title>
     <listitem>
-      <para>The contents of <emphasis role="strong">entry</emphasis> are, apart from
+      <para>The properties of <emphasis role="strong">entry</emphasis> are, apart from
           <code>sense</code>, formal properties of the headword such as orthography, morphology,
         syntax and pronunciation. A <emphasis role="strong">sense</emphasis> is a container for
         statements about the headword's semantics. DMLex deliberately makes it impossible to include
-        morphological information at sense level. It is impossible inm DMLex to model an entry where
+        morphological information at sense level. It is impossible in DMLex to model an entry where
         each sense has slightly different morphological properties (eg. a noun has a weak plural in
-        one sense and a strong plural in another). Such phenomena need to be treatedas two entries
+        one sense and a strong plural in another). Such phenomena need to be treated as two entries
         (homographs) and can be linked using the Linking Module to make sure they are always shown
         together to human users.</para>
     </listitem>

dmlex-v1.0/specification/core/objectTypes/transcription.xml

@@ -14,14 +14,14 @@
   <para>Represents the transcription of a pronunciation in some notation such as IPA.</para>
 
   <itemizedlist>
-    <title>Child of</title>
+    <title>Property of</title>
     <listitem>
       <para><literal><olink targetptr="core_pronunciation">pronunciation</olink></literal></para>
     </listitem>
   </itemizedlist>
 
   <itemizedlist>
-    <title>Contents</title>
+    <title>Properties</title>
     <listitem>
       <para><literal>text</literal>
         <glossterm>required</glossterm> (exactly one). Non-empty string. The actual