-
Notifications
You must be signed in to change notification settings - Fork 37
/
independent-system-characteristics-schema.xsd
928 lines (928 loc) · 69.9 KB
/
independent-system-characteristics-schema.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
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
<?xml version="1.0" encoding="utf-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:ind-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#independent" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#independent" elementFormDefault="qualified" version="5.10.1">
<xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" schemaLocation="oval-system-characteristics-schema.xsd"/>
<xsd:annotation>
<xsd:documentation>This document outlines the items of the OVAL System Characteristics XML schema that are independent of any specific family or platform. Each iten is an extention of a basic System Characteristics item defined in the core System Characteristics XML schema.</xsd:documentation>
<xsd:documentation>The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.</xsd:documentation>
<xsd:appinfo>
<schema>Independent System Characteristics</schema>
<version>5.10.1</version>
<date>1/27/2012 1:22:32 PM</date>
<terms_of_use>Copyright (c) 2002-2012, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.</terms_of_use>
<sch:ns prefix="oval-sc" uri="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5"/>
<sch:ns prefix="ind-sc" uri="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#independent"/>
<sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/>
</xsd:appinfo>
</xsd:annotation>
<!-- =============================================================================== -->
<!-- ================================ FAMILY ITEM ================================ -->
<!-- =============================================================================== -->
<xsd:element name="family_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This element stores high level system OS type, otherwise known as the family.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="family" type="ind-sc:EntityItemFamilyType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>This element describes the high level system OS type, otherwise known as the family.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ============================== FILE HASH ITEM =============================== -->
<!-- =============================================================================== -->
<xsd:element name="filehash_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This element stores the different hash values associated with a specific file.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.8</oval:version>
<oval:reason>Replaced by the filehash58_item which allows the hash algorithm to be specified when collecting data. See the filehash58_item.</oval:reason>
<oval:comment>This item has been deprecated and may be removed in a future version of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_filehash_item_dep">
<sch:rule context="ind-sc:filehash_item">
<sch:report test="true()">DEPRECATED ITEM: <sch:value-of select="name()"/> ID: <sch:value-of select="@id"/></sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="md5" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The md5 hash of the file</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="sha1" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The sha1 hash of the file</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="windows_view" type="ind-sc:EntityItemWindowsViewType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The windows view value from which this OVAL Item was collected. This is used to indicate from which view (32-bit or 64-bit), the associated Item was collected. A value of '32_bit' indicates the Item was collected from the 32-bit view. A value of '64-bit' indicates the Item was collected from the 64-bit view. Omitting this entity removes any assertion about which view the Item was collected from, and therefore it is strongly suggested that this entity be set. This entity only applies to 64-bit Microsoft Windows operating systems.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ============================ FILE HASH ITEM (58) ============================= -->
<!-- =============================================================================== -->
<xsd:element name="filehash58_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This element stores a hash value associated with a specific file.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="hash_type" type="ind-sc:EntityItemHashTypeType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Identifier for the hash algorithm used to calculate the hash.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="hash" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The result of applying the hash algorithm to the file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="windows_view" type="ind-sc:EntityItemWindowsViewType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The windows view value from which this OVAL Item was collected. This is used to indicate from which view (32-bit or 64-bit), the associated Item was collected. A value of '32_bit' indicates the Item was collected from the 32-bit view. A value of '64-bit' indicates the Item was collected from the 64-bit view. Omitting this entity removes any assertion about which view the Item was collected from, and therefore it is strongly suggested that this entity be set. This entity only applies to 64-bit Microsoft Windows operating systems.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ======================= ENVIRONMENT VARIABLE ITEM =========================== -->
<!-- =============================================================================== -->
<xsd:element name="environmentvariable_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This item stores information about environment variables and their values.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.8</oval:version>
<oval:reason>Replaced by the environmentvariable58_item. This item allows the hash algorithm to be specified. See the filehash58_item.</oval:reason>
<oval:comment>This object has been deprecated and may be removed in a future version of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_environmentvariable_item_dep">
<sch:rule context="ind-sc:environmentvariable_item">
<sch:report test="true()">DEPRECATED ITEM: <sch:value-of select="name()"/> ID: <sch:value-of select="@id"/></sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>This element describes the name of an environment variable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The actual value of the specified environment variable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ======================= ENVIRONMENT VARIABLE ITEM (58) ======================= -->
<!-- =============================================================================== -->
<xsd:element name="environmentvariable58_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This item stores information about an environment variable, the process ID of the process from which it was retrieved, and its corresponding value.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="pid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The process ID of the process from which the environment variable was retrieved.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>This element describes the name of an environment variable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The actual value of the specified environment variable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================= LDAP ITEM ================================= -->
<!-- =============================================================================== -->
<xsd:element name="ldap_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This element holds information about specific entries in the LDAP directory. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation>
<xsd:documentation>Note that this ite supports only simple (string based) value collection. For more complex values see the ldap57_item.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="suffix" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Each object in an LDAP directory exists under a certain suffix (also known as a naming context). A suffix is defined as a single object in the Directory Information Tree (DIT) with every object in the tree subordinate to it.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="relative_dn" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true">
<xsd:annotation>
<xsd:documentation>The relative_dn field is used to uniquely identify an item inside the specified suffix. It contains all of the parts of the item's distinguished name except those outlined by the suffix. If the xsi:nil attribute is set to true, then the item being represented is the higher level suffix. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true">
<xsd:annotation>
<xsd:documentation>Specifies a named value contained by the object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="object_class" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the class of which the object is an instance.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ldaptype" type="ind-sc:EntityItemLdaptypeType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Specifies the type of information that the specified attribute represents.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The actual value of the specified LDAP attribute.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================= LDAP ITEM (57) ============================ -->
<!-- =============================================================================== -->
<xsd:element name="ldap57_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This element holds information about specific entries in the LDAP directory. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="suffix" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Each object in an LDAP directory exists under a certain suffix (also known as a naming context). A suffix is defined as a single object in the Directory Information Tree (DIT) with every object in the tree subordinate to it.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="relative_dn" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true">
<xsd:annotation>
<xsd:documentation>The relative_dn field is used to uniquely identify an item inside the specified suffix. It contains all of the parts of the item's distinguished name except those outlined by the suffix. If the xsi:nil attribute is set to true, then the item being represented is the higher level suffix.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true">
<xsd:annotation>
<xsd:documentation>Specifies a named value contained by the object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="object_class" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the class of which the object is an instance.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ldaptype" type="ind-sc:EntityItemLdaptypeType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Specifies the type of information that the specified attribute represents.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-sc:EntityItemRecordType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The actual value of the specified LDAP attribute. Note that while an LDAP attribute can contain structured data where it is necessary to collect multiple related fields that can be described by the 'record' datatype, it is not always the case. It also is possible that an LDAP attribute can contain only a single value or an array of values. In these cases, there is not a name to uniquely identify the corresponding field(s) which is a requirement for fields in the 'record' datatype. As a result, the name of the LDAP attribute will be used to uniquely identify the field(s) and satisfy this requirement. If the LDAP attribute contains a single value, the 'record' will have a single field identified by the name of the LDAP attribute. If the LDAP attribute contains an array of values, the 'record' will have multiple fields all identified by the name of the LDAP attribute.</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="ind-sc_ldap57_itemvalue">
<sch:rule context="ind-sc:ldap57_item/ind-sc:value">
<sch:assert test="@datatype='record'"><sch:value-of select="../@id"/> - datatype attribute for the value entity of a ldap57_item must be 'record'</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ============================= SQL CONTENT ITEM ============================= -->
<!-- =============================================================================== -->
<xsd:element name="sql_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>The sql_item outlines information collected from a database via an SQL query.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.7</oval:version>
<oval:reason>Replaced by the sql57_item. This item allows for single fields to be selected from a database. A new item was created to allow more than one field to be selected in one statement. See the sql57_item.</oval:reason>
<oval:comment>This object has been deprecated and may be removed in a future version of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_sql_item_dep">
<sch:rule context="ind-sc:sql_item">
<sch:report test="true()">DEPRECATED ITEM: <sch:value-of select="name()"/> ID: <sch:value-of select="@id"/></sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="engine" type="ind-sc:EntityItemEngineType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The engine entity identifies the specific database engine used to connect to the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="version" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The version entity identifies the version of the database engine used to connect to the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="connection_string" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The connection_string entity defines connection parameters used to connect to the specific database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="sql" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The sql entity holds the specific query used to identify the object(s) in the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="result" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The result entity specifies the result(s) of the given SQL query against the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ============================= SQL CONTENT ITEM (57) ======================== -->
<!-- =============================================================================== -->
<xsd:element name="sql57_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>The sql57_item outlines information collected from a database via an SQL query.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="engine" type="ind-sc:EntityItemEngineType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The engine entity identifies the specific database engine used to connect to the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="version" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The version entity identifies the version of the database engine used to connect to the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="connection_string" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The connection_string entity defines connection parameters used to connect to the specific database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="sql" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The sql entity holds the specific query used to identify the object(s) in the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="result" type="oval-sc:EntityItemRecordType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The result entity holds the results of the specified SQL statement.</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="ind-sc_sql57_itemresult">
<sch:rule context="ind-sc:sql57_item/ind-sc:result">
<sch:assert test="@datatype='record'"><sch:value-of select="../@id"/> - datatype attribute for the result entity of a sql57_item must be 'record'</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ========================== TEXT FILE CONTENT ITEM =========================== -->
<!-- =============================================================================== -->
<xsd:element name="textfilecontent_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>The textfilecontent_item looks at the contents of a text file (aka a configuration file) by looking at individual lines.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filename entity specifies the name of the file (without the path) that is being represented.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="pattern" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The pattern entity represents a regular expression that is used to define a block of text. Subexpression notation (parenthesis) is used to call out a value(s) to test against. For example, the pattern abc(.*)xyz would look for a block of text in the file that starts with abc and ends with xyz, with the subexpression being all the characters that exist inbetween. Note that if the pattern can match more than one block of text starting at the same point, then it matches the longest. Subexpressions also match the longest possible substrings, subject to the constraint that the whole match be as long as possible, with subexpressions starting earlier in the pattern taking priority over ones starting later.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="instance" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The instance entity calls out which match of the pattern is being represented by this item. The first match is given an instance value of 1, the second match is given an instance value of 2, and so on. The main purpose of this entity is too provide uniqueness for different textfilecontent_items that results from multiple matches of a given pattern against the same file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="line" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The line element represents a line in the file and is represented using a regular expression.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.4</oval:version>
<oval:reason>Due to the fact that the TextFileContent54_test supports multi-line pattern matching, the line entity is no longer needed.</oval:reason>
<oval:comment>This entity has been deprecated and will be removed in version 6.0 of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_txtitemline">
<sch:rule context="ind-sc:textfilecontent_item/ind-sc:line">
<sch:report test="true()">DEPRECATED ELEMENT: <sch:value-of select="name()"/> ID: <sch:value-of select="@id"/></sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="text" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The text entity represents the block of text that matched the specified pattern.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="subexpression" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The subexpression entity represents the value of a subexpression in the specified pattern. If multiple subexpressions are specified in the pattern, then multiple entities are presented. Note that the textfilecontent_state in the definition schema only allows a single subexpression entity. This means that the test will check that all (or at least one, none, etc.) the subexpressions pass the same check. This means that the order of multiple subexpression entities in the item does not matter.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="windows_view" type="ind-sc:EntityItemWindowsViewType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The windows view value from which this OVAL Item was collected. This is used to indicate from which view (32-bit or 64-bit), the associated Item was collected. A value of '32_bit' indicates the Item was collected from the 32-bit view. A value of '64-bit' indicates the Item was collected from the 64-bit view. Omitting this entity removes any assertion about which view the Item was collected from, and therefore it is strongly suggested that this entity be set. This entity only applies to 64-bit Microsoft Windows operating systems.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- =============================== VARIABLE ITEM =============================== -->
<!-- =============================================================================== -->
<xsd:element name="variable_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This item stores information about OVAL Variables and their values.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="var_ref" type="ind-sc:EntityItemVariableRefType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The id of the variable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The value of the variable. If a variable represents and array of values, then multiple value elements should exist.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- =========================== XML FILE CONTENT ITEM =========================== -->
<!-- =============================================================================== -->
<xsd:element name="xmlfilecontent_item" substitutionGroup="oval-sc:item">
<xsd:annotation>
<xsd:documentation>This item stores results from checking the contents of an xml file.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-sc:ItemType">
<xsd:sequence>
<xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The filename element specifies the name of the file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="xpath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Specifies an Xpath expression describing the text node(s) or attribute(s) to look at.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value_of" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The value_of element checks the value(s) of the text node(s) or attribute(s) found. How this is used is entirely controlled by operator attributes.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="windows_view" type="ind-sc:EntityItemWindowsViewType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The windows view value from which this OVAL Item was collected. This is used to indicate from which view (32-bit or 64-bit), the associated Item was collected. A value of '32_bit' indicates the Item was collected from the 32-bit view. A value of '64-bit' indicates the Item was collected from the 64-bit view. Omitting this entity removes any assertion about which view the Item was collected from, and therefore it is strongly suggested that this entity be set. This entity only applies to 64-bit Microsoft Windows operating systems.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- =============================================================================== -->
<!-- =============================================================================== -->
<xsd:complexType name="EntityItemEngineType">
<xsd:annotation>
<xsd:documentation>The EntityItemEngineType complex type defines a string entity value that is restricted to an enumeration. Each valid entry in the enumeration is a valid database engine.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:enumeration value="access">
<xsd:annotation>
<xsd:documentation>The access value describes the Microsoft Access database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="db2">
<xsd:annotation>
<xsd:documentation>The db2 value describes the IBM DB2 database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="cache">
<xsd:annotation>
<xsd:documentation>The cache value describes the InterSystems Cache database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="firebird">
<xsd:annotation>
<xsd:documentation>The firebird value describes the Firebird database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="firstsql">
<xsd:annotation>
<xsd:documentation>The firstsql value describes the FirstSQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="foxpro">
<xsd:annotation>
<xsd:documentation>The foxpro value describes the Microsoft FoxPro database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="informix">
<xsd:annotation>
<xsd:documentation>The informix value describes the IBM Informix database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ingres">
<xsd:annotation>
<xsd:documentation>The ingres value describes the Ingres database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="interbase">
<xsd:annotation>
<xsd:documentation>The interbase value describes the Embarcadero Technologies InterBase database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="lightbase">
<xsd:annotation>
<xsd:documentation>The lightbase value describes the Light Infocon LightBase database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="maxdb">
<xsd:annotation>
<xsd:documentation>The maxdb value describes the SAP MaxDB database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="monetdb">
<xsd:annotation>
<xsd:documentation>The monetdb value describes the MonetDB SQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="mimer">
<xsd:annotation>
<xsd:documentation>The mimer value describes the Mimer SQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="mysql">
<xsd:annotation>
<xsd:documentation>The mysql value describes the MySQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="oracle">
<xsd:annotation>
<xsd:documentation>The oracle value describes the Oracle database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="paradox">
<xsd:annotation>
<xsd:documentation>The paradox value describes the Paradox database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="pervasive">
<xsd:annotation>
<xsd:documentation>The pervasive value describes the Pervasive PSQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="postgre">
<xsd:annotation>
<xsd:documentation>The postgre value describes the PostgreSQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="sqlbase">
<xsd:annotation>
<xsd:documentation>The sqlbase value describes the Unify SQLBase database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="sqlite">
<xsd:annotation>
<xsd:documentation>The sqlite value describes the SQLite database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="sqlserver">
<xsd:annotation>
<xsd:documentation>The sqlserver value describes the Microsoft SQL database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="sybase">
<xsd:annotation>
<xsd:documentation>The sybase value describes the Sybase database engine.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityItemFamilyType">
<xsd:annotation>
<xsd:documentation>The EntityItemFamilyType complex type defines a string entity value that is restricted to a set of enumerations. Each valid enumeration is a high-level family of system operating system.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:enumeration value="catos">
<xsd:annotation>
<xsd:documentation>The catos value describes the Cisco CatOS operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ios">
<xsd:annotation>
<xsd:documentation>The ios value describes the Cisco IOS operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="macos">
<xsd:annotation>
<xsd:documentation>The macos value describes the Mac operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="pixos">
<xsd:annotation>
<xsd:documentation>The pixos value describes the Cisco PIX operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="undefined">
<xsd:annotation>
<xsd:documentation>The undefined value is to be used when the desired family is not available.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="unix">
<xsd:annotation>
<xsd:documentation>The unix value describes the UNIX operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="vmware_infrastructure">
<xsd:annotation>
<xsd:documentation>The vmware_infrastructure value describes VMWare Infrastructure.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="windows">
<xsd:annotation>
<xsd:documentation>The windows value describes the Microsoft Windows operating system.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityItemHashTypeType">
<xsd:annotation>
<xsd:documentation>The EntityItemHashTypeType complex type restricts a string value to a specific set of values that specify the different hash algorithms that are supported. The empty string is also allowed to support empty elements associated with variable references.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:enumeration value="MD5">
<xsd:annotation>
<xsd:documentation>The MD5 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SHA-1">
<xsd:annotation>
<xsd:documentation>The SHA-1 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SHA-224">
<xsd:annotation>
<xsd:documentation>The SHA-224 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SHA-256">
<xsd:annotation>
<xsd:documentation>The SHA-256 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SHA-384">
<xsd:annotation>
<xsd:documentation>The SHA-384 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SHA-512">
<xsd:annotation>
<xsd:documentation>The SHA-512 hash algorithm.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityItemVariableRefType">
<xsd:annotation>
<xsd:documentation>The EntityItemVariableRefType complex type defines a string item entity that has a valid OVAL variable id as the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:pattern value="oval:[A-Za-z0-9_\-\.]+:var:[1-9][0-9]*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityItemLdaptypeType">
<xsd:annotation>
<xsd:documentation>The EntityItemLdaptypeType complex type restricts a string value to a specific set of values that specify the different types of information that an ldap attribute can represent. The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:enumeration value="LDAPTYPE_ATTRIBUTE_TYPE_DESCRIP_STRING">
<xsd:annotation>
<xsd:documentation>The data type is the attribute type description.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_DN_STRING">
<xsd:annotation>
<xsd:documentation>The string is of Distinguished Name (path) of a directory service object.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_BIT_STRING">
<xsd:annotation>
<xsd:documentation>The bit string type.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_PRINTABLE_STRING">
<xsd:annotation>
<xsd:documentation>The string is displayable on screen or in print.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_NUMERIC_STRING">
<xsd:annotation>
<xsd:documentation>The string is of a numeral to be interpreted as text.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_BOOLEAN">
<xsd:annotation>
<xsd:documentation>The data is of a Boolean value.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_INTEGER">
<xsd:annotation>
<xsd:documentation>The data is of an integer value.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_UTC_TIME">
<xsd:annotation>
<xsd:documentation>The data is of the universal time as expressed in Universal Time Coordinate (UTC).</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_GENERALIZED_TIME">
<xsd:annotation>
<xsd:documentation>The data is of generalized time.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_DIRECTORY_STRING">
<xsd:annotation>
<xsd:documentation>The directory string.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_OBJECT_CLASS_DESCRIP_STRING">
<xsd:annotation>
<xsd:documentation>The object class description type.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_BINARY">
<xsd:annotation>
<xsd:documentation>The data is binary.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_TIMESTAMP">
<xsd:annotation>
<xsd:documentation>The data is of a time stamp in seconds.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.7</oval:version>
<oval:reason>This value was accidently carried over from the win-sc:EntityItemAdstypeType as it was used as a template for the ind-sc:EntityItemLdaptypeType.</oval:reason>
<oval:comment>This value has been deprecated and will be removed in version 6.0 of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_ldaptype_timestamp_value_dep">
<sch:rule context="oval-sc:oval_system_characteristics/oval-sc:system_data/ind-sc:ldap_item/ind-sc:ldaptype|oval-sc:oval_system_characteristics/oval-sc:system_data/ind-sc:ldap57_item/ind-sc:ldaptype">
<sch:report test=".='LDAPTYPE_TIMESTAMP'">
DEPRECATED ELEMENT VALUE IN: ldap_item ELEMENT VALUE: <sch:value-of select="."/>
</sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LDAPTYPE_EMAIL">
<xsd:annotation>
<xsd:documentation>The data is of an e-mail message.</xsd:documentation>
<xsd:appinfo>
<oval:deprecated_info>
<oval:version>5.7</oval:version>
<oval:reason>This value was accidently carried over from the win-sc:EntityItemAdstypeType as it was used as a template for the ind-sc:EntityItemLdaptypeType.</oval:reason>
<oval:comment>This value has been deprecated and will be removed in version 6.0 of the language.</oval:comment>
</oval:deprecated_info>
<sch:pattern id="ind-sc_ldaptype_email_value_dep">
<sch:rule context="oval-sc:oval_system_characteristics/oval-sc:system_data/ind-sc:ldap_item/ind-sc:ldaptype|oval-sc:oval_system_characteristics/oval-sc:system_data/ind-sc:ldap57_item/ind-sc:ldaptype">
<sch:report test=".='LDAPTYPE_EMAIL'">
DEPRECATED ELEMENT VALUE IN: ldap_item ELEMENT VALUE: <sch:value-of select="."/>
</sch:report>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityItemWindowsViewType">
<xsd:annotation>
<xsd:documentation>The EntityItemWindowsViewType restricts a string value to a specific set of values: 32-bit and 64-bit. These values describe the different values possible for the windows view behavior.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-sc:EntityItemStringType">
<xsd:enumeration value="32_bit">
<xsd:annotation>
<xsd:documentation>Indicates the 32_bit windows view.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="64_bit">
<xsd:annotation>
<xsd:documentation>Indicates the 64_bit windows view.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for empty elements associated with variable references.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>