-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathPresenceHealth.xsd
410 lines (410 loc) · 37.2 KB
/
PresenceHealth.xsd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
<?xml version='1.0' encoding='UTF-8' ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sawsdl="http://www.w3.org/ns/sawsdl" xmlns:m="org.FTT.fts#" targetNamespace="org.FTT.fts#" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="PresenceHealth" type="m:PresenceHealth"/>
<xs:complexType name="PresenceHealth">
<xs:sequence>
<xs:element name="Event" type="m:Event" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="Event" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event">
<xs:annotation>
<xs:documentation>represents a TAK event: this class is instantiated with a standard set of values.</xs:documentation>
<xs:documentation> The opex field is intended to indicate that the event is part of a live operation, an exercise, or a simulation. For backward compatibility, absence of the opex indicates "no statement", which will be interpreted in an installation specific manner.</xs:documentation>
<xs:documentation> </xs:documentation>
<xs:documentation> opex="o-&lt;name&gt;" or "e-&lt;nickname&gt;" or "s-&lt;nickname&gt;",</xs:documentation>
<xs:documentation> where "-&lt;name&gt;" is optional. That is, it is permissible to specify only "o", "e", or "s" for the opex value.</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> o = operations</li></xs:documentation>
<xs:documentation> <li> e = exercise</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> s = simulation</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="access" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.access">
<xs:annotation>
<xs:documentation>Specifies access controls that should be applied to the event</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="how" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.how">
<xs:annotation>
<xs:documentation>Gives a hint about how the coordinates were generated. It is used specifically to relay a hint about the types of errors that may be expected in the data and to weight the data in systems that fuse multiple inputs.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="time" minOccurs="1" maxOccurs="1" type="xs:long" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.time">
<xs:annotation>
<xs:documentation>time stamp with respect to Zulu time indicating when an event was generated in extended ISO 8601 format </xs:documentation>
<xs:documentation>in ProtoBuff expressed is in milliseconds</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="type" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.type">
<xs:annotation>
<xs:documentation>Event.type contains the Code for the Center on Target object. It Defines what the Event is about. An event may describe a physical object, a set of raw, unprocessed bits, or a tasking. </xs:documentation>
<xs:documentation># Hierarchically organized hint about event type (<b>default </b>is 'a-f-G-I' for "Friendly Ground infrastructure)</xs:documentation>
<xs:documentation>The "type" attribute is a composite of components delimited by the semi-colon character. The first component of this composite attribute is defined below.</xs:documentation>
<xs:documentation> Future versions of this schema will define other components which we expect will aid in machine filtering. Despite the exclusion of definitions for additional components in this version of the schema, users of this schema should expect and design an optional trailing field delimited by the semi-colon character. This field can be ignored.</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> <font color="#a52a2a"><i>component1</i></font>;<font color="#32cd32">optional field</font></li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> The first component (<font color="#a52a2a">component1</font>) is a hierarchically organized hint about type.</xs:documentation>
<xs:documentation> The intention is that this hierarchy be flexible and extensible and facilitate simple filtering, translation and display. To facilitate filtering, the hierarchy needs to present key fields in an easily parsed and logical order. To facilitate this, this component is a composite of fields separated by the "-" punctuation character, so a valid type would be: x-x-X-X-x. Using a punctuation for field separation allows arbitrary expansion of the type space, </xs:documentation>
<xs:documentation><i>e.g., a-fzp-mlk-gm-...</i></xs:documentation>
<xs:documentation> Field meanings are type specific. That is, the third field of an "<u>atom</u>" type may represent air vs. ground while the same field for a "<u>reservation</u>" type may represent purpose.</xs:documentation>
<xs:documentation><b><u>MEANING of 'a' in the first position</u></b> </xs:documentation>
<xs:documentation>The "Atoms" portion of the type tree requires some additional explanation past the taxonomy defined below. The "Atoms" portion of the type tree contains CoT defined fields and part of the <b>MIL-STD-2525</b> type definition. <u>To distinguish MIL-STD-2525 type strings from CoT defined fields, the MIL-STD-2525 types must be represented in all upper case</u>. Differentiation of type namespace with upper/lower case facilitates extension of CoT types and MIL-STD-2525 types without name space conflict. An example:</xs:documentation>
<xs:documentation> <font color="#008080">a</font>-<font color="#006400">f</font>-<font color="#dc143c"><b>A-B-C</b></font>-<font color="#00ffff">x</font> </xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>a = Atom</li></xs:documentation>
<xs:documentation> <li><font color="#006400">f</font> = attitude or disposition (friendly in this case)</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>A-B-C =the SDIC 2525 separated by dashs</li></xs:documentation>
<xs:documentation> <li><font color="#00ffff">x</font> = COT specific extension</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> The organization of CoT and MIL-STD-2525 types can be determined from the taxonomy below, but additional details are provided here.</xs:documentation>
<xs:documentation> The "Atoms" portion of the "type" tree contains the "Battle Dimension" and "Function ID" fields taken from MIL-STD-2525.</xs:documentation>
<xs:documentation> "Battle Dimension" is a single character taken from MIL-STD-2525 and is located in the position 5. </xs:documentation>
<xs:documentation>a-.-<font color="#dc143c"><b>G</b></font>-I-M-N-B</xs:documentation>
<xs:documentation>&nbsp;</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>P - Space</li></xs:documentation>
<xs:documentation> <li>A - Air</li></xs:documentation>
<xs:documentation> <li>G - Ground</li></xs:documentation>
<xs:documentation> <li>S - Sea Surface</li></xs:documentation>
<xs:documentation> <li>U - Sea Subsurface</li></xs:documentation>
<xs:documentation> <li>SF - Special Operations Forces</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> The typical 2525 representation for "Function ID" is three groups of two characters separated by a space (e.g. "12 34 56"). The CoT schema maps this to a "-" delimited list of characters. (e.g. "1-2-3-4-5-6").</xs:documentation>
<xs:documentation> The concatenation of the "Battle Dimension" and "Function ID" fields from the MIL-STD-2525 specification represented in the CoT schema will be as follows:</xs:documentation>
<xs:documentation> battle dimension-<font color="#a52a2a">func id char1</font>-func id char2- ... -func id char6</xs:documentation>
<xs:documentation> When an appropriate MIL-STD-2525 type exists, it should be used. If there is a MIL-STD-2525 representation which is close, but may be refined, a CoT extension to the 2525 type can be appended.</xs:documentation>
<xs:documentation> for example: </xs:documentation>
<xs:documentation>a-h-X-X-X-X-X-<b>i</b> might represent hostile MIL-STD-2525 type X-X-X-X-X of <b>Israeli </b>(the 'i'<b>) </b>manufacture. Again, the<u> CoT extension uses lower case</u>. </xs:documentation>
<xs:documentation> Conceptually, this extension defines further branching from the nearest MIL-STD-2525 tree point.</xs:documentation>
<xs:documentation> If no appropriate 2525 representation exists, a type definition can be added to the CoT tree defined here. The resulting definition would be represented in all lower case. For example</xs:documentation>
<xs:documentation> a-h-G-p-i</xs:documentation>
<xs:documentation> might define atoms-hostile-Ground-photon cannon-infrared.</xs:documentation>
<xs:documentation> The taxonomy currently looks like this: Note that the coding of the sub fields are determined entirely by the preceding fields!) The current type tree is defined here. </xs:documentation>
<xs:documentation> <b>+--- First position, this event describes</b></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> a - Atoms - this event describes an actual "thing"</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> <b> +--- 2nd CoT affiliation of these atoms</b></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li><b> </b> p - Pending</li></xs:documentation>
<xs:documentation> <li> u - Unknown</li></xs:documentation>
<xs:documentation> <li> a - Assumed friend</li></xs:documentation>
<xs:documentation> <li> f - Friend</li></xs:documentation>
<xs:documentation> <li> n - Neutral</li></xs:documentation>
<xs:documentation> <li> s - Suspect</li></xs:documentation>
<xs:documentation> <li> h - Hostile</li></xs:documentation>
<xs:documentation> <li> j - Joker</li></xs:documentation>
<xs:documentation> <li> k - Faker</li></xs:documentation>
<xs:documentation> <li> o - None specified</li></xs:documentation>
<xs:documentation> <li> x - Other</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><b> +--- Battle dimension</b></xs:documentation>
<xs:documentation><b> | Taken from MIL-STD-2525 "Battle Dimension" (upper case)</b></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li><b> </b>P - Space</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>A - Air</li></xs:documentation>
<xs:documentation> <li>G - Ground</li></xs:documentation>
<xs:documentation> <li>S - Sea Surface</li></xs:documentation>
<xs:documentation> <li>U - Sea Subsurface</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>SF - Special Operations Forces</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> <b> +--- Function (dimension specific!)</b></xs:documentation>
<xs:documentation><b> </b><i>See MIL-STD-2525B specification for function fields (must be upper case) </i></xs:documentation>
<xs:documentation> Any number of char before the first “dash”, it express also the hierarchy</xs:documentation>
<xs:documentation>(Hundreds of options)</xs:documentation>
<xs:documentation><b> +--- The event describes ...</b></xs:documentation>
<xs:documentation><b> </b> <b>b - Bits </b>- Events in the "Bit" group (pos 1163++ ) carry meta information about raw data sources. For example, range-doppler radar returns or SAR imagery represent classes of information that are "bits". However, tracks derived from such sources represent objects on the battlespace and this have event type "A-..."</xs:documentation>
<xs:documentation> The intention with the "Bit" type is to facilitate the identification of germane information products.</xs:documentation>
<xs:documentation> This hierarchy is not intended to replace more detailed domain-specific meta information (such as that contained in NITF image headers or the GMTI data formats), rather it is intended to provide a domain-neutral mechanism for rapid filtering of information products.</xs:documentation>
<xs:documentation><b> +--- Dimension </b></xs:documentation>
<xs:documentation>second position, Like battle dimension but for 'b' types</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> <font color="#006400"> i - Imagery</font></li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ol></xs:documentation>
<xs:documentation> <li> e - Electro-optical</li></xs:documentation>
<xs:documentation> <li> i - Infra red</li></xs:documentation>
<xs:documentation> <li> s - SAR</li></xs:documentation>
<xs:documentation> <li> v - video</li></xs:documentation>
<xs:documentation></ol></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> ...</li></xs:documentation>
<xs:documentation> <li> r - Radar</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ol></xs:documentation>
<xs:documentation> <li> <font color="#006400"> m - MTI data</font></li></xs:documentation>
<xs:documentation></ol></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> ...</li></xs:documentation>
<xs:documentation> <li> <font color="#006400"> d - Sensor detection events</font></li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ol></xs:documentation>
<xs:documentation> <li> s - Seismic</li></xs:documentation>
<xs:documentation> <li> d - Doppler</li></xs:documentation>
<xs:documentation> <li> a - Acoustic</li></xs:documentation>
<xs:documentation> <li> m - Motion (e.g., IR)</li></xs:documentation>
<xs:documentation></ol></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> m - Mapping</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><ol></xs:documentation>
<xs:documentation> <li> p - Designated point (rally point, etc.)</li></xs:documentation>
<xs:documentation> <li> i - initial points</li></xs:documentation>
<xs:documentation> <li> r - rally points</li></xs:documentation>
<xs:documentation> <li> ...</li></xs:documentation>
<xs:documentation></ol></xs:documentation>
<xs:documentation><b> r - Reservation/Restriction/References </b></xs:documentation>
<xs:documentation> Events in this category are generally "notices" about specific areas. These events are used for deconfliction and conveyance of significant "area" conditions. Generally, the "point" entity will describe a conical region that completely encloses the affected area. The details entity will provide more specific bounds on precisely the region affected.</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> u - Unsafe (hostile capability)</li></xs:documentation>
<xs:documentation> <li> o - Occupied (e.g., SOF forces on ground)</li></xs:documentation>
<xs:documentation> <li> c - Contaminated (NBC event)</li></xs:documentation>
<xs:documentation> <li> c - chemical</li></xs:documentation>
<xs:documentation> <li> x - agents, direction,</li></xs:documentation>
<xs:documentation> <li> y</li></xs:documentation>
<xs:documentation> <li> z</li></xs:documentation>
<xs:documentation> <li> f - Flight restrictions</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><b> t - Tasking (requests/orders)</b></xs:documentation>
<xs:documentation>Events in this category are generalized requests for service. These may be used to request for data collection, request mesuration of a specific object, order an asset to take action against a specific point. Generally, the "details" entity will identify the general or specific entity being tasked.</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> s - Surveillance</li></xs:documentation>
<xs:documentation> <li> r - Relocate</li></xs:documentation>
<xs:documentation> <li> e - Engage</li></xs:documentation>
<xs:documentation> <li> m - Mensurate</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation><b> c - Capability (applied to an area)</b></xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li> s - Surveillance</li></xs:documentation>
<xs:documentation> <li> r - Rescue</li></xs:documentation>
<xs:documentation> <li> f - Fires</li></xs:documentation>
<xs:documentation> <li> d - Direct fires</li></xs:documentation>
<xs:documentation> <li> i - Indirect fires</li></xs:documentation>
<xs:documentation> <li> l - Logistics (supply)</li></xs:documentation>
<xs:documentation> <li> f - Fuel</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation> ...</xs:documentation>
<xs:documentation><b>c - Communications</b></xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="uid" minOccurs="1" maxOccurs="1" type="xs:integer" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.uid">
<xs:annotation>
<xs:documentation>The "uid" attribute is a globally unique name for this specific piece of information.</xs:documentation>
<xs:documentation>Several "events" may be associated with one UID, but in that case, the latest (ordered by timestamp), </xs:documentation>
<xs:documentation>overwrites all previous events for that UID.</xs:documentation>
<xs:documentation>can have additional information attached.</xs:documentation>
<xs:documentation>[EventTYPE].[MACHINESENDERID].Nichname.UniqueID</xs:documentation>
<xs:documentation>e.g. -<i>ping </i>means that this event is a ping, </xs:documentation>
<xs:documentation><i>GeoChat </i>indicates a chat type structure.</xs:documentation>
<xs:documentation>The <b>UID</b> should be in the following format: GeoChat.&lt;sender uid&gt;.&lt;recipient callsign or name of the group&gt;.&lt;random string for uniqueness&gt;. Diverging from this format should not cause significant issues; however, the UID is used as a fallback if other information cannot be parsed from the message, so issues may still be experienced. If uid does not contain any “.” characters, the chat room will default to “All Chat Rooms”.</xs:documentation>
<xs:documentation>GeoChat.ANDROID-7C:91:22:E8:6E:4D.DIPPER.44bf77cd-289e-4ea4-8756-ce295de168ca</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="version" minOccurs="1" maxOccurs="1" type="" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.version">
<xs:annotation>
<xs:documentation>Schema version of this event instance (e.g. 2.0)</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="detail" minOccurs="1" maxOccurs="1" type="m:detail" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.detail"/>
<xs:element name="point" minOccurs="1" maxOccurs="1" type="m:point" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Event.point"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="Health" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Health">
<xs:sequence>
<xs:element name="stress" minOccurs="1" maxOccurs="1" type="xs:integer" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Health.stress"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="Precisionlocation" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#Precisionlocation">
<xs:annotation>
<xs:documentation>some type of location?</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:simpleType name="TeamColor" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#TeamColor">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:complexType name="color" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#color">
<xs:sequence>
<xs:element name="argb" minOccurs="1" maxOccurs="1" type="xs:integer" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#color.argb">
<xs:annotation>
<xs:documentation>integer with a color</xs:documentation>
<xs:documentation>e.g. 65536</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="contact" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#contact">
<xs:annotation>
<xs:documentation>This is a Cursor On Target Class representing communications parameters for contacting a friendly element for human-to-human communications. The objective of this Class is to carry the essential information needed to contact this entity by a variety of means. Multiple ways of establishing contact can be specified;</xs:documentation>
<xs:documentation>noThe attributes callsign, phone, and email should be self-explanatory. particular mode of contact is required. Other attributes, freq, dsn, modulation, and hostname, are also available.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="callsign" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#contact.callsign">
<xs:annotation>
<xs:documentation>The unit's voice call sign</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="detail" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail">
<xs:annotation>
<xs:documentation>An optional element used to hold CoT sub-schema. Detail has no special properties.</xs:documentation>
<xs:documentation> <b> Detail entities...</b></xs:documentation>
<xs:documentation> The "detail" entity is intended to carry information that is specific to smaller communities of producers and consumers and require more intimate knowledge of the operating domain. For example, mensurated "target" events may come from dramatically different sources and need to propagate dramatically different "detail" information. A close-air-support mission will augment target details with initial point and callsign details to facilitate coordination of weapon delivery. In contrast, a</xs:documentation>
<xs:documentation> mission planning system may augment planned targets with target catalog information and weapon fuzing requirements. </xs:documentation>
<xs:documentation> Because the "details" portion of the event are of interest only to a subset of subscribers, that entity may be mentioned by reference when the event is communicated. This reduces the congestion when events are transmitted over bandwidth limited links and also prevents the retransmission of static data elements.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="color" minOccurs="0" maxOccurs="1" type="m:color" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.color"/>
<xs:element name="contact" minOccurs="0" maxOccurs="1" type="m:contact" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.contact"/>
<xs:element name="group" minOccurs="1" maxOccurs="1" type="m:group" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.group"/>
<xs:element name="Health" minOccurs="1" maxOccurs="1" type="m:Health" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.Health"/>
<xs:element name="Precisionlocation" minOccurs="0" maxOccurs="1" type="m:Precisionlocation" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.Precisionlocation"/>
<xs:element name="remarks" minOccurs="0" maxOccurs="1" type="m:remarks" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.remarks"/>
<xs:element name="status" minOccurs="0" maxOccurs="1" type="m:status" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.status"/>
<xs:element name="takv" minOccurs="0" maxOccurs="1" type="m:takv" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.takv"/>
<xs:element name="track" minOccurs="0" maxOccurs="unbounded" type="m:track" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.track"/>
<xs:element name="uid" minOccurs="0" maxOccurs="1" type="m:uid" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.uid"/>
<xs:element name="usericon" minOccurs="0" maxOccurs="1" type="m:usericon" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#detail.usericon"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="group" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#group">
<xs:sequence>
<xs:element name="name" minOccurs="1" maxOccurs="1" type="m:TeamColor" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#group.name"/>
<xs:element name="role" minOccurs="1" maxOccurs="1" type="" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#group.role"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="point" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point">
<xs:sequence>
<xs:element name="ce" minOccurs="1" maxOccurs="1" type="xs:double" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point.ce">
<xs:annotation>
<xs:documentation>Circular area around the point defined by lat and lon fields in meters. Although named ce, this field is intended to define a circular area around the event point, not necessarily an error (e.g. Describing a reservation area is not an "error"). </xs:documentation>
<xs:documentation>If it is appropriate for the "ce" field to represent an error value (e.g. event describes laser designated target), the value will represent the one sigma point for a zero mean normal (Guassian) distribution.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="hae" minOccurs="1" maxOccurs="1" type="xs:double" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point.hae">
<xs:annotation>
<xs:documentation>Height above Ellipsoid based on WGS-84 ellipsoid (measured in meters) </xs:documentation>
<xs:documentation>HAE acronym for Height above Ellipsoid based on WGS-84 ellipsoid (measured in meters).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="lat" minOccurs="1" maxOccurs="1" type="xs:double" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point.lat">
<xs:annotation>
<xs:documentation>Latitude referred to the WGS 84 ellipsoid in degrees</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="le" minOccurs="1" maxOccurs="1" type="xs:double" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point.le">
<xs:annotation>
<xs:documentation>Linear Error in meters associated with the HAE field. Although named le, this field is intended to define a height range about the event point, not necessarily an error. This field, along with the ce field allow for the definition of a cylindrical volume about the point. If it is appropriate for the "le" field to represent an error (e.g. event describes laser designated target), the value will represent the one sigma point for a zero mean normal (Guassian) distribution.</xs:documentation>
<xs:documentation>A height range about the event point in meters associated with the HAE field. When used to represent error, the value represents the one sigma point for a zero mean normal (Gaussian) distribution.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="lon" minOccurs="1" maxOccurs="1" type="xs:double" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#point.lon">
<xs:annotation>
<xs:documentation>Longitude referred to the WGS 84 in degrees</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="remarks" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#remarks">
<xs:annotation>
<xs:documentation>This is a Cursor On TargetClass for a generic remarks (aka "FreeText").</xs:documentation>
<xs:documentation>Provides a place to annotate CoT with free text information. e.g. comments from other users about the current COT. Used also for the geoChat.</xs:documentation>
<xs:documentation><b>the xml body of this class is used to transport the chat message</b></xs:documentation>
<xs:documentation> While the use of free text is strongly discouraged (it hampers machine-to-machine communication) it is a pragmatic necessity. This entity attempts to encapsulate freetext in a way that simplifies subsequent machine processing. The content of this entity is presumed to be a human-readable chunk of textual data. The attributes merely aid in the machine handling of the data.</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="status" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#status">
<xs:annotation>
<xs:documentation>The status element provides a container for elements reporting different kinds of</xs:documentation>
<xs:documentation>status. e.g. a fuel subschema is used to report the amount of burnable fuel</xs:documentation>
<xs:documentation>remaining in liters and the current burn rate (in liters per second).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="battery" minOccurs="1" maxOccurs="1" type="xs:integer" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#status.battery">
<xs:annotation>
<xs:documentation>% of the battery on the phone</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="takv" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#takv">
<xs:annotation>
<xs:documentation>Provides the type and version of the TAK client</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="device" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#takv.device">
<xs:annotation>
<xs:documentation>type of physical device</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="platform" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#takv.platform">
<xs:annotation>
<xs:documentation>the variant of TAK</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="version" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#takv.version">
<xs:annotation>
<xs:documentation>the version of TAK running on the device</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="track" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#track">
<xs:annotation>
<xs:documentation>The track element specifies <b>direction</b> and <b>speed </b>of travel. It has two required attributes: course and speed. It also has optional attributes for specifying the vertical component of the motion vector (slope) and errors associated with course, speed, and slope.</xs:documentation>
<xs:documentation><b>Course&nbsp;</b>denotes the direction of motion and is specified as the number of degrees measured clockwise from true North.</xs:documentation>
<xs:documentation><b>Speed&nbsp;</b>is specified in meters per second as speed over ground.</xs:documentation>
<xs:documentation>There is no constraint on the precision used for these values.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="course" minOccurs="1" maxOccurs="1" type="" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#track.course"/>
<xs:element name="speed" minOccurs="1" maxOccurs="1" type="" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#track.speed"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="uid" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#uid">
<xs:annotation>
<xs:documentation>This is a Cursor On Target detail Class that holds the unique ID assigned by each system that processed this event. </xs:documentation>
<xs:documentation>Most systems (including CoT) have their own method for assigning system-wide unique identifiers for a particular object. In general, it is not possible for a single UID to be used for all systems. This 'uid' entity provides a common place where each systems can record its particular UID for each CoT event. Like the _flow-tags_ element, each system is responsible for adding its own attribute to this entity. The name of the attribute should represent the system, and the value of the attribute should be the id that system assigned to this CoT object.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Droid" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#uid.Droid">
<xs:annotation>
<xs:documentation>TBD, maybe from Android?</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="usericon" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#usericon">
<xs:annotation>
<xs:documentation>the image used to display the COt</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="iconsetpath" minOccurs="1" maxOccurs="1" type="xs:string" sawsdl:modelReference="http://iec.ch/TC57/CIM-generic#usericon.iconsetpath">
<xs:annotation>
<xs:documentation>the path of the icon image used </xs:documentation>
<xs:documentation>MIL 2525 STD</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>COT_MAPPING_2525B/a-u/a-u-G</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation>ICON</xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>34ae1613-9645-4222-a9d2-e5f243dea2865/Military/EA-6B.png</li></xs:documentation>
<xs:documentation> <li>'f7f71666-8b28-4b57-9fbb-e38e61d33b79/Google/hiker.png'/</li></xs:documentation>
<xs:documentation></ul></xs:documentation>
<xs:documentation>in alternative for a spot </xs:documentation>
<xs:documentation><ul></xs:documentation>
<xs:documentation> <li>COT_MAPPING_SPOTMAP/b-m-p-s-m/-65536 </li></xs:documentation>
<xs:documentation></ul></xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>