epb_view_models 2.2.21 → 2.3.0

data/api/schemas/xml/RdSAP-Schema-S-14.0/RdSAP/SAP-EPC/Templates/SAP05-Report.xsd

@@ -0,0 +1,195 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema targetNamespace="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" xmlns="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:bdt="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" xmlns:SAP05="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" elementFormDefault="qualified" version="LIG-14.0">
+	<xs:import namespace="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" schemaLocation="../UDT/BaseDataTypes.xsd"/>
+	<xs:include schemaLocation="../UDT/SharedDomains.xsd"/>
+	<xs:include schemaLocation="../UDT/SAP05-Domains.xsd"/>
+	<xs:include schemaLocation="../Templates/UserManagement.xsd"/>
+	<xs:include schemaLocation="../Templates/Property.xsd"/>
+	<xs:include schemaLocation="../Templates/SAP05-CollectedData.xsd"/>
+	<xs:include schemaLocation="../Templates/EPC-Certificate.xsd"/>
+	<xs:element name="Energy-Performance-Certificate" type="Energy-Performance-Certificate"/>
+	<xs:complexType name="Energy-Performance-Certificate">
+		<xs:sequence>
+			<xs:element name="SAP-Version" type="SAP-VersionCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>SAP version that was used for the assessment.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="BEDF-Revision-Number" type="xs:nonNegativeInteger" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>BEDF Revision Number from SEDBUK database if boiler details retrieved from database (as on the $001 line in bedf2005.dat); if boiler or other data (mechanical vent system, PFGHRD) from database.  This must be included if any item is from database. At the moment it can be
+- boilers
+- mech vent system
+but others things will be added in future revisions.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Calculation-Software-Name" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Name of the software used to perform the SAP calculation.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Calculation-Software-Version" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Version of the software used to perform the SAP calculation.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Report-Header" type="Report-Header" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Energy-Assessment" type="Energy-Assessment" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="SAP05-Data" type="SAP05-Data" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="PDF" type="xs:base64Binary" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Insurance-Details" type="Insurance-Details" minOccurs="0" maxOccurs="1"/>
+			<xs:element name="ExternalDefinitions-Revision-Number" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>A number indicating the version of related ExternalDefinitions.xsd</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:element name="ReportKeyFields" type="ReportKeyFields"/>
+	<xs:complexType name="ReportKeyFields">
+		<xs:annotation>
+			<xs:documentation>Primary Key Fields definition for a Report - used when a message requires a reference tio a report to be passed.</xs:documentation>
+		</xs:annotation>
+		<xs:sequence>
+			<xs:element name="RRN" type="bdt:RRNType" minOccurs="1" maxOccurs="1"/>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:element name="Insurance-Details" type="Insurance-Details"/>
+	<xs:complexType name="Insurance-Details">
+		<xs:annotation>
+			<xs:documentation>Details of the Professional Indemnity Insurance policy used to provide cover against a compensation claim against any particular Home Condition Report.
+
+A particular Home Condition Report may be covered by an Professional Indemnity Insurance policy in one of three different ways:
+*	The Home Inspector has personal Professional Indemnity Insurance and the Home Condition Report is covered by this.
+*	The Home Condition Report is covered by an umbrella Professional Indemnity Insurance policy held by the Home Condition Report Supplier that assigned the inspection to the Home Inspector.
+*	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 Home Inspectors normal Professional Indemnity Insurance policy.
+
+A Home Inspector may use any or all of these methods to providing Professional Indemnity Insurance for a Home Condition Report on a case-by-case basis.
+</xs:documentation>
+		</xs:annotation>
+		<xs:all>
+			<xs:element name="Insurer" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The name of the insurance company that underwrites / issued the insurance policy</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Policy-No" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The policy number of the insurance policy</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Effective-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the insurance policy becomes effective (commences cover)</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Expiry-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the insurance policy is supposed to expire.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="PI-Limit" type="bdt:Money" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The upper limit of the Professional Indemnity cover provided by the insurance policy.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+		</xs:all>
+	</xs:complexType>
+	<xs:element name="Report-Header" type="Report-Header"/>
+	<xs:complexType name="Report-Header">
+		<xs:annotation>
+			<xs:documentation>Report Header contains all the identification and searchable details for the Report.</xs:documentation>
+		</xs:annotation>
+		<xs:sequence>
+			<xs:element name="RRN" type="bdt:RRNType" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Report Reference Number is the unique report Identifier that the report will be publicly known by.
+
+The RRN is allocated to the Report at the point that it is registered and will be algorithmically derived from the natural key characteristics of the Home Condition Report i.e. The Unique Property Reference Number (UPRN) and Inspection Date.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Inspection-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the inspection was actually carried out by the Home Inspector.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Report-Type" type="ReportTypeCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The type of Home Inspection that was carried out.
+
+Initially the only allowed type will be a Home Condition Report inspection but this may be extended in the future to cover Energy Assessment Only inspections.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Completion-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the Home Inspector completed the report. This will be after the Inspection Date but generally before the Registration Date.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Registration-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the report was submitted to the HCR Registration Organisation for lodging in the HCR Register.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Status" type="ReportStatusCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The Status of the Report.
+
+A Home Condition Report can have a number of distinct states depending on whereabouts in its overall lifecycle the HCR is - see Home Condition Report Statechart for more details.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Language-Code" type="bdt:LanguageCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The language that the report is written in. </xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Restricted-Access" type="RestrictedAccessCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Indicates that the Seller wants to restrict access to the Home Condition Report to General Public / Unregistered Users only.
+
+Some members of the public have a moral / religious objection to money lending and hence may not want to let Mortgage Lenders have access to the data. When set to "Yes" retrieval of the structured (XML) data will be blocked.
+
+However anyone with access to the Report Reference Number (RRN) can retrieve the PDF version of the Home Condition Report via the public access mechanism which cannot be restricted in this way.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Transaction-Type" type="TransactionType" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Seller-Commission-Report" type="bdt:Flag" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Indicates that the HCR was commissioned by the Seller of the Property or their Agent. This is required in order to differentiate these reports from Buyer commisioned reports  which are not eligible for inclusion in a Home Information Pack</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Property-Type" type="PropertyTypeCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Describes the type of Property that is being inspected. This should be the same as the Property-Type recorded in the Property-Details section.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Home-Inspector" type="Home-Inspector" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Property" type="Property" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Region-Code" type="UKRegionCode" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Region within the UK.  This field is optional.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Country-Code" type="UKCountryCode" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Country within the UK.  This field is optional.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Related-Party-Disclosure">
+				<xs:complexType>
+					<xs:choice>
+						<xs:element name="Related-Party-Disclosure-Text" type="bdt:Sentence" minOccurs="1" maxOccurs="1">
+							<xs:annotation>
+								<xs:documentation>For backward compatibility only.</xs:documentation>
+							</xs:annotation>
+						</xs:element>
+						<xs:element name="Related-Party-Disclosure-Number" type="DisclosureCode" minOccurs="1" maxOccurs="1">
+							<xs:annotation>
+								<xs:documentation>Code indicating any potential conflicts of interest or commercial relationships with other parties.</xs:documentation>
+							</xs:annotation>
+						</xs:element>
+					</xs:choice>
+				</xs:complexType>
+			</xs:element>
+		</xs:sequence>
+	</xs:complexType>
+</xs:schema>

