Skip to content

Commit

Permalink
Merge pull request #127 from jmccrae/issue-123
Browse files Browse the repository at this point in the history
Add clarity to uniqueness constraints
  • Loading branch information
michmech authored Jun 3, 2024
2 parents 2d6eed7 + 968373b commit 46b5afc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion dmlex-v1.0/specification/dmlex.xml
Original file line number Diff line number Diff line change
Expand Up @@ -447,7 +447,7 @@
<para>
Some object types defined in DMLex have a property or a combination of properties mandated to be unique.
Designating a property as unique means that its value must be unique within the scope of its parent object type.
Designating a combination of properties as unique means that the ordered composition of its values must be unique within the scope of their parent object type. Such unique properties in DMLex serve two purposes:
Designating a combination of properties as unique means that the ordered composition of its values must be unique within the scope of their parent object type. In the case that all unique properties are missing, <code>listingOrder</code> <glossterm>must</glossterm> be used to verify uniqueness. Such unique properties in DMLex serve two purposes:
</para>
<itemizedlist>
<listitem>
Expand Down

0 comments on commit 46b5afc

Please sign in to comment.