Merge pull request #93 from gchq/gh-62-meta-id

PR for #62 - The Meta element could do with some form of ID/key

event-logging.xsd

@@ -710,6 +710,11 @@
         <xs:documentation>Defines the version of data structure specification.</xs:documentation>
       </xs:annotation>
     </xs:attribute>
+    <xs:attribute name="Id" type="xs:string">
+      <xs:annotation>
+        <xs:documentation>An identifier, name or key to distinguish this block of content from others in the document. It can either be globally unqiue, unique within the document or unique within its siblings.</xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
   </xs:complexType>
   <xs:complexType name="ApprovalComplexType">
     <xs:annotation>

unreleased_changes/20240606_120340_595__62.md

@@ -0,0 +1,24 @@
+* Issue **#62** : Add the `Id` attribute to `AnyContentComplextType`, e.g. `Meta/@Id`. This is to distinguish between multiple sibling `Meta` elements.
+
+
+```sh
+# ********************************************************************************
+# Issue title: The Meta element could do with some form of ID/key
+# Issue link:  https://github.com/gchq/event-logging-schema/issues/62
+# ********************************************************************************
+
+# ONLY the top line will be included as a change entry in the CHANGELOG.
+# The entry should be in GitHub flavour markdown and should be written on a SINGLE
+# line with no hard breaks. You can have multiple change files for a single GitHub issue.
+# The  entry should be written in the imperative mood, i.e. 'Fix nasty bug' rather than
+# 'Fixed nasty bug'.
+#
+# Examples of acceptable entries are:
+#
+#
+# * Issue **123** : Fix bug with an associated GitHub issue in this repository
+#
+# * Issue **namespace/other-repo#456** : Fix bug with an associated GitHub issue in another repository
+#
+# * Fix bug with no associated GitHub issue.
+```