Whitespace cleanup in metadata metaschema

src/metaschema/oscal_metadata_metaschema.xml

@@ -333,14 +333,7 @@
                             </index-has-key>
                         </constraint>
                         <remarks>
-                            <p>Since the reference target of an organizational affiliation must be
-                                another  <code>party</code> (whether further qualified as person or
-                                organization) as inidcated by its <code>uuid</code>. As a <a
-                                    href="/concepts/identifier-use/#machine-oriented"
-                                    >machine-oriented</a> identifier with uniqueness across document
-                                and trans-document scope, this <code>uuid</code> value is sufficient
-                                to reference the data item locally or globally across related
-                                documents, e.g., in an imported OSCAL instance. </p>
+                            <p>Since the reference target of an organizational affiliation must be another <code>party</code> (whether further qualified as person or organization) as inidcated by its <code>uuid</code>. As a <a href="/concepts/identifier-use/#machine-oriented" >machine-oriented</a> identifier with uniqueness across document and trans-document scope, this <code>uuid</code> value is sufficient to reference the data item locally or globally across related documents, e.g., in an imported OSCAL instance. </p>
                             <p>Parties of both the <code>person</code> or <code>organization</code> type can be associated with an organization using the <code>member-of-organization</code>.</p>
                         </remarks>
                     </define-field>
@@ -525,16 +518,7 @@
                     <description>A unique identifier for a resource, for referencing across document
                         and trans-document scope.</description>
                     <remarks>
-                        <p>A <a href="/concepts/identifier-use/#machine-oriented"
-                                >machine-oriented</a>, <a
-                                href="/concepts/identifier-use/#globally-unique">globally unique</a>
-                            identifier with <a href="/concepts/identifier-use/#cross-instance"
-                                >cross-instance</a> scope that can be used to reference this defined
-                            resource elsewhere in <a href="/concepts/identifier-use/#scope">this or
-                                other OSCAL instances</a>. This UUID should be assigned <a
-                                href="/concepts/identifier-use/#consistency">per-subject</a>, which
-                            means it should be consistently used to identify the same subject across
-                            revisions of the document.</p>
+                        <p>A <a href="/concepts/identifier-use/#machine-oriented" >machine-oriented</a>, <a href="/concepts/identifier-use/#globally-unique">globally unique</a> identifier with <a href="/concepts/identifier-use/#cross-instance" >cross-instance</a> scope that can be used to reference this defined resource elsewhere in <a href="/concepts/identifier-use/#scope">this or other OSCAL instances</a>. This UUID should be assigned <a href="/concepts/identifier-use/#consistency">per-subject</a>, which means it should be consistently used to identify the same subject across revisions of the document.</p>
                     </remarks>
                     <!-- identifier declaration -->
                 </define-flag>
@@ -769,13 +753,8 @@
             <description>A textual label that provides a sub-type or characterization of the
                 property's <code>name</code>.</description>
             <remarks>
-                <p>This can be used to further distinguish or discriminate between the semantics of
-                    multiple properties of the same object with the same <code>name</code> and
-                        <code>ns</code>, or to group properties into categories.</p>
-                <p>A <code>class</code> can be used in validation rules to express extra constraints
-                    over named items of a specific <code>class</code> value. It is available for
-                    grouping, but unlike <code>group</code> is not expected specifically to
-                    designate any group membership as such.</p>
+                <p>This can be used to further distinguish or discriminate between the semantics of multiple properties of the same object with the same <code>name</code> and <code>ns</code>, or to group properties into categories.</p>
+                <p>A <code>class</code> can be used in validation rules to express extra constraints over named items of a specific <code>class</code> value. It is available for grouping, but unlike <code>group</code> is not expected specifically to designate any group membership as such.</p>
             </remarks>
         </define-flag>
         <define-flag name="group" as-type="token">
@@ -1132,17 +1111,10 @@
             </remarks>
         </define-flag>
         <remarks>
-            <p>A document identifier provides a <a href="/concepts/identifier-use/#globally-unique"
-                    >globally unique</a> identifier with a <a
-                    href="/concepts/identifier-use/#cross-instance">cross-instance</a> scope that is
-                used for a group of documents that are to be treated as different versions,
-                representations or digital surrogates of the same document.</p>
+            <p>A document identifier provides a <a href="/concepts/identifier-use/#globally-unique" >globally unique</a> identifier with a <a href="/concepts/identifier-use/#cross-instance">cross-instance</a> scope that is used for a group of documents that are to be treated as different versions, representations or digital surrogates of the same document.</p>
             <p>A document identifier provides an additional data point for identifying a document that can be assigned by a publisher or organization for purposes in a wider system, such as a digital object identifier (DOI) or a local content management system identifier.</p>
             <p>Use of a document identifier allows for document creators to associate sets of documents that are related in some way by the same <code>document-id</code>.</p>
-            <p>An OSCAL document always has an implicit document identifier provided by the
-                document's UUID, defined by the <code>uuid</code> on the top-level object. Having a
-                default UUID-based identifier ensures all documents can be minimally identified when
-                other document identifiers are not provided.</p>
+            <p>An OSCAL document always has an implicit document identifier provided by the document's UUID, defined by the <code>uuid</code> on the top-level object. Having a default UUID-based identifier ensures all documents can be minimally identified when other document identifiers are not provided.</p>
         </remarks>
     </define-field>
 </METASCHEMA>