epb_view_models 2.2.2 → 2.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/api/schemas/data/orchestrate.json +3 -0
- data/api/schemas/xml/DECAR-S-7.0/CommonFiles/CommonStructures.xsd +24 -0
- data/api/schemas/xml/DECAR-S-7.0/CommonFiles/Exceptions.xsd +69 -0
- data/api/schemas/xml/DECAR-S-7.0/Messages/LodgeReportRequest.xsd +14 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/BaseDataTypes.xsd +181 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/CEPC-Reports.xsd +66 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/Input-Data.xsd +307 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/Performance-Summary.xsd +105 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/Report-Header.xsd +449 -0
- data/api/schemas/xml/DECAR-S-7.0/Reports/Reported-Data.xsd +403 -0
- data/lib/epb_view_models.rb +1 -1
- data/lib/presenter/dec_rr/summary.rb +1 -3
- data/lib/view_model/cepc31/dec_rr.rb +4 -0
- data/lib/view_model/cepc40/dec_rr.rb +4 -0
- data/lib/view_model/cepc50/dec_rr.rb +4 -0
- data/lib/view_model/cepc51/dec_rr.rb +4 -0
- data/lib/view_model/cepc60/dec_rr.rb +4 -0
- data/lib/view_model/cepc70/dec_rr.rb +4 -0
- data/lib/view_model/cepc71/dec_rr.rb +4 -0
- data/lib/view_model/cepc800/dec_rr.rb +4 -0
- data/lib/view_model/cepc_ni800/dec_rr.rb +4 -0
- data/lib/view_model/dec_rr_wrapper.rb +2 -0
- data/lib/view_model/dec_summary_wrapper.rb +2 -0
- data/lib/view_model/dec_wrapper.rb +2 -0
- data/lib/view_model/decar_s_70/common_schema.rb +109 -0
- data/lib/view_model/decar_s_70/dec.rb +235 -0
- data/lib/view_model/decar_s_70/dec_rr.rb +102 -0
- data/lib/view_model/factory.rb +4 -1
- metadata +13 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 44f53edb23a539cbc882b65a1ce15baff6f2ab918f565d41918c433622adda46
|
|
4
|
+
data.tar.gz: fab418244814328f957fcd9539804fdf794cea1b5622be8d3a8278e216abe971
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 637f1a23d81cb624d8128bfd229a20e3c2db0aae8f50a2704877796dbe64a40756bc015752f92ccea3d4d785598b1640156c0dd5dba02075cf8160f9c4479407
|
|
7
|
+
data.tar.gz: 0cb4ea6c12754f37fe81a10eecdcb849865fe85383bc74fbd62746e6ad62157f0bc688409eb2c6a766c6821f8ee6b90ca04aef459ae28d4df5d21fef1207d535
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:CS="DCLG-CEPC/CommonStructures" targetNamespace="DCLG-CEPC/CommonStructures" elementFormDefault="qualified" attributeFormDefault="unqualified" version="LIG-CEPC-7.0">
|
|
3
|
+
<!-- ***************************************************************************
|
|
4
|
+
Simple Type declarations for Identification Block property values
|
|
5
|
+
*************************************************************************** -->
|
|
6
|
+
<xs:simpleType name="ReportRetrievalType">
|
|
7
|
+
<xs:restriction base="xs:string">
|
|
8
|
+
<xs:enumeration value="List"/>
|
|
9
|
+
<xs:enumeration value="Data"/>
|
|
10
|
+
<xs:enumeration value="PDF"/>
|
|
11
|
+
</xs:restriction>
|
|
12
|
+
</xs:simpleType>
|
|
13
|
+
<xs:element name="MessageIdentifier" type="CS:MessageIdentifier"/>
|
|
14
|
+
<xs:complexType name="MessageIdentifier">
|
|
15
|
+
<xs:annotation>
|
|
16
|
+
<xs:documentation>The standard Identifying Block for all messages.</xs:documentation>
|
|
17
|
+
</xs:annotation>
|
|
18
|
+
<xs:sequence>
|
|
19
|
+
<xs:element name="ClientID" type="xs:string" minOccurs="0"/>
|
|
20
|
+
<!--<xs:element name="TransactionID" type="xs:string"/>-->
|
|
21
|
+
<xs:element name="Timestamp" type="xs:dateTime"/>
|
|
22
|
+
</xs:sequence>
|
|
23
|
+
</xs:complexType>
|
|
24
|
+
</xs:schema>
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<xs:schema xmlns="DCLG-CEPC/Exceptions" xmlns:ERR="DCLG-CEPC/Exceptions" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:UDT="DCLG-CEPC" targetNamespace="DCLG-CEPC/Exceptions" elementFormDefault="qualified" version="LIG-CEPC-7.0">
|
|
3
|
+
<xs:annotation>
|
|
4
|
+
<xs:documentation>© Department of Communities and Local Government. © Crown copyright, 2007. The Home Condition Report logo and associated wording is a registered trade mark - any unlicensed use is not permitted. Copyright in the typographical arrangement of this document rests with the Crown. This publication, excluding logos, may be reproduced free of charge in any format or medium for research, private study, for internal circulation within an organisation or by registered scheme users. This is subject to it being reproduced accurately and not used in a misleading context.</xs:documentation>
|
|
5
|
+
</xs:annotation>
|
|
6
|
+
<xs:import namespace="DCLG-CEPC" schemaLocation="../Reports/BaseDataTypes.xsd"/>
|
|
7
|
+
<xs:element name="DataItem" type="DataItem"/>
|
|
8
|
+
<xs:complexType name="DataItem">
|
|
9
|
+
<xs:annotation>
|
|
10
|
+
<xs:documentation>The Data-Item from the input XML message that caused the data exception to be raised.
|
|
11
|
+
|
|
12
|
+
Each Data Item consists of the name of the XML Element(s) that caused the exception to be raised, the value assigned to the element and an optional reference to the individual element of there is more than one of them in the XML Message.</xs:documentation>
|
|
13
|
+
</xs:annotation>
|
|
14
|
+
<xs:sequence>
|
|
15
|
+
<xs:element name="ItemName" type="xs:string">
|
|
16
|
+
<xs:annotation>
|
|
17
|
+
<xs:documentation>The name of the data-item that was in error. This is that actual name of the element as it is in the message, for example:
|
|
18
|
+
|
|
19
|
+
<MyElementName>[Value]</MyElementName>
|
|
20
|
+
|
|
21
|
+
would result in:
|
|
22
|
+
|
|
23
|
+
<ItemName>MyElementname</DataItem>
|
|
24
|
+
|
|
25
|
+
</xs:documentation>
|
|
26
|
+
</xs:annotation>
|
|
27
|
+
</xs:element>
|
|
28
|
+
<xs:element name="Path" type="xs:string" minOccurs="0">
|
|
29
|
+
<xs:annotation>
|
|
30
|
+
<xs:documentation>The full X-Path to the XML Element containing the error.
|
|
31
|
+
|
|
32
|
+
This is required because there may be multiple data-items with the same name sometimes in separate functional components and sometimes the same functional component may occur multiple times. In both cases the Data-Item Name may not uniquely identify the actual error.</xs:documentation>
|
|
33
|
+
</xs:annotation>
|
|
34
|
+
</xs:element>
|
|
35
|
+
<xs:element name="Value" type="xs:anyType" minOccurs="0">
|
|
36
|
+
<xs:annotation>
|
|
37
|
+
<xs:documentation>The value that was in error.
|
|
38
|
+
|
|
39
|
+
This is an optional field because it may be the case where a mandatory data-item isn't present.</xs:documentation>
|
|
40
|
+
</xs:annotation>
|
|
41
|
+
</xs:element>
|
|
42
|
+
</xs:sequence>
|
|
43
|
+
</xs:complexType>
|
|
44
|
+
<xs:element name="ExceptionList" type="ExceptionList"/>
|
|
45
|
+
<xs:complexType name="ExceptionList">
|
|
46
|
+
<xs:sequence>
|
|
47
|
+
<xs:element name="Exception" type="Exception" maxOccurs="unbounded"/>
|
|
48
|
+
</xs:sequence>
|
|
49
|
+
</xs:complexType>
|
|
50
|
+
<xs:element name="Exception" type="Exception"/>
|
|
51
|
+
<xs:complexType name="Exception">
|
|
52
|
+
<xs:sequence>
|
|
53
|
+
<xs:element name="ErrorCode" type="UDT:NumericString"/>
|
|
54
|
+
<xs:element name="ErrorMessage" type="UDT:Sentence"/>
|
|
55
|
+
<xs:element name="DataItemList" type="DataItemList" minOccurs="0"/>
|
|
56
|
+
</xs:sequence>
|
|
57
|
+
</xs:complexType>
|
|
58
|
+
<xs:element name="DataItemList" type="DataItemList"/>
|
|
59
|
+
<xs:complexType name="DataItemList">
|
|
60
|
+
<xs:annotation>
|
|
61
|
+
<xs:documentation>The set of Data-Items that were instrumental in raising the exception.
|
|
62
|
+
|
|
63
|
+
This is an aggregation point for all of the Data-Items because there may be more than one Data-Item for each exception. For example if the check is that A = B and the check fails then the values of both A and B need to be returned as the context of the exception.</xs:documentation>
|
|
64
|
+
</xs:annotation>
|
|
65
|
+
<xs:sequence>
|
|
66
|
+
<xs:element name="DataItem" type="DataItem" maxOccurs="unbounded"/>
|
|
67
|
+
</xs:sequence>
|
|
68
|
+
</xs:complexType>
|
|
69
|
+
</xs:schema>
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<!-- edited with XMLSpy v2007 rel. 3 sp1 (http://www.altova.com) by Niall Horgan (Bridgeall Technology) -->
|
|
3
|
+
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:CS="DCLG-CEPC/CommonStructures" xmlns:ERR="DCLG-CEPC/Exceptions" xmlns:UDT="DCLG-CEPC/BaseDataTypes" xmlns:CEPC="DCLG-CEPC" xmlns:ns1="http://www.est.org.uk/DECAR/lodgement" targetNamespace="http://www.est.org.uk/DECAR/lodgement" elementFormDefault="qualified" attributeFormDefault="unqualified" version="LIG-CEPC-7.0">
|
|
4
|
+
<xs:import namespace="DCLG-CEPC" schemaLocation="../Reports/CEPC-Reports.xsd"/>
|
|
5
|
+
<xs:import namespace="DCLG-CEPC/CommonStructures" schemaLocation="../CommonFiles/CommonStructures.xsd"/>
|
|
6
|
+
<xs:element name="LodgeReportRequest">
|
|
7
|
+
<xs:complexType>
|
|
8
|
+
<xs:sequence>
|
|
9
|
+
<xs:element name="MessageIdentifier" type="CS:MessageIdentifier"/>
|
|
10
|
+
<xs:element name="Report" type="CEPC:Report" maxOccurs="2"/>
|
|
11
|
+
</xs:sequence>
|
|
12
|
+
</xs:complexType>
|
|
13
|
+
</xs:element>
|
|
14
|
+
</xs:schema>
|
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<xs:schema xmlns="DCLG-CEPC" xmlns:UDT="DCLG-CEPC" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="DCLG-CEPC" version="LIG-CEPC-7.0" elementFormDefault="qualified">
|
|
3
|
+
<xs:annotation>
|
|
4
|
+
<xs:documentation>
|
|
5
|
+
The purpose of Base Data Type declarations is to provide a point of declaration of all the primitive datatypes that are in use within the domain and can be used to describe the contents of the Business Information Model.
|
|
6
|
+
|
|
7
|
+
A significant problem with the XML Schema Definition standard is that it is designed to solve a large number of software implementation problems and so provides an equally large number of datatypes with each datatype describing a variation on a theme.
|
|
8
|
+
|
|
9
|
+
For example as well as "number" we also have "short" (with a range of values corresponding to that which may be stored a 16 bit computer word), "long", "int", "integer", "decimal", "double", "byte" and quite a few other number variations. However many of these datatypes are highly-specialized computer-focused definitions that have little or no relevance to the Business stakeholders.
|
|
10
|
+
|
|
11
|
+
Most likely the business stakeholders would only recognise a limited number of datatypes - such as String, Date, Time, Integer, Decimal - and some domain-specific ones - such as Money (amount + currency attribute) - and will prefer the model to be restricted to that small set.
|
|
12
|
+
|
|
13
|
+
The advantages of defining a set of base data types and gathering them together in a single file are:
|
|
14
|
+
* It allows documented controls to be placed on the primitive types that are used in any schema.
|
|
15
|
+
* It will improve consistency of use of primitive types (e.g. consistent use of "integer" rather than "int", "long" etc.) that must be handled by applications
|
|
16
|
+
* It will improve code reuse.
|
|
17
|
+
* It allows standard attributes to be added to all elements whilst hiding the detail in a non business definition layer.
|
|
18
|
+
|
|
19
|
+
The principle is something like the way datayping is implemented in Java (as well as other programming languages) where every primitive datatype, such as "string", is wrapped by an equivalent complex class such as "String".The Java developer could declare object attributes using the "string" primitive but this isn't regarded as good practice. By using the "pfdt:string" class instead they are protected from physical changes to the implementation of "string" and also gain an extension point where additional behaviour not supported by the primitive datatype can be defined.
|
|
20
|
+
|
|
21
|
+
The declarations in this file underpin the User Defined Types, Message Infrastructure and Business Entity Template declarations.
|
|
22
|
+
</xs:documentation>
|
|
23
|
+
</xs:annotation>
|
|
24
|
+
<xs:simpleType name="Percentage">
|
|
25
|
+
<xs:restriction base="xs:decimal">
|
|
26
|
+
<xs:maxInclusive value="100"/>
|
|
27
|
+
<xs:minInclusive value="0"/>
|
|
28
|
+
</xs:restriction>
|
|
29
|
+
</xs:simpleType>
|
|
30
|
+
<xs:simpleType name="NumericString">
|
|
31
|
+
<xs:annotation>
|
|
32
|
+
<xs:documentation>A Numeric String is a string based datatype for representing strings, such as telephone numbers and IP addresses, that are limited to the numeric character-set.
|
|
33
|
+
</xs:documentation>
|
|
34
|
+
</xs:annotation>
|
|
35
|
+
<xs:restriction base="xs:string">
|
|
36
|
+
<xs:pattern value="[0-9\-\.\+]+"/>
|
|
37
|
+
</xs:restriction>
|
|
38
|
+
</xs:simpleType>
|
|
39
|
+
<xs:simpleType name="Flag">
|
|
40
|
+
<xs:annotation>
|
|
41
|
+
<xs:documentation>The Boolean datatype is a redefinition of the XML Schema defined "Boolean". The XSD version is a logical True / False datatype whereas from a data processing perspective it is more likely to be a string based Y/N value. This could be seen as an Enumerated Domain but "Boolean" is so common that it makes more sense to be a base datatype.
|
|
42
|
+
</xs:documentation>
|
|
43
|
+
</xs:annotation>
|
|
44
|
+
<xs:restriction base="xs:string">
|
|
45
|
+
<xs:enumeration value="Y">
|
|
46
|
+
<xs:annotation>
|
|
47
|
+
<xs:documentation>Yes</xs:documentation>
|
|
48
|
+
</xs:annotation>
|
|
49
|
+
</xs:enumeration>
|
|
50
|
+
<xs:enumeration value="N">
|
|
51
|
+
<xs:annotation>
|
|
52
|
+
<xs:documentation>No</xs:documentation>
|
|
53
|
+
</xs:annotation>
|
|
54
|
+
</xs:enumeration>
|
|
55
|
+
</xs:restriction>
|
|
56
|
+
</xs:simpleType>
|
|
57
|
+
<xs:simpleType name="LanguageCode">
|
|
58
|
+
<xs:restriction base="xs:string">
|
|
59
|
+
<xs:enumeration value="1">
|
|
60
|
+
<xs:annotation>
|
|
61
|
+
<xs:documentation>English</xs:documentation>
|
|
62
|
+
</xs:annotation>
|
|
63
|
+
</xs:enumeration>
|
|
64
|
+
<xs:enumeration value="2">
|
|
65
|
+
<xs:annotation>
|
|
66
|
+
<xs:documentation>Welsh</xs:documentation>
|
|
67
|
+
</xs:annotation>
|
|
68
|
+
</xs:enumeration>
|
|
69
|
+
</xs:restriction>
|
|
70
|
+
</xs:simpleType>
|
|
71
|
+
<xs:element name="Sentence" type="Sentence"/>
|
|
72
|
+
<xs:complexType name="Sentence">
|
|
73
|
+
<xs:annotation>
|
|
74
|
+
<xs:documentation>String value with a language code for natural-language text.</xs:documentation>
|
|
75
|
+
</xs:annotation>
|
|
76
|
+
<xs:simpleContent>
|
|
77
|
+
<xs:extension base="xs:string">
|
|
78
|
+
<xs:attribute name="language" type="LanguageCode" use="optional">
|
|
79
|
+
<xs:annotation>
|
|
80
|
+
<xs:documentation>Identifies the language that the sentence is recorded in.</xs:documentation>
|
|
81
|
+
</xs:annotation>
|
|
82
|
+
</xs:attribute>
|
|
83
|
+
</xs:extension>
|
|
84
|
+
</xs:simpleContent>
|
|
85
|
+
</xs:complexType>
|
|
86
|
+
<xs:simpleType name="YN_Flag">
|
|
87
|
+
<xs:restriction base="xs:string">
|
|
88
|
+
<xs:enumeration value="Yes"/>
|
|
89
|
+
<xs:enumeration value="No"/>
|
|
90
|
+
</xs:restriction>
|
|
91
|
+
</xs:simpleType>
|
|
92
|
+
<xs:simpleType name="RRNType">
|
|
93
|
+
<xs:annotation>
|
|
94
|
+
<xs:documentation>
|
|
95
|
+
The Report Reference Number is a 20-digit unique identifier assigned to each Report.
|
|
96
|
+
It is formatted as five blocks of four digits i.e. 9999-9999-9999-9999-9999 and generated by an algorithm described in Appendix A "Report ID Generation" of Section 18 "Transformation Rules" of the Technical Standards.
|
|
97
|
+
</xs:documentation>
|
|
98
|
+
</xs:annotation>
|
|
99
|
+
<xs:restriction base="xs:string">
|
|
100
|
+
<xs:pattern value="[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}"/>
|
|
101
|
+
</xs:restriction>
|
|
102
|
+
</xs:simpleType>
|
|
103
|
+
<xs:element name="ACRatedOuput" type="ACRatedOuput"/>
|
|
104
|
+
<xs:complexType name="ACRatedOuput">
|
|
105
|
+
<xs:choice>
|
|
106
|
+
<xs:element name="AC-kW-Rating" type="xs:positiveInteger">
|
|
107
|
+
<xs:annotation>
|
|
108
|
+
<xs:documentation>Rating in kW</xs:documentation>
|
|
109
|
+
</xs:annotation>
|
|
110
|
+
</xs:element>
|
|
111
|
+
<xs:element name="AC-Rating-Unknown-Flag" type="xs:boolean"/>
|
|
112
|
+
</xs:choice>
|
|
113
|
+
</xs:complexType>
|
|
114
|
+
<xs:simpleType name="ACEstimatedOutput">
|
|
115
|
+
<xs:restriction base="xs:int">
|
|
116
|
+
<xs:enumeration value="1">
|
|
117
|
+
<xs:annotation>
|
|
118
|
+
<xs:documentation>Below 12kW</xs:documentation>
|
|
119
|
+
</xs:annotation>
|
|
120
|
+
</xs:enumeration>
|
|
121
|
+
<xs:enumeration value="2">
|
|
122
|
+
<xs:annotation>
|
|
123
|
+
<xs:documentation>Between 12kW and 250kW</xs:documentation>
|
|
124
|
+
</xs:annotation>
|
|
125
|
+
</xs:enumeration>
|
|
126
|
+
<xs:enumeration value="3">
|
|
127
|
+
<xs:annotation>
|
|
128
|
+
<xs:documentation>Greater than 250kW</xs:documentation>
|
|
129
|
+
</xs:annotation>
|
|
130
|
+
</xs:enumeration>
|
|
131
|
+
</xs:restriction>
|
|
132
|
+
</xs:simpleType>
|
|
133
|
+
<xs:simpleType name="ACInspectionCommissioned">
|
|
134
|
+
<xs:restriction base="xs:int">
|
|
135
|
+
<xs:enumeration value="1">
|
|
136
|
+
<xs:annotation>
|
|
137
|
+
<xs:documentation>Yes, inspection completed</xs:documentation>
|
|
138
|
+
</xs:annotation>
|
|
139
|
+
</xs:enumeration>
|
|
140
|
+
<xs:enumeration value="2">
|
|
141
|
+
<xs:annotation>
|
|
142
|
+
<xs:documentation>Yes, inspection commissioned</xs:documentation>
|
|
143
|
+
</xs:annotation>
|
|
144
|
+
</xs:enumeration>
|
|
145
|
+
<xs:enumeration value="3">
|
|
146
|
+
<xs:annotation>
|
|
147
|
+
<xs:documentation>No inspection completed or commissioned</xs:documentation>
|
|
148
|
+
</xs:annotation>
|
|
149
|
+
</xs:enumeration>
|
|
150
|
+
<xs:enumeration value="4">
|
|
151
|
+
<xs:annotation>
|
|
152
|
+
<xs:documentation>Not relevant</xs:documentation>
|
|
153
|
+
</xs:annotation>
|
|
154
|
+
</xs:enumeration>
|
|
155
|
+
<xs:enumeration value="5">
|
|
156
|
+
<xs:annotation>
|
|
157
|
+
<xs:documentation>Don't know</xs:documentation>
|
|
158
|
+
</xs:annotation>
|
|
159
|
+
</xs:enumeration>
|
|
160
|
+
</xs:restriction>
|
|
161
|
+
</xs:simpleType>
|
|
162
|
+
<xs:simpleType name="DECStatusCode">
|
|
163
|
+
<xs:restriction base="xs:int">
|
|
164
|
+
<xs:enumeration value="0">
|
|
165
|
+
<xs:annotation>
|
|
166
|
+
<xs:documentation>Standard DEC</xs:documentation>
|
|
167
|
+
</xs:annotation>
|
|
168
|
+
</xs:enumeration>
|
|
169
|
+
<xs:enumeration value="1">
|
|
170
|
+
<xs:annotation>
|
|
171
|
+
<xs:documentation>Default DEC</xs:documentation>
|
|
172
|
+
</xs:annotation>
|
|
173
|
+
</xs:enumeration>
|
|
174
|
+
<xs:enumeration value="2">
|
|
175
|
+
<xs:annotation>
|
|
176
|
+
<xs:documentation>Asset Rating Only DEC</xs:documentation>
|
|
177
|
+
</xs:annotation>
|
|
178
|
+
</xs:enumeration>
|
|
179
|
+
</xs:restriction>
|
|
180
|
+
</xs:simpleType>
|
|
181
|
+
</xs:schema>
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<!-- edited with XMLSpy v2007 rel. 3 sp1 (http://www.altova.com) by Niall Horgan (Bridgeall Technology) -->
|
|
3
|
+
<xs:schema xmlns="DCLG-CEPC" xmlns:CEPC="DCLG-CEPC" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="DCLG-CEPC" elementFormDefault="qualified" version="LIG-CEPC-7.0">
|
|
4
|
+
<xs:include schemaLocation="./Reported-Data.xsd"/>
|
|
5
|
+
<xs:include schemaLocation="./Performance-Summary.xsd"/>
|
|
6
|
+
<xs:include schemaLocation="./Report-Header.xsd"/>
|
|
7
|
+
<xs:include schemaLocation="./Input-Data.xsd"/>
|
|
8
|
+
<xs:element name="Report" type="Report"/>
|
|
9
|
+
<xs:complexType name="Report">
|
|
10
|
+
<xs:sequence>
|
|
11
|
+
<xs:element name="Report-Header" type="Report-Header"/>
|
|
12
|
+
<xs:element name="Summary-Of-Performance" type="Summary-Of-Performance" minOccurs="0"/>
|
|
13
|
+
<xs:element name="Formatted-Report" type="xs:base64Binary" minOccurs="0"/>
|
|
14
|
+
<xs:choice>
|
|
15
|
+
<xs:element name="OR-Operational-Rating" type="OR-Operational-Rating" minOccurs="0"/>
|
|
16
|
+
<xs:element name="AR-Questions" type="AR-Questions" minOccurs="0"/>
|
|
17
|
+
<xs:element name="Unstructured-Data" type="Unstructured-Data" minOccurs="0"/>
|
|
18
|
+
</xs:choice>
|
|
19
|
+
<xs:choice>
|
|
20
|
+
<xs:element name="Advisory-Report" type="Advisory-Report"/>
|
|
21
|
+
<xs:element name="Display-Certificate" type="Display-Certificate"/>
|
|
22
|
+
</xs:choice>
|
|
23
|
+
</xs:sequence>
|
|
24
|
+
</xs:complexType>
|
|
25
|
+
<xs:element name="Insurance-Details" type="Insurance-Details"/>
|
|
26
|
+
<xs:complexType name="Insurance-Details">
|
|
27
|
+
<xs:annotation>
|
|
28
|
+
<xs:documentation>Details of the Professional Indemnity Insurance policy used to provide cover against a compensation claim against any particular Report.
|
|
29
|
+
|
|
30
|
+
A Report may be covered by an Professional Indemnity Insurance policy in one of three different ways:
|
|
31
|
+
* The Energy Assessor has personal Professional Indemnity Insurance and the Report is covered by this.
|
|
32
|
+
* The Report is covered by an umbrella Professional Indemnity Insurance policy held by the Report Supplier (the employer of the Energy Assessor) that assigned the inspection to the Energy Assessor.
|
|
33
|
+
* An individual insurance policy is taken out to cover the individual report such as the case where the property is unusual and falls outside the Energy Assessors normal Professional Indemnity Insurance policy.
|
|
34
|
+
|
|
35
|
+
A Energy Assessor may use any or all of these methods to providing Professional Indemnity Insurance for a Report on a case-by-case basis.
|
|
36
|
+
</xs:documentation>
|
|
37
|
+
</xs:annotation>
|
|
38
|
+
<xs:all>
|
|
39
|
+
<xs:element name="Insurer" type="xs:string">
|
|
40
|
+
<xs:annotation>
|
|
41
|
+
<xs:documentation>The name of the insurance company that underwrites / issued the insurance policy</xs:documentation>
|
|
42
|
+
</xs:annotation>
|
|
43
|
+
</xs:element>
|
|
44
|
+
<xs:element name="Policy-No" type="xs:string">
|
|
45
|
+
<xs:annotation>
|
|
46
|
+
<xs:documentation>The policy number of the insurance policy</xs:documentation>
|
|
47
|
+
</xs:annotation>
|
|
48
|
+
</xs:element>
|
|
49
|
+
<xs:element name="Effective-Date" type="xs:date">
|
|
50
|
+
<xs:annotation>
|
|
51
|
+
<xs:documentation>The date that the insurance policy becomes effective (commences cover)</xs:documentation>
|
|
52
|
+
</xs:annotation>
|
|
53
|
+
</xs:element>
|
|
54
|
+
<xs:element name="Expiry-Date" type="xs:date">
|
|
55
|
+
<xs:annotation>
|
|
56
|
+
<xs:documentation>The date that the insurance policy is supposed to expire.</xs:documentation>
|
|
57
|
+
</xs:annotation>
|
|
58
|
+
</xs:element>
|
|
59
|
+
<xs:element name="PI-Limit" type="xs:decimal">
|
|
60
|
+
<xs:annotation>
|
|
61
|
+
<xs:documentation>The upper limit of the Professional Indemnity cover provided by the insurance policy.</xs:documentation>
|
|
62
|
+
</xs:annotation>
|
|
63
|
+
</xs:element>
|
|
64
|
+
</xs:all>
|
|
65
|
+
</xs:complexType>
|
|
66
|
+
</xs:schema>
|