-
Notifications
You must be signed in to change notification settings - Fork 0
/
sap.ui.core.xsd
1818 lines (1800 loc) · 73.3 KB
/
sap.ui.core.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
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="sap.ui.core" xmlns:n0="sap.ui.core">
<xsd:element name="ComponentContainer" type="n0:_ComponentContainerType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Component Container</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Control" type="n0:_ControlType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>Base Class for Controls.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CustomData" type="n0:_CustomDataType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>Contains a single key/value pair of custom data attached to an Element. See method data().</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Element" type="n0:_ElementType">
<xsd:annotation>
<xsd:documentation>Base Class for Elements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="HTML" type="n0:_HTMLType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Embeds standard HTML in a SAPUI5 control tree.
Security Hint: By default, the HTML content (property 'content') is not sanitized and therefore
open to XSS attacks. Applications that want to show user defined input in an HTML control, should
either sanitize the content on their own or activate automatic sanitizing through the
{@link #setSanitizeContent sanitizeContent} property.
Although this control inherits the <code>tooltip</code> aggregation/property and the
<code>hasStyleClass</code>, <code>addStyleClass</code>, <code>removeStyleClass</code> and
<code>toggleStyleClass</code> methods from its base class, it doesn't support them.
Instead, the defined HTML content can contain a tooltip (title attribute) or custom CSS classes.
For further hints about usage restrictions for this control, see also the documentation of the
<code>content</code> property.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Icon" type="n0:_IconType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Icon uses embeded font instead of pixel image. Comparing to image, Icon is easily scalable, color can be altered live and various effects can be added using css.
A set of built in Icons is available and they can be fetched by calling sap.ui.core.IconPool.getIconURI and set this value to the src property on the Icon.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="InvisibleText" type="n0:_InvisibleTextType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>An InvisibleText is used to bring hidden texts to the UI for screen reader support. The hidden text can e.g. be referenced
in the ariaLabelledBy or ariaDescribedBy associations of other controls.
The inherited properties busy, busyIndicatorDelay and visible and the aggregation tooltip is not supported by this control.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Item" type="n0:_ItemType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>A control base type.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="LayoutData" type="n0:_LayoutDataType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>A layout data base type.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ListItem" type="n0:_ListItemType" substitutionGroup="n0:Item">
<xsd:annotation>
<xsd:documentation>An item that is used in lists or list-similar controls such as DropdownBox, for example.
The element foresees the usage of additional texts displayed in a second column.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="LocalBusyIndicator" type="n0:_LocalBusyIndicatorType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>The LocalBusyIndicator is a special version of the
BusyIndicator. This one doesn't block the whole screen - it just
blocks the corresponding control and puts a local animation over the
control. To use the functionality of this control the corresponding
control needs to be enabled via the 'LocalBusyIndicatorSupport'
accordingly to the ListBox control (see the init-function of the
ListBox).</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Message" type="n0:_MessageType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>This element used to provide messages. Rendering must be done within the control that uses this kind of element.
Its default level is none.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScrollBar" type="n0:_ScrollBarType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>The ScrollBar control can be used for virtual scrolling of a certain area.
This means: to simulate a very large scrollable area when technically the area is small and the control takes care of displaying the respective part only. E.g. a Table control can take care of only rendering the currently visible rows and use this ScrollBar control to make the user think he actually scrolls through a long list.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SeparatorItem" type="n0:_SeparatorItemType" substitutionGroup="n0:Item">
<xsd:annotation>
<xsd:documentation>An item that provides a visual separation. It borrows all its methods from the classes sap.ui.core.Item, sap.ui.core.Element,
sap.ui.base.EventProvider, and sap.ui.base.Object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Title" type="n0:_TitleType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>Represents a title element that can be used for aggregation with other controls</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TooltipBase" type="n0:_TooltipBaseType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Abstract class that can be extended in order to implement any extended tooltip. For example, RichTooltip Control is based on it. It provides the opening/closing behavior and the main "text" property.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="UIComponent" type="n0:_UIComponentType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Creates and initializes a new UI component with the given <code>sId</code> and
settings.
The set of allowed entries in the <code>mSettings</code> object depends on
the concrete subclass and is described there. See {@link sap.ui.core.Component}
for a general description of this argument.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VariantLayoutData" type="n0:_VariantLayoutDataType" substitutionGroup="n0:LayoutData">
<xsd:annotation>
<xsd:documentation>Allows to add multiple LayoutData to one control in case that a easy switch of layouts (e.g. in a Form) is needed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="HTMLView" type="n0:_HTMLViewType" substitutionGroup="n0:View">
<xsd:annotation>
<xsd:documentation>A view defined/constructed by declarative HTML.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="JSONView" type="n0:_JSONViewType" substitutionGroup="n0:View">
<xsd:annotation>
<xsd:documentation>A View defined using JSON.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="JSView" type="n0:_JSViewType" substitutionGroup="n0:View">
<xsd:annotation>
<xsd:documentation>A View defined/constructed by JavaScript code.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TemplateView" type="n0:_TemplateViewType" substitutionGroup="n0:View">
<xsd:annotation>
<xsd:documentation>A view defined in a template.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="View" type="n0:_ViewType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>A base class for Views.
Introduces the relationship to a Controller, some basic visual appearance settings like width and height
and provides lifecycle events.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="XMLView" type="n0:_XMLViewType" substitutionGroup="n0:View">
<xsd:annotation>
<xsd:documentation>A View defined using (P)XML and HTML markup.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OpenSearchProvider" type="n0:_OpenSearchProviderType" substitutionGroup="n0:SearchProvider">
<xsd:annotation>
<xsd:documentation>A SearchProvider which uses the OpenSearch protocol (either JSON or XML).</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SearchProvider" type="n0:_SearchProviderType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>Abstract base class for all SearchProviders which can be e.g. attached to a SearchField. Do not create instances of this class, but use a concrete sub class instead.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DOMAttribute" type="n0:_DOMAttributeType" substitutionGroup="n0:Element">
<xsd:annotation>
<xsd:documentation>Represents a DOM attribute of a DOM element.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DOMElement" type="n0:_DOMElementType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Represents a DOM element. It allows to use databinding for the properties and nested DOM attributes.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Template" type="n0:_TemplateType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>Base Class for Template.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TemplateControl" type="n0:_TemplateControlType" substitutionGroup="n0:Control">
<xsd:annotation>
<xsd:documentation>This is the base class for all template controls. Template controls are declared based on templates.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--type definition for UIElement 'sap.ui.core.ComponentContainer'-->
<xsd:complexType name="_ComponentContainerType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Component name, the package where the component is contained. The property can only be applied initially.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="url" type="n0:_URIType">
<xsd:annotation>
<xsd:documentation>The URL of the component. The property can only be applied initially.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="handleValidation" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Enable/disable validation handling by MessageManager for this component.
The resulting Messages will be propagated to the controls.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="settings" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The settings object passed to the component when created. The property can only be applied initially.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="propagateModel" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Defines whether binding information is propagated to the component.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="width" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>Container width in CSS size</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="height" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>Container height in CSS size</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="component" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The component displayed in this ComponentContainer.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Control'-->
<xsd:complexType name="_ControlType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="busy" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether the control is currently in busy state.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="busyIndicatorDelay" type="xsd:int">
<xsd:annotation>
<xsd:documentation>The delay in milliseconds, after which the busy indicator will show up for this control.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="visible" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether the control should be visible on the screen. If set to false, a placeholder is rendered instead of the real control</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.CustomData'-->
<xsd:complexType name="_CustomDataType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="key" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The key of the data in this CustomData object.
When the data is just stored, it can be any string, but when it is to be written to HTML (writeToDom == true) then it must also be a valid HTML attribute name (it must conform to the sap.ui.core.ID type and may contain no colon) to avoid collisions, it also may not start with "sap-ui". When written to HTML, the key is prefixed with "data-".
If any restriction is violated, a warning will be logged and nothing will be written to the DOM.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="value" type="n0:_anyType">
<xsd:annotation>
<xsd:documentation>The data stored in this CustomData object.
When the data is just stored, it can be any JS type, but when it is to be written to HTML (writeToDom == true) then it must be a string.
If this restriction is violated, a warning will be logged and nothing will be written to the DOM.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="writeToDom" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>If set to "true" and the value is of type "string" and the key conforms to the documented restrictions, this custom data is written to the HTML root element of the control as a "data-*" attribute.
If the key is "abc" and the value is "cde", the HTML will look as follows:
&lt;SomeTag ... data-abc="cde" ... &gt;
Thus the application can provide stable attributes by data binding which can be used for styling or identification purposes.
ATTENTION: use carefully to not create huge attributes or a large number of them.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Element'-->
<xsd:complexType name="_ElementType">
<xsd:sequence>
<xsd:element name="tooltip" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The tooltip that should be shown for this Element.
Can either be an instance of a TooltipBase subclass or a simple string.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:TooltipBase" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="customData" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Custom Data, a data structure like a map containing arbitrary key value pairs.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:CustomData" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="layoutData" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Defines the layout constraints for this control when it is used inside a Layout.
LayoutData classes are typed classes and must match the embedding Layout.
See VariantLayoutData for aggregating multiple alternative LayoutData instances to a single Element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:LayoutData" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="dependents" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Dependents are not rendered, but their databinding context and lifecycle are bound to the aggregating Element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="n0:Control" minOccurs="0"/>
<xsd:any processContents="lax" namespace="http://www.w3.org/1999/xhtml"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="n0:_IDType">
<xsd:annotation>
<xsd:documentation>The unique identifier within a page, either configured or automatically generated.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.HTML'-->
<xsd:complexType name="_HTMLType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="content" type="xsd:string">
<xsd:annotation>
<xsd:documentation>HTML content to be displayed, defined as a string.
The content is converted to DOM nodes with a call to <code>new jQuery(content)</code>, so any
restrictions for the jQuery constructor apply to the content of the HTML control as well.
Some of these restrictions (there might be others!) are:
<ul>
<li>the content must be enclosed in tags, pure text is not supported. </li>
<li>if the content contains script tags, they will be executed but they will not appear in the
resulting DOM tree. When the contained code tries to find the corresponding script tag,
it will fail.</li>
</ul>
Please consider to consult the jQuery documentation as well.
The HTML control currently doesn't prevent the usage of multiple root nodes in its DOM content
(e.g. setContent("<div/><div/>")), but this is not a guaranteed feature. The accepted content
might be restricted to single root nodes in future versions. To notify applications about this
fact, a warning is written in the log when multiple root nodes are used.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="preferDOM" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether existing DOM content is preferred over the given content string.
There are two scenarios where this flag is relevant (when set to true):
<ul>
<li>for the initial rendering: when an HTML control is added to an UIArea for the first time
and if the root node of that UIArea contained DOM content with the same id as the HTML
control, then that content will be used for rendering instead of any specified string
content</li>
<li>any follow-up rendering: when an HTML control is rendered for the second or any later
time and the preferDOM flag is set, then the DOM from the first rendering is preserved
and not replaced by the string content</li>
</ul>
As preserving the existing DOM is the most common use case of the HTML control, the default value is true.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sanitizeContent" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether to run the HTML sanitizer once the content (HTML markup) is applied or not.
To configure allowed URLs please use the whitelist API via jQuery.sap.addUrlWhitelist.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="visible" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Specifies whether the control is visible. Invisible controls are not rendered.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="afterRendering" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired after the HTML control has been rendered. Allows to manipulate the resulting DOM.
When the control doesn't have string content and no preserved DOM existed for this control,
then this event will fire, but there won't be a DOM node for this control.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Icon'-->
<xsd:complexType name="_IconType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="src" type="n0:_URIType">
<xsd:annotation>
<xsd:documentation>This property should be set by the return value of calling sap.ui.core.IconPool.getIconURI with a Icon name parameter and an optional collection parameter which is required when using application extended Icons. A list of standard FontIcon is available here.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="size" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>Since Icon uses font, this property will be applied to the css font-size property on the rendered DOM element.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="color" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The color of the Icon. If color is not defined here, the Icon inherits the color from its DOM parent.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="hoverColor" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This color is shown when icon is hovered. This property has no visual effect when run on mobile device.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="activeColor" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This color is shown when icon is pressed/activated by the user.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="width" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>This is the width of the DOM element which contains the Icon. Setting this property doesn't affect the size of the font. If you want to make the font bigger, increase the size property.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="height" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>This is the height of the DOM element which contains the Icon. Setting this property doesn't affect the size of the font. If you want to make the font bigger, increase the size property.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="backgroundColor" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Background color of the Icon in normal state.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="hoverBackgroundColor" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Background color for Icon in hover state. This property has no visual effect when run on mobile device.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="activeBackgroundColor" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Background color for Icon in active state.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="decorative" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>A decorative icon is included for design reasons. Accessibility tools will ignore decorative icons. Tab stop isn't affected by this property anymore and it's now controlled by the existence of press event handler and the noTabStop property.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="useIconTooltip" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Decides whether a default Icon tooltip should be used if no tooltip is set.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="alt" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This defines the alternative text which is used for outputting the aria-label attribute on the DOM.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="noTabStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Defines whether the tab stop of icon is controlled by the existence of press event handler. When it's set to false, Icon control has tab stop when press event handler is attached.
If it's set to true, Icon control never has tab stop no matter whether press event handler exists or not.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ariaLabelledBy" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Association to controls / ids which label this control (see WAI-ARIA attribute aria-labelledby).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="press" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This event is fired when icon is pressed/activated by the user. When a handler is attached to this event, the Icon gets tab stop. If you want to disable this behavior, set the noTabStop property to true.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.InvisibleText'-->
<xsd:complexType name="_InvisibleTextType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The text of the InvisibleText.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Item'-->
<xsd:complexType name="_ItemType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The text to be displayed for the item.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="enabled" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Enabled items can be selected.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="textDirection" type="n0:_TextDirectionType">
<xsd:annotation>
<xsd:documentation>Options are RTL and LTR. Alternatively, an item can inherit its text direction from its parent control.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="key" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Can be used as input for subsequent actions.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.LayoutData'-->
<xsd:complexType name="_LayoutDataType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.ListItem'-->
<xsd:complexType name="_ListItemType">
<xsd:complexContent>
<xsd:extension base="n0:_ItemType">
<xsd:attribute name="icon" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The icon belonging to this list item instance.
This can be an URI to an image or an icon font URI.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="additionalText" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Some additional text of type string, optionally to be displayed along with this item.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.LocalBusyIndicator'-->
<xsd:complexType name="_LocalBusyIndicatorType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="width" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>This property is the width of the control that has to
be covered. With this width the position of the animation can be
properly set.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="height" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>This property is the height of the control that has to
be covered. With this height the position of the animation can be
properly set.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Message'-->
<xsd:complexType name="_MessageType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Message text</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="timestamp" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Message's timestamp. It is just a simple String that will be used without any transformation. So the application that uses messages needs to format the timestamp to its own needs.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="icon" type="n0:_URIType">
<xsd:annotation>
<xsd:documentation>A possible icon URI of the message</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="level" type="n0:_MessageTypeType">
<xsd:annotation>
<xsd:documentation>Setting the message's level.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="readOnly" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Determines whether the message should be read only. This helps the application to handle a message a different way if the application differentiates between read-only and common messages.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.ScrollBar'-->
<xsd:complexType name="_ScrollBarType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="vertical" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Orientation. Defines if the Scrollbar is vertical or horizontal.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="scrollPosition" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Scroll position in steps or pixels.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="size" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>Size of the Scrollbar (in pixels).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="contentSize" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>Size of the scrollable content (in pixels).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="steps" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Number of steps to scroll. Used if the size of the content is not known as the data is loaded dynamically.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="scroll" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Scroll event.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.SeparatorItem'-->
<xsd:complexType name="_SeparatorItemType">
<xsd:complexContent>
<xsd:extension base="n0:_ItemType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.Title'-->
<xsd:complexType name="_TitleType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Defines the title text</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="icon" type="n0:_URIType">
<xsd:annotation>
<xsd:documentation>Defines the URL for icon display</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="level" type="n0:_TitleLevelType">
<xsd:annotation>
<xsd:documentation>Defines the level of the title. If set to auto the level of the title is chosen by the control rendering the title.
Currently not all controls using the Title.control supporting this property.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="emphasized" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>If set the title is displayed emphasized.
This feature is nor supported by all controls using the Title.control.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.TooltipBase'-->
<xsd:complexType name="_TooltipBaseType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The text that is shown in the tooltip that extends the TooltipBase class, for example in RichTooltip.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="openDuration" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Optional. Open Duration in milliseconds.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="closeDuration" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Optional. Close Duration in milliseconds.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="myPosition" type="n0:_DockType">
<xsd:annotation>
<xsd:documentation>Optional. My position defines which position on the extended tooltip being positioned to align with the target control.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="atPosition" type="n0:_DockType">
<xsd:annotation>
<xsd:documentation>Optional. At position defines which position on the target control to align the positioned tooltip.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="offset" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Optional. Offset adds these left-top values to the calculated position.
Example: "10 3".</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="collision" type="n0:_CollisionType">
<xsd:annotation>
<xsd:documentation>Optional. Collision - when the positioned element overflows the window in some direction, move it to an alternative position.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="openDelay" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Opening delay of the tooltip in milliseconds</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="closeDelay" type="xsd:int">
<xsd:annotation>
<xsd:documentation>Closing delay of the tooltip in milliseconds</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="closed" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This event is fired when the Tooltip has been closed</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.UIComponent'-->
<xsd:complexType name="_UIComponentType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:sequence/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.VariantLayoutData'-->
<xsd:complexType name="_VariantLayoutDataType">
<xsd:complexContent>
<xsd:extension base="n0:_LayoutDataType">
<xsd:sequence>
<xsd:element name="multipleLayoutData" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Allows multiple LayoutData.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:LayoutData" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.HTMLView'-->
<xsd:complexType name="_HTMLViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ViewType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.JSONView'-->
<xsd:complexType name="_JSONViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ViewType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.JSView'-->
<xsd:complexType name="_JSViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ViewType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.TemplateView'-->
<xsd:complexType name="_TemplateViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ViewType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.View'-->
<xsd:complexType name="_ViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="n0:Control"/>
<xsd:any processContents="lax" namespace="http://www.w3.org/1999/xhtml"/>
</xsd:choice>
<xsd:element name="content" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Child Controls of the view</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="n0:Control" minOccurs="0"/>
<xsd:any processContents="lax" namespace="http://www.w3.org/1999/xhtml"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="width" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>The width</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="height" type="n0:_CSSSizeType">
<xsd:annotation>
<xsd:documentation>The height</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="viewName" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Name of the View</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="displayBlock" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether the CSS display should be set to "block".
Set this to "true" if the default display "inline-block" causes a vertical scrollbar with Views that are set to 100% height.
Do not set this to "true" if you want to display other content in the same HTML parent on either side of the View (setting to "true" may push that other content to the next/previous line).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="afterInit" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired when the View has parsed the UI description and instantiated the contained controls (/control tree).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="beforeExit" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired when the view has received the request to destroy itself, but before it has destroyed anything.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="afterRendering" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired when the View has been (re-)rendered and its HTML is present in the DOM.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="beforeRendering" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired before this View is re-rendered. Use to unbind event handlers from HTML elements etc.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.mvc.XMLView'-->
<xsd:complexType name="_XMLViewType">
<xsd:complexContent>
<xsd:extension base="n0:_ViewType"/>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.search.OpenSearchProvider'-->
<xsd:complexType name="_OpenSearchProviderType">
<xsd:complexContent>
<xsd:extension base="n0:_SearchProviderType">
<xsd:attribute name="suggestUrl" type="n0:_URIType">
<xsd:annotation>
<xsd:documentation>The URL for suggestions of the search provider. As placeholder for the concrete search queries '{searchTerms}' must be used. For cross domain requests maybe a proxy must be used.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="suggestType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The type of data which is provided by the given suggestUrl: either 'json' or 'xml'.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.search.SearchProvider'-->
<xsd:complexType name="_SearchProviderType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="icon" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Icon of the Search Provider</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.tmpl.DOMAttribute'-->
<xsd:complexType name="_DOMAttributeType">
<xsd:complexContent>
<xsd:extension base="n0:_ElementType">
<xsd:attribute name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Name of the DOM attribute</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="value" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Value of the DOM attribute</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.tmpl.DOMElement'-->
<xsd:complexType name="_DOMElementType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:sequence>
<xsd:element name="attributes" minOccurs="0">
<xsd:annotation>
<xsd:documentation>DOM attributes which are rendered as part of the DOM element and bindable</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:DOMAttribute" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="elements" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Nested DOM elements to support nested bindable structures</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="n0:DOMElement" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="text" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The text content of the DOM element</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="tag" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The HTML-tag of the DOM element which contains the text</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.tmpl.Template'-->
<xsd:complexType name="_TemplateType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:attribute name="content" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The Template definition as a String.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--type definition for UIElement 'sap.ui.core.tmpl.TemplateControl'-->
<xsd:complexType name="_TemplateControlType">
<xsd:complexContent>
<xsd:extension base="n0:_ControlType">
<xsd:sequence/>
<xsd:attribute name="context" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The context is a data object. It can be used for default template expressions. A change of the context object leads to a re-rendering whereas a change of a nested property of the context object doesn't. By default the context is an empty object.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="template" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The template on which the template control is based on.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="afterRendering" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired when the Template Control has been (re-)rendered and its HTML is present in the DOM.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="beforeRendering" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Fired before this Template Control is re-rendered. Use to unbind event handlers from HTML elements etc.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="_AccessibleRoleType">