Fix typos in documentation siri_situation.xsd (#147)

* Fix typos in documentation siri_situation.xsd

Fix typos & addition of one annotation missing

* add missing tags to new annotation

it seems that author added a new annotation in previous commit but forgot proper tags.

* correct typo

---------

Co-authored-by: haeckerbaer <54021300+haeckerbaer@users.noreply.github.com>
Co-authored-by: Tim Rivett <56296031+tim-rivett@users.noreply.github.com>

Author: 3 people

xsd/siri_model/siri_situation.xsd

@@ -94,7 +94,7 @@ siri_model\siri_situation-v2.0.xsd:
        -->
 				</Date>
 				<Description>
-					<p>SIRI-SX is an XML schema for the exchange of structured SITUATIONs </p>
+					<p>SIRI-SX is an XML schema for the exchange of structured SITUATIONs</p>
 				</Description>
 				<Format>
 					<MediaType>text/xml</MediaType>
@@ -115,7 +115,7 @@ siri_model\siri_situation-v2.0.xsd:
 				</Rights>
 				<Source>
 					<ul>
-						<li>Schema Derived from the Kizoom XTIS schema </li>
+						<li>Schema Derived from the Kizoom XTIS schema</li>
 					</ul>
 				</Source>
 				<Status>Version 2.1</Status>
@@ -127,7 +127,7 @@ Public transport, Bus services, Coach services, Bus stops and stations,
 Rail transport, Railway stations and track, Train services, Underground trains,
 Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
 Rail transport, Roads and road transport
-     </Category>
+					</Category>
 					<Project>CEN TC278 WG3 SG7</Project>
 				</Subject>
 				<Title>SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema</Title>
@@ -241,7 +241,7 @@ Rail transport, Roads and road transport
 	<!--===PT SITUATION =========================================== -->
 	<xsd:element name="PtSituationElement" type="PtSituationElementStructure">
 		<xsd:annotation>
-			<xsd:documentation>Type for individual IPT ncident.</xsd:documentation>
+			<xsd:documentation>Type for individual PT Incident.</xsd:documentation>
 		</xsd:annotation>
 	</xsd:element>
 	<xsd:complexType name="PtSituationElementStructure">
@@ -296,7 +296,7 @@ Rail transport, Roads and road transport
 	<!--===PT SITUATION =========================================== -->
 	<xsd:element name="RoadSituationElement" type="RoadSituationElementStructure">
 		<xsd:annotation>
-			<xsd:documentation>Type for individual IPT ncident.</xsd:documentation>
+			<xsd:documentation>Type for individual PT incident.</xsd:documentation>
 		</xsd:annotation>
 	</xsd:element>
 	<xsd:complexType name="RoadSituationElementStructure">
@@ -365,7 +365,7 @@ Rail transport, Roads and road transport
 			</xsd:element>
 			<xsd:element name="situationRecordCreationTime" type="D2LogicalModel:DateTime" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier.</xsd:documentation>
+					<xsd:documentation>The date/time that the SITUATION Record object (the first version of the record) was created by the original supplier.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="situationRecordObservationTime" type="D2LogicalModel:DateTime" minOccurs="0">
@@ -380,7 +380,7 @@ Rail transport, Roads and road transport
 			</xsd:element>
 			<xsd:element name="situationRecordVersionTime" type="D2LogicalModel:DateTime" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>The date/time that this current version of the SITUATIONRecord was written into the database of the supplier which is involved in the data exchange.</xsd:documentation>
+					<xsd:documentation>The date/time that this current version of the SITUATION Record was written into the database of the supplier which is involved in the data exchange.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="situationRecordFirstSupplierVersionTime" type="D2LogicalModel:DateTime">
@@ -406,7 +406,7 @@ Rail transport, Roads and road transport
 	</xsd:group>
 	<xsd:group name="Datex2RoadGroup">
 		<xsd:annotation>
-			<xsd:documentation>Datex2 Trrffic element road.</xsd:documentation>
+			<xsd:documentation>Datex2 Traffic element road.</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:element name="impact" type="D2LogicalModel:Impact" minOccurs="0">
@@ -421,7 +421,7 @@ Rail transport, Roads and road transport
 			</xsd:element>
 			<xsd:element name="generalPublicComment" type="D2LogicalModel:Comment" minOccurs="0" maxOccurs="unbounded">
 				<xsd:annotation>
-					<xsd:documentation> Datex 2 comments for public use.</xsd:documentation>
+					<xsd:documentation>Datex 2 comments for public use.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="nonGeneralPublicComment" type="D2LogicalModel:Comment" minOccurs="0" maxOccurs="unbounded">
@@ -448,12 +448,12 @@ Rail transport, Roads and road transport
 	</xsd:group>
 	<xsd:complexType name="AffectedRoadStructure">
 		<xsd:annotation>
-			<xsd:documentation>Type for Raod scope for scope of SITUATION or effect.</xsd:documentation>
+			<xsd:documentation>Type for Road scope for scope of SITUATION or effect.</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:element name="Road" type="D2LogicalModel:RoadsideReferencePointLinear" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Affected Road as described by a Date2x location.</xsd:documentation>
+					<xsd:documentation>Affected Road as described by a Datex 2 location.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:group ref="ProjectionGroup">
@@ -466,7 +466,7 @@ Rail transport, Roads and road transport
 	</xsd:complexType>
 	<xsd:complexType name="OptionalTrafficElementStructure" abstract="true">
 		<xsd:annotation>
-			<xsd:documentation>An event which is not planned by the traffic OPERATOR, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX SITUATION elements.</xsd:documentation>
+			<xsd:documentation>An event which is not planned by the traffic OPERATOR, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex 2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX SITUATION elements.</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:group ref="Datex2ManagementGroup"/>
@@ -527,7 +527,7 @@ Rail transport, Roads and road transport
 			</xsd:element>
 			<xsd:element name="Name" type="NaturalLanguageStringStructure" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Name of for source.</xsd:documentation>
+					<xsd:documentation>Name of Source.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="SourceRole" type="xsd:string" minOccurs="0">
@@ -659,7 +659,7 @@ Rail transport, Roads and road transport
 			</xsd:element>
 			<xsd:element name="Repetitions" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>situation applies only on the repeated day types within the overall validity period(s). For example Sunday.</xsd:documentation>
+					<xsd:documentation>Situation applies only on the repeated day types within the overall validity period(s). For example, Sunday.</xsd:documentation>
 				</xsd:annotation>
 				<xsd:complexType>
 					<xsd:sequence>
@@ -708,7 +708,7 @@ Rail transport, Roads and road transport
 			<xsd:element ref="ReportType" minOccurs="0"/>
 			<xsd:element name="Planned" type="xsd:boolean" default="false" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned.</xsd:documentation>
+					<xsd:documentation>Whether the SITUATION was planned (e.g. engineering works) or unplanned (e.g. service alteration). Default is 'false', i.e. unplanned.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="Keywords" type="xsd:NMTOKENS" minOccurs="0">
@@ -740,7 +740,7 @@ Rail transport, Roads and road transport
 	<xsd:group name="ReasonGroup">
 		<xsd:annotation>
 			<xsd:documentation>Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. 
-Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message!</xsd:documentation>
+Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message!			</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:group ref="TpegReasonGroup">
@@ -794,7 +794,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor
 	</xsd:simpleType>
 	<xsd:simpleType name="NatureEnumeration">
 		<xsd:annotation>
-			<xsd:documentation>Type for Quality of data indication.  </xsd:documentation>
+			<xsd:documentation>Type for Quality of data indication.</xsd:documentation>
 		</xsd:annotation>
 		<xsd:restriction base="xsd:string">
 			<xsd:enumeration value="plannedOnly"/>
@@ -922,7 +922,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor
 			</xsd:element>
 			<xsd:element name="Operators" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Affected OPERATORs, If absent, taken from context. If present, any OPERATORs stated completely replace those from context.</xsd:documentation>
+					<xsd:documentation>Affected OPERATORs. If absent, taken from context. If present, any OPERATORs stated completely replace those from context.</xsd:documentation>
 				</xsd:annotation>
 				<xsd:complexType>
 					<xsd:choice>
@@ -1090,7 +1090,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor
 			</xsd:element>
 			<xsd:element name="Summary" type="DefaultedTextStructure" minOccurs="0" maxOccurs="unbounded">
 				<xsd:annotation>
-					<xsd:documentation>Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description.  (Unbounded since SIRI 2.0)</xsd:documentation>
+					<xsd:documentation>Summary of SITUATION. If absent should be generated from structure elements, and/or by condensing Description.  (Unbounded since SIRI 2.0)</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="Description" type="DefaultedTextStructure" minOccurs="0" maxOccurs="unbounded">
@@ -1278,7 +1278,11 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor
 					<xsd:documentation>Change to normal boarding activity allowed at stop.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
-			<xsd:element name="Delays" type="DelaysStructure" minOccurs="0"/>
+			<xsd:element name="Delays" type="DelaysStructure" minOccurs="0">
+				<xsd:annotation>
+					<xsd:documentation>Information on delays.</xsd:documentation>
+				</xsd:annotation>
+			</xsd:element>
 			<xsd:element name="Casualties" type="CasualtiesStructure" minOccurs="0">
 				<xsd:annotation>
 					<xsd:documentation>Information on casualties.</xsd:documentation>
@@ -1295,7 +1299,7 @@ Note: this means that ReasonName is NOT a complete message, but only a (few) wor
 	<xsd:group name="ConditionGroup">
 		<xsd:annotation>
 			<xsd:documentation>Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. 
-Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message!</xsd:documentation>
+Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message!			</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:element ref="Condition" minOccurs="0" maxOccurs="unbounded">
@@ -1332,7 +1336,7 @@ Note: this means that ConditionName is NOT a complete message, but only a (few)
 			<xsd:documentation>Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. 
 Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message!
 Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message.
-   </xsd:documentation>
+			</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:element name="AdviceRef" type="AdviceRefStructure" minOccurs="0">
@@ -1484,7 +1488,7 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi
 		<xsd:sequence>
 			<xsd:element name="TicketRestrictions" type="TicketRestrictionEnumeration" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Ticket restriction conditiosn in effect. TPEG pti table pti25.</xsd:documentation>
+					<xsd:documentation>Ticket restriction conditions in effect. TPEG pti table pti25.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 			<xsd:element name="Easement" type="NaturalLanguageStringStructure" minOccurs="0" maxOccurs="unbounded">
@@ -1494,7 +1498,7 @@ Alternatively, AdviceRef can be used to reference a (complete) standardised advi
 			</xsd:element>
 			<xsd:element name="EasementRef" type="xsd:normalizedString" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. </xsd:documentation>
+					<xsd:documentation>Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for example "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>
 		</xsd:sequence>