data/api/schemas/xml/RdSAP-Schema-S-14.0/RdSAP/SAP-EPC/Templates/UserManagement.xsd

@@ -0,0 +1,215 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema targetNamespace="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" xmlns="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:bdt="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" xmlns:SAP05="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05" elementFormDefault="qualified" version="LIG-14.0">
+	<xs:import namespace="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" schemaLocation="../UDT/BaseDataTypes.xsd"/>
+	<xs:include schemaLocation="../UDT/SharedDomains.xsd"/>
+	<xs:include schemaLocation="../Templates/Property.xsd"/>
+	<xs:simpleType name="CertificateNumberType">
+		<xs:annotation>
+			<xs:documentation>The Certificate Number is a 10-character fixed-length alphanumeric code consisting of 4 characters identifying the Certification Scheme and a 6-digit zero-padded identifier for each Home Inspector certified by that Certification Scheme. For example ABCD987654, XYZ_123456 etc.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:pattern value="[A-Z/_]{4}[0-9]{6}"/>
+			<xs:minLength value="10"/>
+			<xs:maxLength value="10"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="Home-Inspector" type="Home-Inspector"/>
+	<xs:complexType name="Home-Inspector">
+		<xs:annotation>
+			<xs:documentation>A Certified Home Inspector is a person certified by a Certification Scheme - that is they exist on the Home Inspector Register - as being qualified to carry out a Home Inspection and produce a Home Condition Report. 
+
+The exact criteria for fit + proper are laid down in regulations and the Business Standards and it is the responsibility of the Certification Scheme to carry out sufficient checks to ensure those criteria are adhered to. 
+
+Although covered by a different regulatory regime a Home Inspector and Energy Assessor serve synonymous roles in the product of a Home Condition Report or Energy Performance Certificate respectively.</xs:documentation>
+		</xs:annotation>
+		<xs:all>
+			<xs:element name="Name" type="PersonNameType" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The name by which the Home Inspector is registered. This is a structured name containing prefix, first name + surname.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Certification-Date" type="xs:date" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The date that the status is/was effective from</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Status" type="HomeInspectorStatusCode" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The current status of the Home Inspector e.g. Registered, Not Active, Suspended etc. 
+
+Reports are only acceptable from Home Inspectors who are actually "Active" at the point that the Report is submitted for registration.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Notify-Lodgement" type="bdt:Flag" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Indicates whether the Home Inspector wants to be notified that a new Home Condition Report has been lodged in the HCR Register under his name.
+
+If "Yes" then the HCR Registration Operating Entity must send a written notification, preferably an e-mail to the Home Inspector's registered E-Mail Address, for every Home Condition Report that the Home Inspector produces.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Contact-Address" type="AddressType" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The address that any written correspondence can be sent to. This is not the same as the Registered Address because it may, of course, be a Post Office Box.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Web-Site" type="xs:string" minOccurs="0" maxOccurs="1"/>
+			<xs:element name="E-Mail" type="xs:string" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>the E-Mail address that the Authorised User can be contacted at.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Fax" type="PhoneNumberType" minOccurs="0" maxOccurs="1"/>
+			<xs:element name="Telephone" type="PhoneNumberType" minOccurs="0" maxOccurs="1"/>
+			<xs:element name="Qualifications" type="xs:string" minOccurs="0" maxOccurs="1"/>
+			<xs:element name="Specialisms" type="xs:string" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>A free-text list of any specialisms that the Home Inspector may offer to the consumer e.g. Thatched Roofs, SBEM etc). The list is at the discretion of the Home Inspector though may eventaully evolve into a predefined list.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Company-Name" type="xs:string" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The Name of the Company that the Home Inspector is empolyed by.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Postcode-Coverage" type="Postcode-CoverageType" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>Comma-delimited string of Postcode Areas and/or Postcode Outcodes that the Home Inspector covers - for example: NN, PE18, LE27. 
+
+This is used by the General Public as part of the Search Home Inspector Register to find Home Inspectors that take work in a particular area.
+
+An empty list means that the Home Inspector does not cover any specific areas (which would be the case if they did not take privately commissioned work) and hence would not match on any Postcode based search.
+</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Inspector-Report-Types" type="Inspector-Report-Types" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>A list of ReportTypeCode elements that indicate what reports the assessor/inspector is allowed to undertake.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Certification-Scheme" type="Certification-Scheme" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Base-Postcode-Location" type="PostcodeType" minOccurs="0" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The full postcode that the Home Inspector works from.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Identification-Number">
+				<xs:complexType>
+					<xs:choice>
+						<xs:element name="Certificate-Number" type="CertificateNumberType" minOccurs="1" maxOccurs="1">
+							<xs:annotation>
+								<xs:documentation>The unique identifier assigned to the Home Inspector by the Certification Scheme by which they can be identified throughout their membership of the Certification Scheme. The Certificate Number is included in the HCR.</xs:documentation>
+							</xs:annotation>
+						</xs:element>
+						<xs:element name="Membership-Number" type="xs:string" minOccurs="1" maxOccurs="1">
+							<xs:annotation>
+								<xs:documentation>For Scottish DEAs only</xs:documentation>
+							</xs:annotation>
+						</xs:element>
+					</xs:choice>
+				</xs:complexType>
+			</xs:element>
+		</xs:all>
+	</xs:complexType>
+	<xs:simpleType name="HomeInspectorStatusCode">
+		<xs:restriction base="xs:string">
+			<xs:enumeration value="Inactive">
+				<xs:annotation>
+					<xs:documentation>Inactive</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Registered">
+				<xs:annotation>
+					<xs:documentation>Registered</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Struck-Off">
+				<xs:annotation>
+					<xs:documentation>Struck Off</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Suspended">
+				<xs:annotation>
+					<xs:documentation>Suspended</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="PersonNameType" type="PersonNameType"/>
+	<xs:complexType name="PersonNameType">
+		<xs:annotation>
+			<xs:documentation>A Person Name is a complex structure to capture the separate components of the name for a Person, consisting of:
+*	A prefix e.g. "Mr", "Mrs", "Dr" etc.
+*	First Name e.g. "John"
+*	Middle Initial 
+*	Surname e.g. "Smith"
+*	Suffix e.g. "PhD", "FRICS" 
+The First Name and Surname are the only mandatory elements of a name.
+
+The name elements can then be combined in a number of different ways to produce different formats appropriate to the output context.
+
+Note that all parts of the Persons Name should be stored as uppercase strings because this makes it easier to search and index the names but some components may be converted to mixed case for printing on reports and such like.
+</xs:documentation>
+		</xs:annotation>
+		<xs:all>
+			<xs:element name="Prefix" type="xs:string" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="First-Name" type="xs:string" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Surname" type="xs:string" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Suffix" type="xs:string" minOccurs="1" maxOccurs="1"/>
+		</xs:all>
+	</xs:complexType>
+	<xs:element name="Inspector-Report-Types" type="Inspector-Report-Types"/>
+	<xs:complexType name="Inspector-Report-Types">
+		<xs:sequence>
+			<xs:element name="Report-Type" type="ReportTypeCode" minOccurs="1" maxOccurs="unbounded"/>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:simpleType name="PhoneNumberType">
+		<xs:restriction base="xs:string">
+			<xs:pattern value="[0-9\-\.\)\(\+ ]+"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:simpleType name="Postcode-CoverageType">
+		<xs:restriction base="xs:string">
+			<xs:pattern value="[A-Z]{1,2}[0-9]{0,2}(,[A-Z]{1,2}[0-9]{0,2})*"/>
+			<xs:maxLength value="500"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="Certification-Scheme" type="Certification-Scheme"/>
+	<xs:complexType name="Certification-Scheme">
+		<xs:annotation>
+			<xs:documentation>The Certification Scheme is the "regulatory" body responsible for regulating the activities of the Home Inspectors. 
+
+A Certification Scheme will carry out certain primary functions in accordance with the standards, focussed around certifying, managing and regulating Home Inspectors and registering Home Condition Reports.
+
+Although covered by a different regulatory regime a Certification Scheme is synonymous with the role of an Accreditation Body in the production of an Energy Performance Certificate.</xs:documentation>
+		</xs:annotation>
+		<xs:all>
+			<xs:element name="Scheme-Name" type="xs:string" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Complaints-Address" type="AddressType" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The address to which any complaints should be sent.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Contact-Address" type="AddressType" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The address that any written correspondence can be sent to. This is not the same as the Registered Address because it may, of course, be a Post Office Box.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Web-Site" type="xs:string" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="E-Mail" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>the E-Mail address that the Authorised User can be contacted at.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Registered-Name" type="xs:string" minOccurs="1" maxOccurs="1">
+				<xs:annotation>
+					<xs:documentation>The public name by which the Authorised User is known by - this is either a personal name (e.g. "Mr John Smith") built up from the components of the Person Name if the Authorised User is an individual such as a Home Inspector or a Company Name if the Authorised User is an organisation.
+
+In the case of a individual the name may not be unique (e.g. there may be many thousands of people called "Mr John Smith") so this is information about the Authorised User rather than an identifier.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Fax" type="PhoneNumberType" minOccurs="1" maxOccurs="1"/>
+			<xs:element name="Telephone" type="PhoneNumberType" minOccurs="1" maxOccurs="1"/>
+		</xs:all>
+	</xs:complexType>
+</xs:schema>

