<?xml version="1.0" encoding="UTF-8"?>
<!--W3C XML Schema generated by XMLSpy v2016 rel. 2 sp1 (x64) (http://www.altova.com)-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:fi1="urn:postnl/mail/fields1" xmlns:udt="urn:postnl/mail/oagis/9/unqualifieddatatypes/1.1" xmlns:ccts="urn:un:unece:uncefact:documentation:1.1" xmlns:cl1="urn:postnl/mail/codelists/1" xmlns:qdt="urn:postnl/mail/oagis/9/qualifieddatatypes/1.1" targetNamespace="urn:postnl/mail/fields1" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xsd:import namespace="urn:postnl/mail/oagis/9/unqualifieddatatypes/1.1" schemaLocation="UnqualifiedDataTypes.xsd"/>
	<xsd:import namespace="urn:postnl/mail/oagis/9/qualifieddatatypes/1.1" schemaLocation="QualifiedDataTypes.xsd"/>
	<xsd:import namespace="urn:postnl/mail/codelists/1" schemaLocation="CodeLists1.xsd"/>
	<xsd:element name="Amount" type="fi1:AmountType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The monetary value of the object in which the amount is associated</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BasisAmount" type="fi1:AmountType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the base amount from which the charge/allowance is derived.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TaxAuthorityAmount" type="fi1:AmountType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">This is used to represent the tax amount in the currency of the taxing authority in addition to the transactional tax amount which may be in a different currency.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EmbeddedData" type="fi1:BinaryObjectType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Allows the data to be embedded directly into the BOD instance.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ChannelCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the channel in which the associated entity comes.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Code" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Element for the communication of all codes.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CountrySubDivisionCode" type="fi1:CountrySubDivisionCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Qualifies the further division of the Country. These may be Districts, Regions, States, Provinces etc. A possible list of values is as specified in ISO 3166-2. The name attribute identifies the name of this e.g. District, Region etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CreditRatingCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Credit rating.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DeliveryPointCode" type="fi1:DeliveryPointCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the Dock or the Mail Stop or Lane or any other specific Delivery Point. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DirectionCode" type="fi1:CodeType"/>
	<xsd:element name="FormatCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Format Code indicates the format of the address. Examples are US Military, US Formatted Address, European Formatted Address etc.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FormatDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Describes the format of the address. Examples are US Military, US Formatted Address, Netherlands, French, Spanish, UK Formatted Address etc.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentMethodCode" type="fi1:PaymentMethodCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the payment method code for the associate entity. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PostalCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Postal Code of the Address. (NEN5825 5.3.11) nb: in address is dit veld vervangen door postalcode</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ReasonCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the reason for an activity</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SourceCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="Observation">Idenfifies the type of source that brought the associated entity.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StatusCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the Code to indicate the status for the Noun or Component in which the Status Component occurs.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UPCPackagingLevelCode" type="fi1:CodeType"/>
	<xsd:element name="UseCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Code identifying the usage of the contact point e.g. business, private, etc.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CountryCode" type="fi1:CountryCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Country in which the Address is in. A possible list of values is as specified in ISO 3166-2.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CurrencyCode" type="fi1:CurrencyCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Specifies the currency code of the object in which it is associated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SourceCurrencyCode" type="fi1:CurrencyCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The source Currency Code for the monetary amount to be converted.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TargetCurrencyCode" type="fi1:CurrencyCodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The target Currency Code for the monetary amount to be converted.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FileType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the type of the file type of the attachment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Type" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the type of the object in which assoicated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.starstandards.org">Date and time that the associated entity took place .</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DocumentDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The date that document was created within the system of record.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EffectiveDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">This is the DateTime the associated object is made effective</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EndDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the ending timestamp of the event.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LastModificationDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The datetime on which the object was last modified</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SetDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the date in which the conversion factor was set by the Issueing agency.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StartDateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Start timestamp indicating the starting point of the event.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Year" type="fi1:YearDateType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the financial year in which this accounting period occurs. Generally a period of 12 months for which the company regularly has to create financial statements</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Duration" type="fi1:DurationMeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AccountID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifier of the account</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BICID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CAGEID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Commercial and Government Entity (CAGE) code is a five-character ID number used extensively within the Department of Defense to identify specific companies.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DODAACID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">DoDAAC (Dept. of Defense Activity Address Code) is a unique six-position, alphanumeric string that uniquely identifies departments, locations, units, and so on within the military. This identifier serves the same purpose as a company</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DUNSID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifier for business provided by Dun and Bradstreet.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EMailAddressID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">An identifier that identifies an electronic mail address.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="IBANID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>International Bank Account Number. Het International Bank Account Number (IBAN) identificeert elke rekeninghouder, inclusief bank en vestigingsland. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ReleaseNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the Release Number in the case of Blanket POs</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="RevisionID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShipUnitTotalID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">In a set of similar shipping units for a delivery, ShipUnitTotalId represents the total or final unit in the set.  When used in conjunction with ShipUnitSequenceId and printed on a shipping unit label or packing list, the receiving partner can easily ascertain whether or not the delivery was complete.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShipUnitSequenceID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">In a set of similar shipping units for a delivery, ShipUnitSequenceId represents a particular unit out of the total set.  When used in conjunction with ShipUnitTotalId and printed on a shipping unit label or packing list, the receiving partner can easily ascertain whether or not the delivery was complete.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SourceID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Idenfifies the source that brought the associated entity.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SystemID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the system in which the userid applies.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TaxID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifier for a business or individual provided by the government. This maybe a FIIN, Social Security Number, or Drivers License Number to name a few.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TrackingID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">TRACKINGID is a unique identifier for the purpose of tracking an individual package or shipment

Examples of a valid TRACKINGID include:
•An express parcel tracking number as typically assigned by UPS, DHL, Fedex or other similar carriers.
•A UCC (Uniform Code Council) Serialized Shipping Container (SCC-18) identifier, as assigned by the shipper.  
•A "Pro Number" (Progressive Number), as assigned by an LTL (less-than-truckload) freight carrier.  Since the same Pro Number can be assigned to multiple shipping units within an LTL shipment, the SHIPUNITSEQ and SHIPUNITTOT field identifiers may be used to identify the individual pieces.
•The unique identifier of a motor freight trailer, railroad box or tank car, ocean freight container or other transportation vessel.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="URI" type="fi1:URIType"/>
	<xsd:element name="VariationID" type="fi1:IdentifierType"/>
	<xsd:element name="ISBN" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Allows a reference to an ISBN.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LineNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Number" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Account Number, depending upon the context used this may be the credit card number of the checking account number, etc.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ScheduleLineNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the ScheduleLineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated  by the DocumentId under DocumentIds.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SubLineNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the SublineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated  by the DocumentId under DocumentIds.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DimensionRandomSizeIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">An indicator specifying random sizes in the dimensions.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HTMLPreferredIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates that the associated entity preferrs HTML format.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InclusiveIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The InclusiveIndicator element is used to identify whether the SearchValue should be an included or excluded component of the result set.  For example, if a user was looking for ballpoint pens, but NOT red ballpoint pens, the transaction would contain two instances of the SearchTerm data type one containing a SearchValue of ‘Ballpoint’ and an SearchValueInclusive of 'Inclusive' and one containing a SearchValue of ‘Red’ and an SearchValueInclusive of 'Exclusive'</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Indicator" type="fi1:IndicatorType"/>
	<xsd:element name="AltitudeMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the value and unit of measure in the z-axis in a three dimensional system (= Elevation).

Examples of this maybe the Altitude in the case of a map of the world, or the height or shelf in a rack system in the case of a manufacturing or warehouse facility.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DegreeMeasure" type="fi1:MeasureType"/>
	<xsd:element name="GrossWeightMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Gross weight of the associated entity. The total weight of the entity without reduction of packaging or container. I.e The Gross wieght of a pallet of goods includes the weight of the pallet.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HeightMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the Height of an object</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LengthMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the length of an object</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MaximumMeasure" type="fi1:MeasureType"/>
	<xsd:element name="MaximumWeightMeasure" type="fi1:MeasureType"/>
	<xsd:element name="Measure" type="fi1:MeasureType"/>
	<xsd:element name="MinimumMeasure" type="fi1:MeasureType"/>
	<xsd:element name="MinimumWeightMeasure" type="fi1:MeasureType"/>
	<xsd:element name="MinuteMeasure" type="fi1:MeasureType"/>
	<xsd:element name="NetWeightMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Net weight of the associaed item. The net weight is calculated by subtracting the tare weight or the weight of the container from the GrossWeight.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OverSizeMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">A measure specifying the over size of a dimension.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SecondMeasure" type="fi1:MeasureType"/>
	<xsd:element name="TareWeightMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Tare weight of the associated Entity. The Tare weight is the weight of the packaging when empty (in the case of a pallet the weight of the empty pallet) that when subtracted from the Gross weight results in the Net weight.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TotalVolumeMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Quantifies the volume, or amount of space, that is occupied by an item, container or shipment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UnderSizeMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">A measure specifying the under size of a dimension.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="WidthMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the width of an object</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FlashpointTemperature" type="fi1:TemperatureMeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">FlashpointTemperature is related to hazadous substances or goods, indicates the temperature at which the associated substance of goods become flammable, explossive or toxic..</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MinimumTemperature" type="fi1:TemperatureMeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the lowest temperature that the associated item can be kept.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MaximumTemperature" type="fi1:TemperatureMeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the maximum termperature that the associated item can be kept.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="RateNumeric" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the multiplier to convert the source units to the target units. (e.g.) The conversion of one currency to another currency monitary amount in the from currency is multiplied by the CalculationRateNumeric to calcultate the monitary amount in the to currency. Another example maybe the conversion between units of measure.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Sequence" type="fi1:PositiveIntegerNumericType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">A value expressing the value of a Sequence.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SourceUnitBaseNumeric" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Specifies the unit base of the source currency for currencies with small denominations.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TargetUnitBaseNumeric" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Specifies the unit base of the target currency for currencies with small denominations.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BasisQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the base quantityfrom which the charge/allowance is derived.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CapacityPerPackageQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the maximum number of instances of an item in the unit of measure that maybe contained within the package.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FileSizeQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Specifies how big the file is.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OrderQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the quantity of a material or product ordered by the customer.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PerPackageQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the number of instances of the item in the unit of measure contained with in the package.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Quantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SCACID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Standard Carrier Alpha Code, a two-to-four digit identification, is used by (in the United States) transportation industry to identify freight carriers in computer systems and shipping documents such as Bill of Lading, Freight Bill, Packing List, and Purchase Order.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Access" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AreaDialing" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The area dialing code for a communication number.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BuildingNumber" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Number of the building or house on the street that identifies where to deliver mail.  For example, Building 300 on Standards Parkway. (NEN5825 5.3.4)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CountryDialing" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The country dialing code for a communication number.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DialNumber" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The commication number, not including country dialing or area dialing codes.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Directions" type="fi1:TextType"/>
	<xsd:element name="Extension" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The extension of the assoicated communication number.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Floor" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The floor where the housename is located</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Formula" type="fi1:TextType"/>
	<xsd:element name="JobTitle" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LineOne" type="fi1:TextType"/>
	<xsd:element name="LineTwo" type="fi1:TextType"/>
	<xsd:element name="LineThree" type="fi1:TextType"/>
	<xsd:element name="LineFour" type="fi1:TextType"/>
	<xsd:element name="LineFive" type="fi1:TextType"/>
	<xsd:element name="PostOfficeBox" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies a Post Office Box number. (NEN5825 5.3.8)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Responsibility" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">A text description of the responsibility of the associated entity.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Text" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is a message to the reader about the object associated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Title" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the title of the person. For example Dr..</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Unit" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the apartment number or office suite.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Description" type="fi1:DescriptionType">
		<xsd:annotation>
			<xsd:documentation>Description of the related subject.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AttentionOfName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The name of the person or organization that the associated entity is intended.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BankName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The name of the bank.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BuildingName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The building or house name on the street that identifies where to deliver mail</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CareOfName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The name that the associated entity is sent by.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CityName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the town or the city (NEN 5825 5.3.13)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CitySubDivisionName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Qualifies the further division of the City, example a city may have many districts or Boroughs. The type attribute identifies the type of this entity e.g. City, Borough etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CompanyName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The name of the company unit.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DepartmentName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of a department of the company</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FamilyName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the persons family name.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FileName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Indicates the name of the File being referenced.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GivenName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the Persons given name or first name.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MaidenName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>Achternaam bij geboorte</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MiddleName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the persons middle name.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Name" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Identifies the Name of the object in which associated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NickName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>Voornaam</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Reason" type="fi1:SequencedTextType"/>
	<xsd:element name="StreetName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Street Name where the building/ house is located. (NEN5825 5.3.2)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StreetNameShort" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Street Name where the building/ house is located. (NEN5825 5.3.3)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SuffixName" type="fi1:NameType"/>
	<xsd:element name="TechnicalName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Is the Technical name of the associated entity.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Note" type="fi1:NoteType"/>
	<xsd:complexType name="UserAreaType">
		<xsd:sequence>
			<xsd:any namespace="##any" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:element name="UserArea" type="fi1:UserAreaType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.</xsd:documentation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.</xsd:documentation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="AmountType">
		<xsd:simpleContent>
			<xsd:extension base="udt:AmountType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="BinaryObjectType">
		<xsd:simpleContent>
			<xsd:extension base="udt:BinaryObjectType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="CodeType">
		<xsd:annotation>
			<xsd:documentation>Code_V2 is SAPPI naam</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="udt:CodeType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:simpleType name="DateTimeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Month_ Date. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText>A particular point in the progression of time together with the relevant supplementary information.  Provides the XML Schema simpleType that allows either just the Date or the Date and Time to be provided in the elements that are based on this type and/or types that use this as their base.</ccts:DefinitionText>
				<ccts:RepresentationTermName>Date</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Month</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:union memberTypes="udt:DateType udt:TimeType udt:DateTimeType"/>
	</xsd:simpleType>
	<xsd:simpleType name="DateType">
		<xsd:restriction base="udt:DateType"/>
	</xsd:simpleType>
	<xsd:simpleType name="TimeType">
		<xsd:restriction base="udt:TimeType"/>
	</xsd:simpleType>
	<xsd:complexType name="IdentifierType">
		<xsd:simpleContent>
			<xsd:extension base="udt:IdentifierType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:simpleType name="IndicatorType">
		<xsd:restriction base="udt:IndicatorType"/>
	</xsd:simpleType>
	<xsd:complexType name="MeasureType">
		<xsd:simpleContent>
			<xsd:extension base="udt:MeasureType"/>
			<!--NM 22-04-2013  ten behoeve van consistentie SAPPI is extensie type gemarkeerd als tekst.
				<xsd:attribute name="type" type="fi1:NormalizedStringType"/>-->
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:simpleType name="NumericType">
		<xsd:restriction base="udt:NumericType"/>
	</xsd:simpleType>
	<xsd:complexType name="QuantityType">
		<xsd:simpleContent>
			<xsd:extension base="udt:QuantityType"/>
			<!--NM: 22-04-2013  tbv consistentie SAP PI is extensie met type gemarkeerd als tekst.
				<xsd:attribute name="type" type="fi1:NormalizedStringType"/>-->
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="TextType">
		<xsd:simpleContent>
			<xsd:extension base="udt:TextType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="NameType">
		<xsd:annotation>
			<xsd:documentation>NameTypeCore = SAPPI naam</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="udt:NameType">
				<xsd:attribute name="sequence" type="fi1:IntegerNumericType">
					<xsd:annotation>
						<xsd:documentation source="http://www.openapplications.org/platform/1">When a Name occurs multiple times, this sequence integer can be used to provide the order in which the Names are meaningful.</xsd:documentation>
					</xsd:annotation>
				</xsd:attribute>
				<xsd:attribute name="sequenceName" type="fi1:StringType"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="DescriptionType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Description_ Text. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText/>
				<ccts:RepresentationTermName>Text</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Description</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="udt:TextType">
				<xsd:attribute name="type" type="fi1:NormalizedStringType"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="NoteType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified.</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:DescriptionType">
				<xsd:attribute name="author" type="fi1:StringType" use="optional"/>
				<xsd:attribute name="entryDateTime" type="fi1:DateTimeType" use="optional"/>
				<xsd:attribute name="status" type="fi1:StringType" use="optional"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="TemperatureMeasureType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">TemperatureMeasureType is logically derived from UN/CEFACT TBG17 ABIE TemperatureType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file.

</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:MeasureType"/>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:element name="SalutationPreferredName" type="fi1:PreferredNameType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/platform/1">Way the person is addressed e.g. Honorable etc?</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="PreferredNameType">
		<xsd:simpleContent>
			<xsd:extension base="fi1:NameType">
				<xsd:attribute name="preferred" type="fi1:IndicatorType" use="optional"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="SequencedIDType">
		<xsd:simpleContent>
			<xsd:extension base="fi1:IdentifierType">
				<xsd:attribute name="sequence" type="fi1:PositiveIntegerNumericType"/>
				<xsd:attribute name="sequenceName" type="fi1:NormalizedStringType" use="optional"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="SequencedTextType">
		<xsd:simpleContent>
			<xsd:extension base="fi1:TextType">
				<xsd:attribute name="sequence" type="fi1:PositiveIntegerNumericType" use="optional"/>
				<xsd:attribute name="sequenceName" type="fi1:NormalizedStringType" use="optional"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:simpleType name="CountryCodeContentType">
		<xsd:restriction base="cl1:CountryCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="CountrySubdivisionCodeContentType">
		<xsd:restriction base="cl1:CountrySubdivisionCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="CurrencyCodeContentType">
		<xsd:restriction base="cl1:CurrencyCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="DeliveryPointCodeContentType">
		<xsd:restriction base="cl1:DeliveryPointCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="LanguageCodeContentType">
		<xsd:restriction base="cl1:LanguageCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="PartyCategoryCodeContentType">
		<xsd:restriction base="cl1:PartyCategoryCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="PartyRoleCodeContentType">
		<xsd:restriction base="cl1:PartyRoleCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="PaymentMethodCodeContentType">
		<xsd:restriction base="cl1:PaymentMethodCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="TaxCodeContentType">
		<xsd:restriction base="cl1:TaxCodeContentType"/>
	</xsd:simpleType>
	<xsd:simpleType name="YearDateType">
		<xsd:restriction base="qdt:YearDateType"/>
	</xsd:simpleType>
	<xsd:simpleType name="URIType">
		<xsd:restriction base="qdt:URIType"/>
	</xsd:simpleType>
	<xsd:simpleType name="DurationMeasureType">
		<xsd:restriction base="qdt:DurationMeasureType"/>
	</xsd:simpleType>
	<xsd:simpleType name="IntegerNumericType">
		<xsd:restriction base="qdt:IntegerNumericType"/>
	</xsd:simpleType>
	<xsd:simpleType name="PositiveIntegerNumericType">
		<xsd:restriction base="qdt:PositiveIntegerNumericType"/>
	</xsd:simpleType>
	<xsd:simpleType name="NormalizedStringType">
		<xsd:restriction base="qdt:NormalizedStringType"/>
	</xsd:simpleType>
	<xsd:simpleType name="StringType">
		<xsd:restriction base="qdt:StringType"/>
	</xsd:simpleType>
	<xsd:attributeGroup name="CodeListAttributeGroup">
		<xsd:attribute name="listID" type="fi1:NormalizedStringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC2</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>The identification of a list of codes.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Identification</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listAgencyID" type="fi1:NormalizedStringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC3</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Agency. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>An agency that maintains one or more lists of codes.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Agency</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
					<ccts:UsageRule>Defaults to the UN/EDIFACT data element 3055 code list.</ccts:UsageRule>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listAgencyName" type="fi1:StringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC4</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Agency Name. Text</ccts:DictionaryEntryName>
					<ccts:Definition>The name of the agency that maintains the list of codes.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Agency Name</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Text</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listName" type="fi1:StringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC5</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Name. Text</ccts:DictionaryEntryName>
					<ccts:Definition>The name of a list of codes.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Name</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Text</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listVersionID" type="fi1:NormalizedStringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC6</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Version. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>The version of the list of codes.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Version</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="name" type="fi1:StringType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC7</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code. Name. Text</ccts:DictionaryEntryName>
					<ccts:Definition>The textual equivalent of the code content component.</ccts:Definition>
					<ccts:ObjectClass>Code</ccts:ObjectClass>
					<ccts:PropertyTermName>Name</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Text</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="languageID" type="fi1:LanguageCodeContentType" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC8</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Language. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>The identifier of the language used in the code name.</ccts:Definition>
					<ccts:ObjectClass>Language</ccts:ObjectClass>
					<ccts:PropertyTermName>Identification</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listURI" type="xsd:anyURI" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC9</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List. Uniform Resource. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>The Uniform Resource Identifier that identifies where the code list is located.</ccts:Definition>
					<ccts:ObjectClass>Code List</ccts:ObjectClass>
					<ccts:PropertyTermName>Uniform Resource Identifier</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
		<xsd:attribute name="listSchemeURI" type="xsd:anyURI" use="optional">
			<xsd:annotation>
				<xsd:documentation xml:lang="en">
					<ccts:UniqueID>UNDT000007-SC10</ccts:UniqueID>
					<ccts:CategoryCode>SC</ccts:CategoryCode>
					<ccts:DictionaryEntryName>Code List Scheme. Uniform Resource. Identifier</ccts:DictionaryEntryName>
					<ccts:Definition>The Uniform Resource Identifier that identifies where the code list scheme is located.</ccts:Definition>
					<ccts:ObjectClass>Code List Scheme</ccts:ObjectClass>
					<ccts:PropertyTermName>Uniform Resource Identifier</ccts:PropertyTermName>
					<ccts:RepresentationTermName>Identifier</ccts:RepresentationTermName>
					<ccts:PrimitiveType>string</ccts:PrimitiveType>
				</xsd:documentation>
			</xsd:annotation>
		</xsd:attribute>
	</xsd:attributeGroup>
	<xsd:complexType name="CountryCodeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Country_ Code. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText/>
				<ccts:RepresentationTermName>Code</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Country</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:CountryCodeContentType">
				<xsd:attributeGroup ref="fi1:CodeListAttributeGroup"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="CountrySubDivisionCodeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Country Subdivision_ Code. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText>A character string (letters, figures, or symbols) that for brevity and/or languange 
independence may be used to represent or replace a definitive value or text of an attribute together with relevant 
supplementary information.</ccts:DefinitionText>
				<ccts:RepresentationTermName>Code</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Country Subdivision</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:CountrySubdivisionCodeContentType">
				<xsd:attributeGroup ref="fi1:CodeListAttributeGroup"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="CurrencyCodeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Currency_ Code. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText/>
				<ccts:RepresentationTermName>Code</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Currency</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:CurrencyCodeContentType">
				<xsd:attributeGroup ref="fi1:CodeListAttributeGroup"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="DeliveryPointCodeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Delivery Point_ Code. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText>A character string (letters, figures, or symbols) that for brevity and/or languange 
independence may be used to represent or replace a definitive value or text of an attribute together with relevant 
supplementary information.</ccts:DefinitionText>
				<ccts:RepresentationTermName>Code</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Delivery Point</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:DeliveryPointCodeContentType">
				<xsd:attributeGroup ref="fi1:CodeListAttributeGroup"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:complexType name="PaymentMethodCodeType">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<ccts:UniqueID>QDT000000</ccts:UniqueID>
				<ccts:CategoryCode>QDT</ccts:CategoryCode>
				<ccts:DictionaryEntryName>Payment Method_ Code. Type</ccts:DictionaryEntryName>
				<ccts:VersionID>1.0</ccts:VersionID>
				<ccts:DefinitionText/>
				<ccts:RepresentationTermName>Code</ccts:RepresentationTermName>
				<ccts:QualifierTerm>Payment Method</ccts:QualifierTerm>
			</xsd:documentation>
		</xsd:annotation>
		<xsd:simpleContent>
			<xsd:extension base="fi1:PaymentMethodCodeContentType">
				<xsd:attributeGroup ref="fi1:CodeListAttributeGroup"/>
			</xsd:extension>
		</xsd:simpleContent>
	</xsd:complexType>
	<xsd:element name="POBoxPostalCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>OUD NIET MEER GEBRUIKEN! Postcode van de postbus. Veld alleen toegevoegd tbv mapping met ESR Adres. Niet gebruiken voor andere doeleinden.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BuildingNumberExtension" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">De letter die toegevoegd kan worden aan het huisnummer. (NEN5825 5.3.5)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The character that can be added to the number of the building or house on the street that identifies where to deliver mail.  </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BuildingNumberDesignation" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">Nadere aanduiding bij de adresgegevens om de plaats te duiden waar de persoon dan wel organisatie bereikbaar is. (NEN5825 5.3.1)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The designation that can be added to the number of the building or house on the street that identifies where to deliver mail.  </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HouseTrailerReference" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">De verwijzing naar de locatie van de woonwagen. (NEN5825 5.3.6)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The reference to the location of the house trailer.  </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HouseBoatReference" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">De verwijzing naar de locatie van de woonboot. (NEN5825 5.3.7)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The reference to the location of the house boat  </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BusinessReplyNumber" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">Identificeert een antwoordnummer. (NEN 5825 5.3.9)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">Identifies a Business Reply Number</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MunicipalityCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">De gemeente code. (NEN5825 5.3.15)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The code of the municipality</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MunicipalityName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation source="PostNL" xml:lang="NL">De naam van de gemeente. (NEN 5825 5.3.14)</xsd:documentation>
			<xsd:documentation source="PostNL" xml:lang="US">The name of the municipality</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PostApartNumber" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation>NEN 5825 5.3.10</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Image" type="fi1:BinaryObjectType">
		<xsd:annotation>
			<xsd:documentation>An image of a subject or a signature, etc.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ProcessCodeID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique ID defined by the organizational unit FB BLS</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ProcessCategoryCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Unique and meaningless Code defined by the organizational unit FB BLS. The ID is between the range from 100 up to 999.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationId" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique ID of the Location, registered in the Master Data System.(Formerly: Unique Code automatically assigned by SAP MDM)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of the Location identified by the LocationID</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationShortName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The short name of the Location identified by the LocationID</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OrganizationId" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique Code automatically assigned by SAP OM. T; wordt vervangen door SF</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EvraLocationCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>External reference to create a unique transport location for each combination of location and address.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AddressType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Identification of the kind of address type.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BAGLatitude" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>BAG-breedtegraad in meters (BAG - Basisadministratie Adressen en Gebouwen Rijksdriehoekstelsel)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BAGLongitude" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>BAG lengtegraad in meters (BAG Basisadminist ratie Adressen en Gebouwen, Rijksdriehoekstelsel)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DeliveryPointType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Defines the type of address.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DeliveryPointDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Describes the type of address.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ExternalReference" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Reference to the administration of the external manager of the BusinessLocation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InternalManagementCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Code which indicates if internal or external management is responsible for the item.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationMDMoldCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Unieke identificatie locatie alleen ten behoeve van Historie MDM.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Identification of the kind of location.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShortName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>A short description of the name.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ContactPersonID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique identifier of the contactperson.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CountryName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of the country.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PreferredCommunicationChannel" type="fi1:CodeType"/>
	<xsd:element name="StartDate" type="fi1:DateType">
		<xsd:annotation>
			<xsd:documentation>Start date indicating the starting point of the event.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EndDate" type="fi1:DateType">
		<xsd:annotation>
			<xsd:documentation>End date indicating the end day of the event ; it includes the end date.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ChamberOfCommerceID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>"KamerVanKoopHandelNummer"</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CustomerOrderID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>klantordernummer referentie (verwijzing naar voorgaande order)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PartyAggregate1" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation> level 1 party ID</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PartyAggregate2" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation> level 2 party ID</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CharacteristicName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation> KenmerkOmschrijving</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CharacteristicValue" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation> KenmerkWaarde</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AlternateID" type="fi1:IdentifierType"/>
	<xsd:element name="Ascription" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>Tenaamstelling</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BankNumber" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>RekeningNummer;
vanaf dec 2017 niet meer gebruiken. Of ID of BIC of IBAN.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ConsignmentID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique identifier of the (main)consignment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AlternateConsignmentID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique alternate identifier of the consignment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ConsignmentShippingDate" type="fi1:DateType">
		<xsd:annotation>
			<xsd:documentation>Date of delivering of the consignment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ContractDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Description of the contract.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ConsignmentDeliveryDate" type="fi1:DateType">
		<xsd:annotation>
			<xsd:documentation>The date the consignment will be deliverd by PostNL.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataFormatCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Indicates the format of a mail piece.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataLength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Length of a mail piece.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataWidth" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Width of a mail piece.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataThicknessClass" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Thickness class code of a mail piece.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataQuantity" type="fi1:QuantityType">
		<xsd:annotation>
			<xsd:documentation>Number of mail pieces belonging to the consignment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataProductWeight" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Weight of a mail piece.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataTotalWeight" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Total weight of the mail pieces belonging to the consignment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalPackagingCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Indicates how the mail piece is packaged.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="RegisteredName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The legal name of a company.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TradeName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The commercial name of a company, usually without legal designation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EndDeliveryPointID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Technical identification within PostNL of an end delivery point issued by the application BRPP</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DisplayName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of the person, suitable for display.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SalutationCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The code for an act, phrase, gesture, etc, that serves as a greeting.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SalutationText" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>The text of an act, phrase, gesture, etc, that serves as a greeting.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Initial" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>The first letter of a name or word, typically a person's given name or a word forming part of a phrase.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PrefixName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>A name placed before.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ChosenLastName" type="fi1:NameType"/>
	<xsd:element name="FormattedName" type="fi1:NameType"/>
	<xsd:element name="PaymentGroupCode" type="fi1:CodeType"/>
	<xsd:element name="FrankingMachineID" type="fi1:IdentifierType"/>
	<xsd:element name="EmballageCode" type="fi1:CodeType"/>
	<xsd:element name="TarraID" type="fi1:IdentifierType"/>
	<xsd:element name="NameTypeCode" type="fi1:CodeType"/>
	<xsd:element name="TransportEquipmentTypeCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A code signifying the type of this piece of transport equipment </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InsuranceValueAmount" type="fi1:AmountType">
		<xsd:annotation>
			<xsd:documentation>The amount covered by insurance for this goods item</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShippingMarks" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Remarks concerning the complete consignment, to be printed on the transport document.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NetNetWeightMeasure" type="fi1:MeasureType"/>
	<xsd:element name="ChargeableWeightMeasure" type="fi1:MeasureType"/>
	<xsd:element name="LoadingLengthMeasure" type="fi1:MeasureType"/>
	<xsd:element name="DunnageWeightMeasure" type="fi1:MeasureType"/>
	<xsd:element name="LocationConditionsCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A class to specify the conditions of the location where the event takes place.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocationConditionsDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Code indicating the specific condition of the location.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PackagingTypeCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A code signifying a type of packaging.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PackagingTypeDescription" type="fi1:TextType"/>
	<xsd:element name="GrossVolumeMeasure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Gross volume of the associated entity. The total volume of the entity without reduction of packaging or container. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BuyersItemIdentification" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Identifying information for this item, assigned by the buyer.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SellersItemIdentification" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Identifying information for this item, assigned by the seller.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ManufacturerItemIdentification" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Identifying information for this item, assigned by the manufacturer.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StandardItemIdentification" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Identifying information for this item, assigned according to a standard system, for example the GN-coding of Intrastat-system of Eurostat</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UNDGCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The UN code for this kind of hazardous item.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EmergencyProceduresCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A code signifying the emergency procedures for this hazardous item.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HazardousClassID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>An identifier for the hazard class applicable to this hazardous item as defined by the relevant regulation authority (e.g., the IMDG Class Number of the SOLAS Convention of IMO and the ADR/RID Class Number for the road/rail environment).</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HazardousRegulationCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Specification of the ADR tunnel code</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CustomerSegment" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Segment waartoe de klant is  ingedeeld, bijv. Consument, KleinZakelijk, Groot Zakelijk, Retail.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CustomerServiceType" type="fi1:CodeType"/>
	<xsd:element name="ContractType" type="fi1:CodeType"/>
	<xsd:element name="CustomerCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Onderverdeling van de klant in groepen, bijv. Zakelijke Klant, Consument.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ABCClass" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A definition of consumer types.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LoadFactor" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation>Defines how efficient the transport equipment is loaded.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GoodsItemTypeCode" type="fi1:CodeType"/>
	<xsd:element name="IssueID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Uitgave identificatie, bijv. Donald Duck week 36.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PhysicalDataThickness" type="fi1:MeasureType"/>
	<xsd:element name="AddressLabelingTypeCode" type="fi1:CodeType"/>
	<xsd:element name="MailingWrapperTypeCode" type="fi1:CodeType"/>
	<xsd:element name="MailingWrapperFinishingTypeCode" type="fi1:CodeType"/>
	<xsd:element name="WeekInYear" type="fi1:CodeType"/>
	<xsd:element name="ConsignmentPlannedDeliveryDate" type="fi1:DateType"/>
	<xsd:element name="FrankingAmount" type="fi1:AmountType"/>
	<xsd:element name="FrankingCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Code for the type of franking on the mailitem</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DeliveryDateTime" type="fi1:DateTimeType"/>
	<xsd:element name="ValueTrackingID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>de waarde van de tracking identificatie</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SymbologyTrackingID" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Dit is de wijze waarop de valuetrackingid is weergegeven bij afdrukken. dit kan zijn: alfanummerieke tekst in geval van een Icentificaite van soort Printregel. Als de waarde afgedrukt wordt als barcode, wordt dit gedaan volgens een symbologie. Het is vergelijkbaar met het lettertype bij tekst. Sommige symbologien zijn beschikbaar als lettertype in tekstverwerkers b.v. KIX. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PostNLTrackingIDName" type="fi1:NameType"/>
	<xsd:element name="RepresentationTrackingID" type="fi1:TextType"/>
	<xsd:element name="MailItemTrackingID" type="fi1:IdentifierType"/>
	<xsd:element name="LogisticProductCode" type="fi1:CodeType"/>
	<xsd:element name="TotalNumberOfAddresses" type="fi1:MeasureType"/>
	<xsd:element name="TotalNumber" type="fi1:MeasureType"/>
	<xsd:element name="ItemID" type="fi1:IdentifierType"/>
	<xsd:element name="CommercialItemOptions" type="fi1:TextType"/>
	<xsd:element name="TotalNumberofParts" type="fi1:MeasureType"/>
	<xsd:element name="PartSequence" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Volgorde nummer van de subset.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PartID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Identificatie van de subset van de voormelding.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UPNID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>UPN/Unique Person Number</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="EORIID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Het EORI-nummer is een uniek identificatienummer dat bedrijven moeten gebruiken bij gegevensuitwisseling met de Douane in alle lidstaten van de Europese Unie.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PartyCode" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Bedoeld om in de Klant structuur info mee te kunnen geven over de (Klant- of) Party code(s)</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ExpStatNr" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Export Statistieknummer</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NoReturnOnUndeliverableIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Indicatie of een pakket retour moet of niet indien onbestelbaar</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GiftIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Indicatie of een pakket een geschenk bevat. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DocumentsIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Indicatie of een pakket documenten bevat. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CommercialGoodsIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Indicatie of een pakket commerciële goederen bevat.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CommercialSampleIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Indicatie of een pakket een commercieel proefmonster bevat.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ReturnGoodsIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Geeft aan of het pakket geretourneerde goederen bevat</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InvoiceIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Geeft aan of het pakket een factuur bevat</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InvoiceNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Factuurnummer van de verzender.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CertificateIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Geeft aan of het pakket een certificaat bevat</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CertificateNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Certificaatnummer van de verzender. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LicenceIndicator" type="fi1:IndicatorType">
		<xsd:annotation>
			<xsd:documentation>Geeft aan of het pakket een licentie bevat</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LicenceNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Licentienummer van de verzender. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Remark" type="fi1:DescriptionType">
		<xsd:annotation>
			<xsd:documentation>Opmerkingen over de zending ten behoeve van de douaneverklaring.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GoodsCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CountryOfOrigin" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ReturnID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Kenmerk ten behoeve van retourzending.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UpNetwPartnerRefNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UpNetwPartnerShipmentID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UpSenderRefNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Referentienummer upstream verzender</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UpSenderShipmentID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Zendingnummer upstream verzender</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DownNetwPartnerShipmentID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ErrorCode" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PartyInfo" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation/>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="RootingNumber" type="fi1:IdentifierType"/>
	<xsd:element name="TransactionType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>bijv. Cash/ Collect on Delivery, Pre-Paid.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NotationStandard" type="fi1:CodeType"/>
	<xsd:element name="imageWidth" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The compression scheme used for the image data. When a primary image is JPEG compressed, this designation is not necessary and is omitted. When thumbnails use JPEG compression, this tag value is set to 6.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="imageLength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Image height. The number of rows of image data. In JPEG compressed data a JPEG marker is used.

</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="bitsPerSample" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of bits per image component. In this standard each component of the image is 8 bits, so the value for this tag is 8. See also SamplesPerPixel. In JPEG compressed data a JPEG marker is used instead of this tag.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="compression" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The compression scheme used for the image data. When a primary image is JPEG compressed, this designation is not necessary and is omitted. When thumbnails use JPEG compression, this tag value is set to 6.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="photometricInterpretation" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Pixel composition. In JPEG compressed data a JPEG marker is used instead of this tag.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="imageDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>A character string giving the title of the image. It may be a comment such as "1988 company picnic" or the like. Two-byte character codes cannot be used. When a 2-byte code is necessary, the Exif Private tag UserComment is to be used.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="make" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Manufacturer of image input equipment</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="model" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Model of image input equipment
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="stripOffsets" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For each strip, the byte offset of that strip. With JPEG compressed data this designation is not needed and is omitted.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="orientation" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The image orientation viewed in terms of rows and columns.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="samplesPerPixel" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of components per pixel. Since this standard applies to RGB and YCbCr images, the value set for this tag is 3. In JPEG compressed data a JPEG marker is used instead of this tag.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="rowsPerStrip" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of rows per strip. This is the number of rows in the image of one strip when an image is divided into strips. With JPEG compressed data this designation is not needed and is omitted.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="stripByteCounts" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The total number of bytes in each strip. With JPEG compressed data this designation is not needed and is omitted.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="xResolution" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of pixels per ResolutionUnit in the ImageWidth direction. When the image resolution is unknown, 72 [dpi] is designated.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="yResolution" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of pixels per ResolutionUnit in the ImageLength direction. The same value as XResolution is designated.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="planarConfiguration" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Indicates whether pixel components are recorded in chunky or planar format. In JPEG compressed files a JPEG marker is used instead of this tag. If this field does not exist, the TIFF default of 1 (chunky) is assumed.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="resolutionUnit" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>YResolution. The same unit is used for both XResolution and YResolution. If the image resolution in unknown, 2 (inches) is designated.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="transferFunction" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>A transfer function for the image, described in tabular style. Normally this tag is not necessary, since color space is specified in the color space information tag (ColorSpace).
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="software" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>The name and version of the software or firmware of the camera or image input device used to generate the image.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="dateTime" type="fi1:DateTimeType">
		<xsd:annotation>
			<xsd:documentation>The date and time of image creation. In this standard it is the date and time the file was changed.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="artist" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Person who created the image
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="whitePoint" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The chromaticity of the white point of the image. Normally this tag is not necessary, since color space is specified in the color space information tag (ColorSpace).
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="primaryChromaticities" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The chromaticity of the three primary colors of the image. Normally this tag is not necessary, since color space is specified in the color space information tag (ColorSpace).
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="jpegInterchangeFormat" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>compressed thumbnail data. This is not used for primary image JPEG data.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="jpegInterchangeFormatLength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of bytes of JPEG compressed thumbnail data. This is not used for primary image JPEG data.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="yCbCrCoefficients" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The matrix coefficients for transformation from RGB to YCbCr image data.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="yCbCrSubSampling" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The sampling ratio of chrominance components in relation to the luminance component. In JPEG compressed data a JPEG marker is used instead of this tag.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="yCbCrPositioning" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The position of chrominance components in relation to the luminance component. This field is designated only for JPEG compressed data or uncompressed YCbCr data.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="referenceBlackWhite" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The reference black point value and reference white point value. The color space is declared in a color space information tag, with the default being the value that gives the optimal image characteristics Interoperability these conditions.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="copyright" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Copyright information. In this standard the tag is used to indicate both the photographer and editor copyrights. It is the copyright notice of the person or organization claiming rights to the image.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="exposureTime" type="fi1:TimeType"/>
	<xsd:element name="fNumber" type="fi1:CodeType"/>
	<xsd:element name="exposureProgram" type="fi1:CodeType"/>
	<xsd:element name="spectralSensitivity" type="fi1:TextType"/>
	<xsd:element name="isoSpeedRatings" type="fi1:MeasureType"/>
	<xsd:element name="oecf" type="fi1:MeasureType"/>
	<xsd:element name="exifVersion" type="fi1:IdentifierType"/>
	<xsd:element name="dateTimeOriginal" type="fi1:DateTimeType"/>
	<xsd:element name="dateTimeDigitized" type="fi1:DateTimeType"/>
	<xsd:element name="componentsConfiguration" type="fi1:CodeType"/>
	<xsd:element name="compressedBitsPerPixel" type="fi1:MeasureType"/>
	<xsd:element name="shutterSpeedValue" type="fi1:MeasureType"/>
	<xsd:element name="apertureValue" type="fi1:CodeType"/>
	<xsd:element name="brightnessValue" type="fi1:MeasureType"/>
	<xsd:element name="exposureBiasValue" type="fi1:MeasureType"/>
	<xsd:element name="maxApertureValue" type="fi1:CodeType"/>
	<xsd:element name="subjectDistance" type="fi1:MeasureType"/>
	<xsd:element name="meteringMode" type="fi1:CodeType"/>
	<xsd:element name="lightSource" type="fi1:CodeType"/>
	<xsd:element name="flash" type="fi1:CodeType"/>
	<xsd:element name="focalLength" type="fi1:MeasureType"/>
	<xsd:element name="subjectArea" type="fi1:CodeType"/>
	<xsd:element name="makerNote" type="fi1:TextType"/>
	<xsd:element name="userComment" type="fi1:TextType"/>
	<xsd:element name="subSecTime" type="fi1:DateTimeType"/>
	<xsd:element name="subSecTimeOriginal" type="fi1:DateTimeType"/>
	<xsd:element name="subSecTimeDigitized" type="fi1:DateTimeType"/>
	<xsd:element name="flashpixVersion" type="fi1:IdentifierType"/>
	<xsd:element name="colorSpace" type="fi1:CodeType"/>
	<xsd:element name="pixelXDimension" type="fi1:MeasureType"/>
	<xsd:element name="pixelYDimension" type="fi1:MeasureType"/>
	<xsd:element name="relatedSoundFile" type="fi1:TextType"/>
	<xsd:element name="flashEnergy" type="fi1:MeasureType"/>
	<xsd:element name="spatialFrequencyResponse" type="fi1:MeasureType"/>
	<xsd:element name="focalPlaneXResolution" type="fi1:MeasureType"/>
	<xsd:element name="focalPlaneYResolution" type="fi1:MeasureType"/>
	<xsd:element name="focalPlaneResolutionUnit" type="fi1:CodeType"/>
	<xsd:element name="subjectLocation" type="fi1:MeasureType"/>
	<xsd:element name="exposureIndex" type="fi1:MeasureType"/>
	<xsd:element name="sensingMethod" type="fi1:CodeType"/>
	<xsd:element name="fileSource" type="fi1:CodeType"/>
	<xsd:element name="sceneType" type="fi1:CodeType"/>
	<xsd:element name="cfaPattern" type="fi1:MeasureType"/>
	<xsd:element name="customRendered" type="fi1:CodeType"/>
	<xsd:element name="exposureMode" type="fi1:CodeType"/>
	<xsd:element name="whiteBalance" type="fi1:CodeType"/>
	<xsd:element name="digitalZoomRatio" type="fi1:MeasureType"/>
	<xsd:element name="focalLengthIn35mmFilm" type="fi1:MeasureType"/>
	<xsd:element name="sceneCaptureType" type="fi1:CodeType"/>
	<xsd:element name="gainControl" type="fi1:CodeType"/>
	<xsd:element name="contrast" type="fi1:CodeType"/>
	<xsd:element name="saturation" type="fi1:CodeType"/>
	<xsd:element name="sharpness" type="fi1:CodeType"/>
	<xsd:element name="deviceSettingDescription" type="fi1:TextType"/>
	<xsd:element name="subjectDistanceRange" type="fi1:CodeType"/>
	<xsd:element name="imageUniqueID" type="fi1:IdentifierType"/>
	<xsd:element name="gpsVersionID" type="fi1:IdentifierType"/>
	<xsd:element name="gpsLatitudeRef" type="fi1:CodeType"/>
	<xsd:element name="gpsLongitudeRef" type="fi1:CodeType"/>
	<xsd:element name="gpsAltitudeRef" type="fi1:MeasureType"/>
	<xsd:element name="gpsTimeStamp" type="fi1:DateTimeType"/>
	<xsd:element name="gpsSatellites" type="fi1:TextType"/>
	<xsd:element name="gpsStatus" type="fi1:CodeType"/>
	<xsd:element name="gpsMeasureMode" type="fi1:CodeType"/>
	<xsd:element name="gpsDOP" type="fi1:MeasureType"/>
	<xsd:element name="gpsSpeedRef" type="fi1:CodeType"/>
	<xsd:element name="gpsSpeed" type="fi1:MeasureType"/>
	<xsd:element name="gpsTrackRef" type="fi1:CodeType"/>
	<xsd:element name="gpsTrack" type="fi1:MeasureType"/>
	<xsd:element name="gpsImgDirectionRef" type="fi1:CodeType"/>
	<xsd:element name="gpsImgDirection" type="fi1:MeasureType"/>
	<xsd:element name="gpsMapDatum" type="fi1:CodeType"/>
	<xsd:element name="gpsDestLatitudeRef" type="fi1:CodeType"/>
	<xsd:element name="gpsDestLongitudeRef" type="fi1:CodeType"/>
	<xsd:element name="gpsDestBearingRef" type="fi1:CodeType"/>
	<xsd:element name="gpsDestBearing" type="fi1:MeasureType"/>
	<xsd:element name="gpsDestDistanceRef" type="fi1:CodeType"/>
	<xsd:element name="gpsDestDistance" type="fi1:MeasureType"/>
	<xsd:element name="gpsProcessingMethod" type="fi1:TextType"/>
	<xsd:element name="gpsAreaInformation" type="fi1:TextType"/>
	<xsd:element name="gpsDateStamp" type="fi1:DateTimeType"/>
	<xsd:element name="gpsDifferential" type="fi1:CodeType"/>
	<xsd:element name="InteroperabilityIndex" type="fi1:CodeType"/>
	<xsd:element name="AliasLayerMetadata" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Alias Sketchbook Pro layer usage description. When used in composite image IFDs, the ASCII string value contains the fields, in order; LayerCount, CurrentLayer, BackgroundColor, ReducedImageCount. The remaining fields are reserved and must be 0. 
When this tag is used on individual layer IFDs, the ASCII string value contains the fields, in order: LayerOpacity, LayerFillColor, LayerVisible, LayerLocked, LayerNameImagePresent, VisibilityChannelCount, MaskLayerCount, Reserved1, Reserved2, Reserved3. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AnalogBalance" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>AnalogBalance defines the gain, either analog (recommended) or digital (not recommended) that has been applied the stored raw values. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AntiAliasStrength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>AntiAliasStrength provides a hint to the DNG reader about how strong the camera's anti-alias filter is. A value of 0.0 means no anti-alias filter (i.e., the camera is prone to aliasing artifacts with some subjects), while a value of 1.0 means a strong anti-alias filter (i.e., the camera almost never has aliasing artifacts). 
Note that this tag overlaps in functionality with the BaselineSharpness tag. The primary difference is the AntiAliasStrength tag is used as a hint to the de-mosaic algorithm, while the BaselineSharpness tag is used as a hint to a sharpening algorithm applied later in the processing pipeline. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AsShotNeutral" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Camera models vary in the trade-off they make between highlight headroom and shadow noise. Some leave a significant amount of highlight headroom during a normal exposure. This allows significant negative exposure compensation to be applied during raw conversion, but also means normal exposures will contain more shadow noise. Other models leave less headroom during normal exposures. This allows for less negative exposure compensation, but results in lower shadow noise for normal exposures. 
Because of these differences, a raw converter needs to vary the zero point of its exposure compensation control from model to model. BaselineExposure specifies by how much (in EV units) to move the zero point. Positive values result in brighter default results, while negative values result in darker default results. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="AsShotWhiteXY" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>AsShotWhiteXY specifies the selected white balance at time of capture, encoded as x-y chromaticity coordinates. The inclusion of this tag precludes the inclusion of the AsShotNeutral tag. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BadFaxLines" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-F standard, denotes the number of 'bad' scan lines encountered by the facsimile device. A 'bad' scanline is defined as a scanline that, when decoded, comprises an incorrect number of pixels. Note that this is an absolute value, a percentage of bad scanlines can be calculated by bringing ImageLength into the equation. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BaselineExposure" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Camera models vary in the trade-off they make between highlight headroom and shadow noise. Some leave a significant amount of highlight headroom during a normal exposure. This allows significant negative exposure compensation to be applied during raw conversion, but also means normal exposures will contain more shadow noise. Other models leave less headroom during normal exposures. This allows for less negative exposure compensation, but results in lower shadow noise for normal exposures. 
Because of these differences, a raw converter needs to vary the zero point of its exposure compensation control from model to model. BaselineExposure specifies by how much (in EV units) to move the zero point. Positive values result in brighter default results, while negative values result in darker default results. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BaselineNoise" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>BaselineNoise specifies the relative noise level of the camera model at a baseline ISO value of 100, compared to a reference camera model. 
Since noise levels tend to vary approximately with the square root of the ISO value, a raw converter can use this value, combined with the current ISO, to estimate the relative noise level of the current image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BaselineSharpness" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>BaselineSharpness specifies the relative amount of sharpening required for this camera model, compared to a reference camera model. Camera models vary in the strengths of their anti-aliasing filters. Cameras with weak or no filters require less sharpening than cameras with strong anti-aliasing filters. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BayerGreenSplit" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>BayerGreenSplit only applies to CFA images using a Bayer pattern filter array. This tag specifies, in arbitrary units, how closely the values of the green pixels in the blue/green rows track the values of the green pixels in the red/green rows. 
A value of zero means the two kinds of green pixels track closely, while a non-zero value means they sometimes diverge. The useful range for this tag is from 0 (no divergence) to about 5000 (quite large divergence). </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BestQualityScale" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For some cameras, the best possible image quality is not achieved by preserving the total pixel count during conversion. For example, Fujifilm SuperCCD images have maximum detail when their total pixel count is doubled. 
This tag specifies the amount by which the values of the DefaultScale tag need to be multiplied to achieve the best quality image size. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BlackLevel" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>This tag specifies the zero light (a.k.a. thermal black or black current) encoding level, as a repeating pattern. The values are stored in row-column-sample scan order.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BlackLevelDeltaH" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>If the zero light encoding level is a function of the image column, BlackLevelDeltaH specifies the difference between the zero light encoding level for each column and the baseline zero light encoding level. 
If SamplesPerPixel is not equal to one, this single table applies to all the samples for each pixel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BlackLevelDeltaV" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>If the zero light encoding level is a function of the image row, this tag specifies the difference between the zero light encoding level for each row and the baseline zero light encoding level. 
If SamplesPerPixel is not equal to one, this single table applies to all the samples for each pixel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="BlackLevelRepeatDim" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>This tag specifies repeat pattern size for the BlackLevel tag. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CalibrationIlluminant" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The illuminant used for the first set of color calibration tags (ColorMatrix1, CameraCalibration1, ReductionMatrix1). The legal values for this tag are the same as the legal values for the LightSource EXIF tag. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CameraCalibration" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>CameraClalibration defines a calibration matrix that transforms reference camera native space values to individual camera native space values under the first calibration illuminant. The matrix is stored in row scan order. 
This matrix is stored separately from the matrix specified by the ColorMatrix tag to allow raw converters to swap in replacement color matrices based on UniqueCameraModel tag, while still taking advantage of any per-individual camera calibration performed by the camera manufacturer. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CameraSerialNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>CameraSerialNumber contains the serial number of the camera or camera body that captured the image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CellLength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The length of the dithering or halftoning matrix used to create a dithered or halftoned bilevel file. 
This field should only be present if Threshholding = 2 </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CellWidth" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The width of the dithering or halftoning matrix used to create a dithered or halftoned bilevel file.
This field should only be present if Threshholding = 2</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CFALayout" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>CFALayout describes the spatial layout of the CFA. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CFAPlaneColor" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>CFAPlaneColor provides a mapping between the values in the CFAPattern tag and the plane numbers in LinearRaw space. This is a required tag for non-RGB CFA images.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ChromaBlurRadius" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>ChromaBlurRadius provides a hint to the DNG reader about how much chroma blur should be applied to the image. If this tag is omitted, the reader will use its default amount of chroma blurring. 
Normally this tag is only included for non-CFA images, since the amount of chroma blur required for mosaic images is highly dependent on the de-mosaic algorithm, in which case the DNG reader's default value is likely optimized for its particular de-mosaic algorithm.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CleanFaxData" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-F standard, indicates if 'bad' lines encountered during reception are stored in the data, or if 'bad' lines have been replaced by the receiver.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ClipPath" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Mirrors the essentials of PostScript's path creation functionality.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="CodingMethods" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard, indicates which coding methods are used in the file.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ColorMap" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>A color map for palette color images. This field defines a Red-Green-Blue color map (often called a lookup table) for palette-color images. In a palette-color image, a pixel value is used to index into an RGB lookup table. For example, a palette-color pixel having a value of 0 would be displayed according to the 0th Red, Green, Blue triplet. 
In a TIFF ColorMap, all the Red values come first, followed by the Green values, then the Blue values. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ColorMatrix" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>ColorMatrix defines a transformation matrix that converts XYZ values to reference camera native color space values, under the first calibration illuminant. The matrix values are stored in row scan order.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ConsecutiveBadFaxLines" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-F standard, denotes the maximum number of consecutive 'bad' scanlines received.
The BadFaxLines and ImageLength data indicate only the quantity of bad lines. The ConsecutiveBadFaxLines field is an indicator of the distribution of bad lines and may therefore be a better general indicator of perceived image quality. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Decode" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-F and TIFF-FX standards, holds information about the ITULAB (PhotometricInterpretation = 10) encoding.
In general, the values are taken in pairs and specify the minimum and maximum output value for each color component. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DefaultCropOrigin" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Raw images often store extra pixels around the edges of the final image. These extra pixels help prevent interpolation artifacts near the edges of the final image. 
DefaultCropOrigin specifies the origin of the final image area, in raw image coordinates (i.e., before the DefaultScale has been applied).</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DefaultCropSize" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Raw images often store extra pixels around the edges of the final image. These extra pixels help prevent interpolation artifacts near the edges of the final image. 
DefaultCropSize specifies the size of the final image area, in raw image coordinates (i.e., before the DefaultScale has been applied). </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DefaultImageColor" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Defined in the Mixed Raster Content part of RFC 2301, is the default color needed in areas where no image is available.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DefaultScale" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>DefaultScale is required for cameras with non-square pixels. It specifies the default scale factors for each direction to convert the image to square pixels. Typically these factors are selected to approximately preserve total pixel count. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DNGBackwardVersion" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>This tag specifies the oldest version of the Digital Negative specification for which a file is compatible. Readers should not attempt to read a file if this tag specifies a version number that is higher than the version number of the specification the reader was based on. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DNGPrivateData" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>DNGPrivateData provides a way for camera manufacturers to store private data in the DNG file for use by their own raw converters, and to have that data preserved by programs that edit DNG files. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DNGVersion" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>This tag encodes the DNG four-tier version number. For example, the version DNG version number 1.0.0.0 is encoded as the four byte sequence 1, 0, 0, 0. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DocumentName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of the document from which this image was scanned.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="DotRange" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The component values that correspond to a 0% dot and 100% dot. The component values that correspond to a 0% dot and 100% dot. 
DotRange[0] corresponds to a 0% dot, and DotRange[1] corresponds to a 100% dot. 
It is possible, though strongly discouraged, to have a pair of DotRange values per component. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ExifIFD" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>A pointer to the Exif IFD. Exif IFD is a set of tags for recording Exif-specific attribute information. It is pointed to by the offset from the TIFF header (Value Offset) indicated by an Exif private tag value. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ExtraSamples" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Description of extra components. Specifies that each pixel has N extra components whose interpretation is defined by one of the values listed below. When this field is used, the SamplesPerPixel field has a value greater than the PhotometricInterpretation field suggests. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FaxProfile" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard, denotes the 'profile' that applies to this file. 'Profile' is defined by the TIFF-FX standard to be a subset of the full set of permitted fields and field values of TIFF for facsimile. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FillOrder" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The logical order of bits within a byte.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FreeByteCounts" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For each string of contiguous unused bytes in a TIFF file, the number of bytes in the string.
Not recommended for general interchange. 
This tag is mostly abandonded, it was an attempt at memory management inside TIFF files that did not succeed. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="FreeOffsets" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>For each string of contiguous unused bytes in a TIFF file, the byte offset of the string.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GdalNodata" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used by the GDAL library, contains an ASCII encoded nodata or background pixel value. In the geospatial image processing field especially (and in other fields) it is common to use a special pixel value to mark geospatial areas for which no information is available. This is often called a "nodata" or "background" value. Applications often treat these pixels as transparent and they are often not included in spatial statistics for the image. Non-geospatial applications might still use the nodata value to track a special value that should be treated as transparent since currently TIFF palettes don't include an alpha value.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GeoAsciiParamsTag" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Used in interchangeable GeoTIFF files. This tag is used to store all of the ASCII valued GeoKeys, referenced by the GeoKeyDirectoryTag. Since keys use offsets into tags, any special comments may be placed at the beginning of this tag. For the most part, the only keys that are ASCII valued are "Citation" keys, giving documentation and references for obscure projections, datums, etc. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GeoDoubleParamsTag" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Used in interchangeable GeoTIFF files. This tag is used to store all of the DOUBLE valued GeoKeys, referenced by the GeoKeyDirectoryTag. The meaning of any value of this double array is determined from the GeoKeyDirectoryTag reference pointing to it. FLOAT values should first be converted to DOUBLE and stored here. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GeoKeyDirectoryTag" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Used in interchangeable GeoTIFF files. This tag is also know as 'ProjectionInfoTag' and 'CoordSystemInfoTag' 
This tag may be used to store the GeoKey Directory, which defines and references the "GeoKeys".</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GlobalParametersIFD" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard to point to an IFD containing tags that are globally applicable to the complete TIFF file. Each field in the GlobalParametersIFD is a TIFF field that is legal in any IFD. Required baseline fields should not be located in the GlobalParametersIFD, but should be in each image IFD. If a conflict exists between fields in the GlobalParametersIFD and in the image IFDs, then the data in the image IFD shall prevail. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GpsIFD" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>A pointer to the Exif-related GPS Info IFD. GPS IFD is a set of tags for recording GPS information. It is pointed to by the offset from the TIFF header (Value Offset) indicated by a GPS private tag value. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GrayResponseCurve" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For grayscale data, the optical density of each possible pixel value. The 0th value of GrayResponseCurve corresponds to the optical density of a pixel having a value of 0, and so on.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="GrayResponseUnit" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The precision of the information contained in the GrayResponseCurve.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HalftoneHints" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Conveys to the halftone function the range of gray levels within a colorimetrically-specified image that should retain tonal detail.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HostComputer" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The computer and/or operating system in use at the time of image creation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HylaFAXFaxRecvParams" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used by HylaFAX. This tag holds a single LONG value which is bit-encoded with information regarding the fax session parameters (T.30 Table 2) for the received facsimile. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HylaFAXFaxRecvTime" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Used by HylaFAX. This tag contains the number of seconds it took for the fax to be received. This tag is always set on all faxes received by HylaFAX. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="HylaFAXFaxSubAddress" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used by HylaFAX. This tag holds an ASCII value containing the subaddress information provided by the sender during the initial fax protocol. This tag is only set on faxes when it is communicated by the sender, and that is infrequent. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ICCProfile" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>ICC profile data.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ImageLayer" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Defined in the Mixed Raster Content part of RFC 2301, used to denote the particular function of this Image in the mixed raster scheme.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ImageSourceData" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used by Adobe Photoshop.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Indexed" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Aims to broaden the support for indexed images to include support for any color space. Indexed images are images where the pixels do not represent color values, but rather an index (usually 8-bit) into a separate color table, the ColorMap. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="INGRFlagRegisters" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Intergraph Application specific flags. Each of the 16 registers is a 32-bit integer.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="INGRPacketDataTag" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Intergraph Application specific storage. N shorts that make up at least one and perhaps more INGR packets. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InkNames" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>The name of each ink used in a separated image. These names are written as a list of concatenated, NUL-terminated ASCII strings. The number of strings must be equal to NumberOfInks. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="InkSet" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The set of inks used in a separated (PhotometricInterpretation=5) image.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="IPTC" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>IPTC (International Press Telecommunications Council) metadata.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="IrasBTransformationMatrix" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Originally part of Intergraph's GeoTIFF tags, but likely understood by IrasB only. The first 16 values are to be used to compute DESIGN FILE coordinates from raster coordinates according to the a matrix equation. The 17th value is a units code. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="JPEGTables" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Old-style JPEG compression field. TechNote2 invalidates this part of the specification.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LensInfo" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>LensInfo contains information about the lens that captured the image. If the minimum f-stops are unknown, they should be encoded as 0/0. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LinearizationTable" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>LinearizationTable describes a lookup table that maps stored values into linear values. This tag is typically used to increase compression ratios by storing the raw data in a non-linear, more visually uniform space with fewer total encoding levels. 
If SamplesPerPixel is not equal to one, this single table applies to all the samples for each pixel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LinearResponseLimit" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Some sensors have an unpredictable non-linearity in their response as they near the upper limit of their encoding range. This non-linearity results in color shifts in the highlight areas of the resulting image unless the raw converter compensates for this effect. 
LinearResponseLimit specifies the fraction of the encoding range above which the response may become significantly non-linear. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="LocalizedCameraModel" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Similar to the UniqueCameraModel field, except the name can be localized for different markets to match the localization of the camera name. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MaxSampleValue" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The maximum component value used. This field is not to be used to affect the visual appearance of an image when it is displayed or printed. Nor should this field affect the interpretation of any other field; it is used only for statistical purposes. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDColorTable" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used to specify the conversion from 16bit to 8bit in the Molecular Dynamics GEL file format.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDFileTag" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Specifies the pixel data format encoding in the Molecular Dynamics GEL file format.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDFileUnits" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Units for data in this file, as used in the Molecular Dynamics GEL file format.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDLabName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>Name of the lab that scanned this file, as used in the Molecular Dynamics GEL file format.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDPrepDate" type="fi1:DateType">
		<xsd:annotation>
			<xsd:documentation>Date the sample was prepared, as used in the Molecular Dynamics GEL file format. The format of this data is YY/MM/DD. 
Note that the word 'sample' as used here, refers to the scanned sample, not an image channel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDPrepTime" type="fi1:TimeType">
		<xsd:annotation>
			<xsd:documentation>Time the sample was prepared, as used in the Molecular Dynamics GEL file format. Format of this data is HH:MM using the 24-hour clock. 
Note that the word 'sample' as used here, refers to the scanned sample, not an image channel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDSampleInfo" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Information about the sample, as used in the Molecular Dynamics GEL file format. This information is entered by the person that scanned the file. 
Note that the word 'sample' as used here, refers to the scanned sample, not an image channel. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MDScalePixel" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Specifies a scale factor in the Molecular Dynamics GEL file format. The scale factor is to be applies to each pixel before presenting it to the user.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="MinSampleValue" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The minimum component value used. This field is not to be used to affect the visual appearance of an image when it is displayed or printed. Nor should this field affect the interpretation of any other field; it is used only for statistical purposes. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ModelPixelScaleTag" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>This tag is optionally provided for defining exact affine transformations between raster and model space. Baseline GeoTIFF files may use this tag or ModelTransformationTag, but shall never use both within the same TIFF image directory. 
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ModelTiepointTag" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>This tag is also known as 'GeoreferenceTag'. 
This tag stores raster->model tiepoint pairs in the order 
ModelTiepointTag = (...,I,J,K, X,Y,Z...) 
where (I,J,K) is the point at location (I,J) in raster space with pixel-value K, and (X,Y,Z) is a vector in model space. In most cases the model space is only two-dimensional, in which case both K and Z should be set to zero; this third dimension is provided in anticipation of future support for 3D digital elevation models and vertical coordinate systems. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ModelTransformationTag" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>This tag is optionally provided for defining exact affine transformations between raster and model space. Baseline GeoTIFF files may use this tag or ModelPixelScaleTag, but shall never use both within the same TIFF image directory. 
This tag may be used to specify the transformation matrix between the raster space (and its dependent pixel-value space) and the (possibly 3D) model space. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ModeNumber" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard, denotes the mode of the standard specified by the FaxProfile field. A value of 0 indicates Mode 1.0. The tag is used in Mixed Raster Content mode. 
The tag is described to be primarly used inside a GlobalParameters IFD, although the specification says that 'each field in the GlobalParametersIFD is a TIFF field that is legal in any IFD'. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NewSubfileType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A general indication of the kind of data contained in this subfile. NewSubfileType is mainly useful when there are multiple subfiles in a single TIFF file. 
This field is made up of a set of 32 flag bits. Unused bits are expected to be 0. Bit 0 is the low-order bit. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="NumberOfInks" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation>The number of inks. Usually equal to SamplesPerPixel, unless there are extra samples. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OceApplicationSelector" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used in the Oce scanning process. Identifies the application to process the TIFF file that results from scanning. 
Includes a trailing zero. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OceIdentificationNumber" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Used in the Oce scanning process. This is the user's answer to an optional question embedded in the Oce scanticket, and presented to that user before scanning. It can serve in further determination of the workflow. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OceImageLogicCharacteristics" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used in the Oce scanning process. This tag encodes the imageprocessing done by the Oce ImageLogic module in the scanner to ensure optimal quality for certain workflows. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OceScanjobDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used in the Oce scanning process. Identifies the scanticket used in the scanning process. 
Includes a trailing zero. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OPIProxy" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>OPIProxy gives information concerning whether this image is a low-resolution proxy of a high-resolution image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PageName" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>The name of the page from which this image was scanned.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PageNumber" type="fi1:NumericType">
		<xsd:annotation>
			<xsd:documentation>The page number of the page from which this image was scanned.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Photoshop" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Collection of Photoshop 'Image Resource Blocks'.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Predictor" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A mathematical operator that is applied to the image data before an encoding scheme is applied. The general idea is that subsequent pixels of an image ressemble each other. Thus, substracting the information from a pixel that is already contained in previous one, is likely to reduce its information density considerably, and aid subsequent compression. 
Theoretically, the predictor step is independent from the compression step, and thus can be combined with any compression scheme. It is, however, likely to be most usefull when combined with either LZW or Deflate compression. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ProfileType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard, denotes the type of data stored in this file or IFD. The tag is described to be primarly used inside a GlobalParameters IFD, although the specification says that 'each field in the GlobalParametersIFD is a TIFF field that is legal in any IFD'.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ReductionMatrix" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>ReductionMatrix defines a dimensionality reduction matrix for use as the first stage in converting color camera native space values to XYZ values, under the first calibration illuminant. This tag may only be used if ColorPlanes is greater than 3. The matrix is stored in row scan order. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SampleFormat" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>pecifies how to interpret each data sample in a pixel.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SMaxSampleValue" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Specifies the maximum sample value. The type should be the field type that best matches the sample data. 
Note that a value should be given for each data sample. That is, if the image has 3 SamplesPerPixel, 3 values must be specified. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SMinSampleValue" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Specifies the minimum sample value. The type should be the field type that best matches the sample data. 
Note that a value should be given for each data sample. That is, if the image has 3 SamplesPerPixel, 3 values must be specified. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StripRowCounts" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Defined in the Mixed Raster Content part of RFC 2301, used to replace RowsPerStrip for IFDs with variable-sized strips. This tag specifies the number of scanlines stored in a strip, per strip, since MRC allows each fax strip to store a different number of scanlines. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SubfileType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A general indication of the kind of data contained in this subfile.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="SubIFDs" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Offset to child IFDs. Each value is an offset (from the beginning of the TIFF file, as always) to a child IFD. Child images provide extra information for the parent image - such as a subsampled version of the parent image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="T4Options" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Options for Group 3 Fax compression</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="T6Options" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Options for Group 4 Fax compression</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TargetPrinter" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A description of the printing environment for which this separation is intended.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Threshholding" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>For black and white TIFF files that represent shades of gray, the technique used to convert from gray to black and white pixels.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TileByteCounts" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For each tile, the number of (compressed) bytes in that tile.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TileLength" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The tile length (height) in pixels. This is the number of rows in each tile.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TileOffsets" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>For each tile, the byte offset of that tile, as compressed and stored on disk. The offset is specified with respect to the beginning of the TIFF file. Note that this implies that each tile has a location independent of the locations of other tiles. 
Offsets are ordered left-to-right and top-to-bottom. For PlanarConfiguration = 2, the offsets for the first component plane are stored first, followed by all the offsets for the second component plane, and so on. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TileWidth" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The tile width in pixels. This is the number of columns in each tile.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="TransferRange" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Expands the range of the TransferFunction. The TransferRange field contains two values for each of three components that are an offset and a scaling, these values expand the TransferFunction range. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="UniqueCameraModel" type="fi1:NameType">
		<xsd:annotation>
			<xsd:documentation>UniqueCameraModel defines a unique, non-localized name for the camera model that created the image in the raw file. This name should include the manufacturer's name to avoid conflicts, and should not be localized, even if the camera name itself is localized for different markets </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="VersionYear" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>Used in the TIFF-FX standard, denotes the year of the standard specified by the FaxProfile field. The year is encoded as 4 characters, e.g. '1997'. The tag is used in lossy and lossless color modes. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="WangAnnotation" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Annotation data, as used in 'Imaging for Windows'.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="WhiteLevel" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>This tag specifies the fully saturated encoding level for the raw sample values. Saturation is caused either by the sensor itself becoming highly non-linear in response, or by the camera's analog to digital converter clipping. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="XClipPathUnits" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of units that span the width of the image, in terms of integer ClipPath coordinates. All horizontal ClipPath coordinates will be divided by this value in order to get a number that is (usually) between 0.0 and 1.0, where 0.0 represents the left side of the image and 1.0 represents the right side of the image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="XMP" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>XML packet containing XMP metadata. XMP is an extensible way to include metadata such as meaningful descriptions and titles, searchable keywords, and up-to-date author and copyright information.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="XPosition" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>X position of the image. The X offset in ResolutionUnits of the left side of the image, with respect to the left side of the page. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="YClipPathUnits" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>The number of units that span the height of the image, in terms of integer ClipPath coordinates. All vertical ClipPath coordinates will be divided by this value in order to get a number that is (usually) between 0.0 and 1.0, where 0.0 represents the top of the image and 1.0 represents the bottom of the image. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="YPosition" type="fi1:MeasureType">
		<xsd:annotation>
			<xsd:documentation>Y position of the image. The Y offset in ResolutionUnits of the top of the image, with respect to the top of the page. In the TIFF coordinate scheme, the positive Y direction is down, so that YPosition is always positive. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentTransactionID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>Unique identifier of the payment transaction.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentTransactionType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Type of payment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentDeviceType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>The type of device that makes the payment.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentDeviceID" type="fi1:IdentifierType">
		<xsd:annotation>
			<xsd:documentation>The unique identification of the device.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentDescription" type="fi1:TextType">
		<xsd:annotation>
			<xsd:documentation>The reason of the payment transaction.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="PaymentReference" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>A coded reason of the payment transaction.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="OrderType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Type of order</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
</xsd:schema>