data/api/schemas/xml/RdSAP-Schema-S-14.0/RdSAP/SAP-EPC/UDT/BaseDataTypes.xsd

@@ -0,0 +1,175 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema targetNamespace="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" xmlns="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" xmlns:bdt="http://www.est.org.uk/epc/lodgement/estV20/DCLG-SAP05/BaseDataTypes" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" version="LIG-14.0">
+	<xs:annotation>
+		<xs:documentation>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. 
+
+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. 
+
+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.
+
+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.
+
+The advantages of defining a set of base data types and gathering them together in a single file are:
+*	It allows documented controls to be placed on the primitive types that are used in any schema.
+*	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
+*	It will improve code reuse.
+*	It allows standard attributes to be added to all elements whilst hiding the detail in a non business definition layer.
+
+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.
+
+The declarations in this file underpin the User Defined Types, Message Infrastructure and Business Entity Template declarations. 
+</xs:documentation>
+	</xs:annotation>
+	<xs:simpleType name="Percentage">
+		<xs:restriction base="xs:decimal">
+			<xs:maxInclusive value="100"/>
+			<xs:minInclusive value="0"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="Money" type="Money"/>
+	<xs:complexType name="Money">
+		<xs:annotation>
+			<xs:documentation>Extension of a Decimal value for use with monetary values where a currency code needs to
+be specified. 
+
+The currency code is actually metadata about the value so, in line with good XML practice, the Currency Code is declared as an XML-Attribute of the Money datatype rather than as a separate XML-Element.
+
+The currency attribute should then include a list of valid currencies codes that are supported.
+</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:extension base="xs:decimal">
+				<xs:attribute name="currency" use="optional" type="xs:string"/>
+			</xs:extension>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="Count">
+		<xs:annotation>
+			<xs:documentation>A count of the number of occurrences of something - must therefore be &gt;=0. This is the functional equivalent of the XML nonNegativeInteger datatype.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:integer"/>
+	</xs:simpleType>
+	<xs:element name="Classifier" type="Classifier"/>
+	<xs:complexType name="Classifier">
+		<xs:annotation>
+			<xs:documentation>A Classifier is an extended datatype used as the basis for a data-item whose allowed values are restricted to a pre-defined set of Classifiers or Enumerated Codes.
+
+Classifier should never actually be used as the datatype for any data-item in a finished data model because a specific Enumerated Domain should be declared for defining the specific values in the domain. However it is acceptable in an incomplete model where definition of the domain has yet to be completed.</xs:documentation>
+		</xs:annotation>
+		<xs:all/>
+		<xs:attribute name="pid" use="required" type="xs:string"/>
+	</xs:complexType>
+	<xs:element name="Reference" type="Reference"/>
+	<xs:complexType name="Reference">
+		<xs:annotation>
+			<xs:documentation>The Reference Data Type is any association between two Business Entities (or their sub-
+components). In order to be consistent across the entire dataset all references contain the ID of the thing being referenced and the value actually assigned to the element is the 'display value'. The type of reference is derived from the underlying data model
+
+This has a shortcoming in that we can't support multi-value keys using this datatype. However
+I'm reluctant to extend the datatype to include the ID as a nested element because it becomes very cumbersome to use. Instead, in all likelihood, the Primary Key to any entity in a data processing application is likely to be a single-value, system-generated key so we're imposing that restriction here as well.</xs:documentation>
+		</xs:annotation>
+		<xs:all/>
+	</xs:complexType>
+	<xs:simpleType name="Measurement">
+		<xs:annotation>
+			<xs:documentation>A measurement of something such as a length or area. All measurements are to 2 decimal places and must be positive.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:decimal"/>
+	</xs:simpleType>
+	<xs:element name="IDString" type="IDString"/>
+	<xs:complexType name="IDString">
+		<xs:annotation>
+			<xs:documentation>A string containing a unique identifier for something.
+
+The underlying assumption is that each instance of a class or entity will have a unique identifier assigned to it which can then be assigned to any referencing entity as a reference to the entity instance.
+
+This is a very similar concept to XML ID datatype but is locally defined because of the need to extend the datatype with domain specific attributes.</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:extension base="xs:string"/>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="NumericString">
+		<xs:annotation>
+			<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. 
+</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:pattern value="[0-9\-\.\+]+"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:simpleType name="Flag">
+		<xs:annotation>
+			<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.
+</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:enumeration value="Y">
+				<xs:annotation>
+					<xs:documentation>Yes</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="N">
+				<xs:annotation>
+					<xs:documentation>No</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:simpleType name="LanguageCode">
+		<xs:restriction base="xs:string">
+			<xs:enumeration value="1">
+				<xs:annotation>
+					<xs:documentation>English</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="2">
+				<xs:annotation>
+					<xs:documentation>Welsh</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:simpleType name="ExtendedBoolean">
+		<xs:annotation>
+			<xs:documentation>An extended boolean type that also allows 'unknown' as a value.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:token">
+			<xs:enumeration value="false"/>
+			<xs:enumeration value="true"/>
+			<xs:enumeration value="unknown"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="Sentence" type="Sentence"/>
+	<xs:complexType name="Sentence">
+		<xs:annotation>
+			<xs:documentation>String value with a language code for natural-language text.</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:extension base="xs:string">
+				<xs:attribute name="language" use="optional" type="LanguageCode">
+					<xs:annotation>
+						<xs:documentation>Identifies the language that the sentence is recorded in.</xs:documentation>
+					</xs:annotation>
+				</xs:attribute>
+			</xs:extension>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="RRNType">
+		<xs:annotation>
+			<xs:documentation>The Report Reference Number is a 20-digit unique identifier assigned to each Report. 
+
+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.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:pattern value="[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}"/>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:element name="ForeignKey" type="ForeignKey"/>
+	<xs:complexType name="ForeignKey">
+		<xs:sequence/>
+		<xs:attribute name="EntityName" use="required" type="xs:string"/>
+		<xs:attribute name="KeyName" use="optional" type="xs:string"/>
+		<xs:attribute name="DomainName" use="optional" type="xs:string"/>
+	</xs:complexType>
+</xs:schema>