<?xml version="1.0" encoding="iso-8859-1"?>
<!-- 
Version 3 (2009-05-29)
Updated to AdsMLBookings 2.5.

Note: A schema location is provided in this sample, but must not be used in production messages.

MASTER SAMPLE OF A NEW AD ORDER for Newspapers or Magazines - Based on a typical North American magazine order - "AD-O" message
    
    A "master" sample includes almost every element that could be used in such an order, 
    even though the combination of elements is not completely realistic.
-->
<AdsMLBookings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.adsml.org/adsmlbookings/2.5 ../../Schemas/AdsMLBookings-2.5-Main-AS.xsd"
	xmlns:adsml-cv="http://www.adsml.org/controlledvocabularies/3.0"
	xmlns="http://www.adsml.org/adsmlbookings/2.5"
	xmlns:adsml="http://www.adsml.org/typelibrary/2.0"
	xmlns:adsml-ma="http://www.adsml.org/adsmlmaterials/2.5"
	xmlns:adsml-sd="http://www.adsml.org/adsmlstructureddescriptions/1.0"
	adsml:transmissionID="DDS.com:2006-06-01:1043T" adsml:systemsID="DDS-WebIO-v1.0"
	adsml:administrativeResponseRequired="true" adsml:sendCount="1" adsml:transmissionSequence="43"
	adsml:transmissionStatus="Production" adsml:transmissionDateTime="2006-06-01T09:15:00-05:00"
	adsml:firstTransmissionDateTime="2006-06-01T09:15:00-05:00" adsml:schemaVersion="2.5.0">
	<adsml:Header>
		<adsml:TransmissionFrom>
			<adsml:Identifier>
				<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
					>AssignedByBuyer</adsml:IDLabel>
				<adsml:IDValue>IDValueForSendingCompany (or a copy of their name if no formal ID is
					used)</adsml:IDValue>
			</adsml:Identifier>
			<adsml:Name>Sending Company Name</adsml:Name>
			<!-- Contact details for the company as a whole -->
			<adsml:PartyAddress>
				<adsml:CommunicationChannel.PhysicalAddress>
					<!-- Sender should EITHER populate the explicit City, State and Zip elements (preferred), 
						or format the entire address as repeated Street elements, 
						but DO NOT FORMAT THE ADDRESS *BOTH* WAYS or the recipient won't know how to display it -->
					<adsml:Street>Street address 1</adsml:Street>
					<adsml:Street>NEW YORK, NY 10011</adsml:Street>
					<!-- Alternative, preferred way of providing city, state and zip starts here -->
					<adsml:ZipPostalCode>10011</adsml:ZipPostalCode>
					<adsml:City>New York</adsml:City>
					<adsml:StateProvince>NY</adsml:StateProvince>
					<adsml:CountryName>USA</adsml:CountryName>
				</adsml:CommunicationChannel.PhysicalAddress>
				<!-- Main phone and fax lines for the company as a whole -->
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-633-0000</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Fax</adsml:Type>
					<adsml:PhoneNumber>212-633-0001</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Other>
					<adsml:Type>
						<adsml:CodeValue>URL</adsml:CodeValue>
					</adsml:Type>
					<adsml:Specification>
						<adsml:Value>WWW.ADVANTAGE.COM</adsml:Value>
					</adsml:Specification>
				</adsml:CommunicationChannel.Other>
			</adsml:PartyAddress>
			<!-- Contacts within the company start here -->
			<adsml:Contact>
				<!-- The person to contact if there is a transmission problem; the contact structure and all its components are optional -->
				<adsml:Role>Optional role or title goes here</adsml:Role>
				<adsml:Name>M. STEVENS</adsml:Name>
				<!-- Direct line -->
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-633-1234</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.EMail>
					<adsml:EMailAddress>MSTEVENS@ADVANTAGE.COM</adsml:EMailAddress>
				</adsml:CommunicationChannel.EMail>
			</adsml:Contact>
		</adsml:TransmissionFrom>
		<adsml:TransmissionTo>
			<adsml:Identifier>
				<!-- See the comments about party IDs in TransmissionFrom above -->
				<adsml:IDLabel>EbizRegistry</adsml:IDLabel>
				<adsml:IDValue>Message recipient company ID code</adsml:IDValue>
			</adsml:Identifier>
			<adsml:Name>Message recipient company name</adsml:Name>
		</adsml:TransmissionTo>
	</adsml:Header>
	<!-- Since this is a brand new order we use the AdOrder element; change messages use the almost identical AdOrderChange element -->
	<AdOrder messageCode="AD-O" adsml:messageID="dds.com:2006-06-16:1043M"
		adsml:messageClass="BusinessTransaction" adsml:messageAssembledTime="2006-07-06T00:00:00">
		<!-- The buyer creates the booking identifier. There are two versions: the AdsML "QID" and the buyer's internal number. 
			The QID format adds a prefix to make it globally unique. This value remains unchanged through all revisions so it should not contain a
			revision number -->
		<BookingIdentifier>dds.com:2006-06-01:M-05THC0015</BookingIdentifier>
		<AuxiliaryBookingReferences>
			<!-- The human-readable version of the order ID as the sender would like it to appear -->
			<adsml:BuyersReference>M-05THC0015-REV000</adsml:BuyersReference>
		</AuxiliaryBookingReferences>
		<!-- In an initial order the business message date is the same as the booking date -->
		<adsml:BusinessMessageDate>2006-07-06</adsml:BusinessMessageDate>
		<BookingDate>2006-07-06</BookingDate>
		<!-- Buyer provides contact information for himself. This may be the same as the data in the TransmissionFrom structure -->
		<adsml:BookingParty>
			<adsml:Identifier>
				<!-- The ID Label identifies the party that assigned the ID value being used; could be DUNS or EbizRegistry -->
				<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
					>AssignedByBuyer</adsml:IDLabel>
				<adsml:IDValue>BuyersFormalID</adsml:IDValue>
			</adsml:Identifier>
			<adsml:Name>Buyers Company Name</adsml:Name>
			<adsml:PartyAddress>
				<adsml:CommunicationChannel.PhysicalAddress>
					<adsml:Street>Street address 1</adsml:Street>
					<!-- repeatable -->
					<adsml:Street>NEW YORK, NY 10011</adsml:Street>
					<adsml:ZipPostalCode>10011</adsml:ZipPostalCode>
					<!-- optional -->
					<adsml:CountryName>USA</adsml:CountryName>
					<!-- optional -->
				</adsml:CommunicationChannel.PhysicalAddress>
				<!-- Main phone and fax for the company as a whole -->
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-633-0000</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Fax</adsml:Type>
					<adsml:PhoneNumber>212-633-0001</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Other>
					<adsml:Type>
						<adsml:CodeValue>URL</adsml:CodeValue>
					</adsml:Type>
					<adsml:Specification>
						<adsml:Value>WWW.ADVANTAGE.COM</adsml:Value>
					</adsml:Specification>
				</adsml:CommunicationChannel.Other>
			</adsml:PartyAddress>
			<adsml:Contact>
				<!-- The person to contact if there is a  problem with the order; the contact structure and all its components are optional -->
				<adsml:Role xsi:type="adsml-cv:AdsMLContactRoleCV">MediaBuyer</adsml:Role>
				<adsml:Name>M. STEVENS</adsml:Name>
				<!-- Direct line  -->
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-633-4321</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.EMail>
					<adsml:EMailAddress>MSTEVENS@ADVANTAGE.COM</adsml:EMailAddress>
				</adsml:CommunicationChannel.EMail>
			</adsml:Contact>
			<adsml:Contact>
				<!-- The person at the agency who approved this IO -->
				<adsml:Role xsi:type="adsml-cv:AdsMLContactRoleCV">AuthorizedSignature</adsml:Role>
				<adsml:Name>J. DONAHUE</adsml:Name>
			</adsml:Contact>
		</adsml:BookingParty>
		<!-- Buyer identifies the seller's main address and optional contact people. -->
		<adsml:SellingParty>
			<adsml:Identifier>
				<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
					>AssignedByBuyer</adsml:IDLabel>
				<adsml:IDValue>IDValueForSellingCompany</adsml:IDValue>
			</adsml:Identifier>
			<adsml:Name>Advantage</adsml:Name>
			<!-- Seller's address - optional -->
			<adsml:PartyAddress>
				<adsml:CommunicationChannel.PhysicalAddress>
					<adsml:Street>1275 BROADWAY</adsml:Street>
					<adsml:Street>NY, NY 10015</adsml:Street>
				</adsml:CommunicationChannel.PhysicalAddress>
			</adsml:PartyAddress>
			<!-- Contact people on the seller's side - all of this is optional  -->
			<adsml:Contact>
				<adsml:Role xsi:type="adsml-cv:AdsMLContactRoleCV"
					>AccountSalesRepresentative</adsml:Role>
				<!-- The main pub contact person -->
				<adsml:Name>R. SHANKEN</adsml:Name>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-555-1212</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Fax</adsml:Type>
					<adsml:PhoneNumber>212-555-1213</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.PhysicalAddress>
					<adsml:Street>1275 BROADWAY</adsml:Street>
					<adsml:Street>NY, NY 10015</adsml:Street>
				</adsml:CommunicationChannel.PhysicalAddress>
			</adsml:Contact>
			<adsml:Contact>
				<adsml:Role xsi:type="adsml-cv:AdsMLContactRoleCV">AdTrafficManager</adsml:Role>
				<adsml:Name>M. STEVENS</adsml:Name>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Voice</adsml:Type>
					<adsml:PhoneNumber>212-633-0000</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.Phone>
					<adsml:Type>Fax</adsml:Type>
					<adsml:PhoneNumber>212-633-0001</adsml:PhoneNumber>
				</adsml:CommunicationChannel.Phone>
				<adsml:CommunicationChannel.EMail>
					<adsml:EMailAddress>MSTEVENS@ADVANTAGE.COM</adsml:EMailAddress>
				</adsml:CommunicationChannel.EMail>
				<adsml:CommunicationChannel.PhysicalAddress>
					<adsml:Street>115 WEST 18TH STREET</adsml:Street>
					<adsml:Street>NEW YORK, NY 10011</adsml:Street>
				</adsml:CommunicationChannel.PhysicalAddress>
			</adsml:Contact>
		</adsml:SellingParty>
		<!-- Any legalistic boilerplate which applies to the entire booking goes here -->
		<TermsAndConditions>
			<adsml:DisclaimerText>THIS ORDER IS BOOKED BY DATATECH ANY CHANGES TO THE ABOVE ORDER MUST
				BE APPROVED IN WRITING. ALL INVOICES SHOULD BE ACCOMPANIED BY CORRESPONDING TEARSHEETS.
				PLEASE SIGN AND FAX BACK AS CONFIRMATION PAYMENT TERMS: THE AGENCY SHALL MAKE SUCH
				PAYMENT AT THE OFFICE OF THE PUBLISHER OR THE PUBLISHER'S AUTHORIZED REPRESENTATIVE
				WITHIN FORTY-FIVE DAYS FORM DATE OF PUBLISHER'S BILL. THE PUBLISHER AGREES TO RENDER
				BILLS TO DATATECH SOFTWARE. AGENCY IS NO LIABLE FOR PAYMENT OF ANY PUBLISHER'S BILLS
				THAT HAVE NOT BEEN RECEIVED 90 DAYS FROM THE ISSUE DATE UNLESS OTHERWISE STIPULATED AND
				AGREED IN WRITING BY THE AGENCY.</adsml:DisclaimerText>			
		</TermsAndConditions>
		<!-- Currency code is optional. Including it clarifies that the default currency for this order is USD -->
		<adsml:DocumentCurrencyCode xsi:type="adsml-cv:ISOCurrencyCodeCV"
			>USD</adsml:DocumentCurrencyCode>
		<!-- Total booking price goes here if present -->
		<TotalBookingPrice>
			<adsml:TotalPrice>
				<adsml:Amount>179327.20</adsml:Amount>
			</adsml:TotalPrice>
			<!-- Optional stack of price components relating to the entire order. If a component is present, it must be named -->
			<adsml:PriceComponent adsml:sequenceNo="1">
				<!-- sequence number is mandatory but you can generate price components in any sequence you want -->
				<adsml:PriceComponentName>
					<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
						>GrossPrice</adsml:CodeValue>
				</adsml:PriceComponentName>
				<adsml:Amount>6000.00</adsml:Amount>
				<adsml:DescriptionLine>Gross Price</adsml:DescriptionLine>
				<!-- You can put an optional Calculation Specification here if you want to show the unit price -->
			</adsml:PriceComponent>
			<!-- Color or production charges or other premium charge(s) would normally go after the gross price -->
			<adsml:PriceComponent adsml:sequenceNo="2">
				<adsml:PriceComponentName>
					<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
						>ColorCharge</adsml:CodeValue>
				</adsml:PriceComponentName>
				<adsml:Amount>0</adsml:Amount>
				<adsml:DescriptionLine>Color Charge</adsml:DescriptionLine>
			</adsml:PriceComponent>
		</TotalBookingPrice>
		<!-- Optional information about the Paying party and how they will make payment. If omitted, the buyer is assumed to be the payer.
	    		It is also possible to put PayerInformation details inside each Placement, which allows for different payers per placement, but this is relatively rare. -->
		<PayerInformation>
			<adsml:PayerParty>
				<adsml:Identifier>
					<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
						>AssignedByBuyer</adsml:IDLabel>
					<adsml:IDValue>PayersFormalID</adsml:IDValue>
				</adsml:Identifier>
				<adsml:Name>Paying party name</adsml:Name>
				<adsml:PartyAddress>
					<!-- Paying party's address can go here  -->
				</adsml:PartyAddress>
			</adsml:PayerParty>
			<!-- Optionally, the payment mechanism can be defined.  -->
			<Payment>
				<Mechanism>
					<!-- This structure says to send the main invoice to the payer, and also a copy to the buyer -->
					<Invoice sendToPayer="true">
						<SendCopyTo>
							<adsml:Identifier>
								<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
									>AssignedByBuyer</adsml:IDLabel>
								<adsml:IDValue>BuyersFormalID</adsml:IDValue>
							</adsml:Identifier>
							<adsml:Name>Buyers Company Name</adsml:Name>
						</SendCopyTo>
					</Invoice>
				</Mechanism>
			</Payment>
		</PayerInformation>
		<!-- ====== The first placement on the order. ====== -->
		<Placement.NewspaperMagazine>
			<!-- Placement Identifier is usually the Booking ID plus a suffix, but the sending system can use any suitable algorithm  -->
			<PlacementIdentifier>dds.com:2006-06-01:M-05THC0015-REV000.219</PlacementIdentifier>
			<AuxiliaryBookingReferences>
				<adsml:BuyersReference>219</adsml:BuyersReference>
				<!-- Buyer's human readable ID for this placement. 
						Can be a repeat of the entire string (M-05THC0015-REV000.219) or just the serial number at the end (219)-->
				<!-- The buyer can provide as many "other references" to the placement as they want -->
				<!-- Each of these should have a value and a label to explain what it is -->
				<!-- But IDs of the artwork materials don't go here, their own section below -->
				<adsml:OtherReference>
					<adsml:Value>THC-CHB-1</adsml:Value>
					<adsml:Label>Copy Number</adsml:Label>
				</adsml:OtherReference>
				<adsml:OtherReference>
					<adsml:Value>1</adsml:Value>
					<adsml:Label>AdCode</adsml:Label>
				</adsml:OtherReference>
				<adsml:OtherReference>
					<adsml:Value>12345</adsml:Value>
					<adsml:Label>ReferenceNo</adsml:Label>
				</adsml:OtherReference>
			</AuxiliaryBookingReferences>
			<IsStandAlone>true</IsStandAlone>
			<!-- The buyer declares the ad type. -->
			<adsml:AdType>
				<adsml:CodeValue xsi:type="adsml-cv:AdsMLAdTypeCV">Magazine</adsml:CodeValue>
			</adsml:AdType>
			<!-- The buyer identifies the advertiser and the product or brand. -->
			<AdvertiserBrand>
				<adsml:Advertiser>
					<adsml:Identifier>
						<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
							>AssignedByBuyer</adsml:IDLabel>
						<adsml:IDValue>THC</adsml:IDValue>
					</adsml:Identifier>
					<adsml:Name>The Hamburger Co.</adsml:Name>
				</adsml:Advertiser>
				<Brand>
					<adsml:Name>Cheeseburger</adsml:Name>
					<Code>
						<adsml:CodeValue>CHB</adsml:CodeValue>
					</Code>
				</Brand>
			</AdvertiserBrand>
			<!-- Name of the Estimate/Campaign including the Campaign Code -->
			<adsml:Campaign>
				<adsml:CodeValue>10</adsml:CodeValue>
				<adsml:Description>YEARLY ESTIMATE 2006</adsml:Description>
			</adsml:Campaign>
			<adsml:Contract>
				<adsml:ContractReference>12</adsml:ContractReference>
				<adsml:ContractType>
					<adsml:CodeValue xsi:type="adsml-cv:AdsMLContractTypeCV">Flat</adsml:CodeValue>
				</adsml:ContractType>
				<adsml:ValidityPeriod>
					<adsml:StartDateTime>2006-01-01</adsml:StartDateTime>
					<adsml:EndDateTime>2006-12-31</adsml:EndDateTime>
				</adsml:ValidityPeriod>
			</adsml:Contract>
			<!-- If any guarantees have been agreed, they can be described here as either codes or text -->
			<Guarantees>
				<adsml:Code>
					<adsml:CodeValue xsi:type="adsml-cv:AdsMLGuaranteeCodeCV">RunAsBooked</adsml:CodeValue>
				</adsml:Code>
				<adsml:Text>Textual description of guarantees could go here...</adsml:Text>
			</Guarantees>
			<!-- The buyer provides details on the expected prices.-->
			<!-- Pricing information is OPTIONAL.  However, if pricing information is provided then the code lists should be controlled (i.e. use the AdsML lists as shown) to clearly
				indicate the nature of each price component  -->
			<PlacementPrice>
				<adsml:TotalPrice>
					<!-- This is the sum of the price components, which ideally should add up to the expected net
						price, but might be a partial value if the price components are partial. -->
					<!-- If putting a total price here would be irrelevant or misleading, use the xsi:nil attribute to omit it -->
					<adsml:Amount>6000.00</adsml:Amount>
					<adsml:DescriptionLine>Net Price</adsml:DescriptionLine>
					<!-- The description explains whether it is a Net or Gross total price type -->
					<!-- This is an unrestricted string in case the sender wants to indicate some other price type -->
				</adsml:TotalPrice>
				<!-- Optional stack of price components. If a component is present, it must be named -->
				<adsml:PriceComponent adsml:sequenceNo="1">
					<!-- sequence number is mandatory but you can generate price components in any sequence you want -->
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>GrossPrice</adsml:CodeValue>
					</adsml:PriceComponentName>
					<adsml:Amount>5500.00</adsml:Amount>
					<adsml:DescriptionLine>Gross Price</adsml:DescriptionLine>
					<!-- You can put an optional Calculation Specification here if you want to show the unit price -->
				</adsml:PriceComponent>
				<!-- Color or production charges or other premium charge(s) would normally go after the gross price -->
				<adsml:PriceComponent adsml:sequenceNo="2">
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>ColorCharge</adsml:CodeValue>
					</adsml:PriceComponentName>
					<adsml:Amount>500</adsml:Amount>
					<!-- This should be the total component price -->
					<adsml:DescriptionLine>Color Charge</adsml:DescriptionLine>
					<!-- Optionally, a further breakdown of the price component in terms of unit prices or percentages could go here -->
				</adsml:PriceComponent>
				<adsml:PriceComponent adsml:sequenceNo="3">
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>Production</adsml:CodeValue>
					</adsml:PriceComponentName>
					<adsml:Amount>0</adsml:Amount>
					<adsml:DescriptionLine>Production Charge</adsml:DescriptionLine>
				</adsml:PriceComponent>
				<adsml:PriceComponent adsml:sequenceNo="4">
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>AgencyCommission</adsml:CodeValue>
					</adsml:PriceComponentName>
					<adsml:Amount>825</adsml:Amount>
					<adsml:DescriptionLine>Agency Commission</adsml:DescriptionLine>
					<adsml:CalculationSpecification>
						<adsml:Percent>15</adsml:Percent>
						<adsml:BasePrice>5500.00</adsml:BasePrice>
					</adsml:CalculationSpecification>
				</adsml:PriceComponent>
				<adsml:PriceComponent adsml:sequenceNo="5">
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>CashDiscount</adsml:CodeValue>
					</adsml:PriceComponentName>
					<adsml:Amount>0</adsml:Amount>
					<adsml:DescriptionLine>Cash Discount</adsml:DescriptionLine>
					<adsml:CalculationSpecification>
						<adsml:Percent>0</adsml:Percent>
						<adsml:BasePrice>0</adsml:BasePrice>
					</adsml:CalculationSpecification>
				</adsml:PriceComponent>
				<adsml:PriceComponent adsml:sequenceNo="6">
					<adsml:PriceComponentName>
						<adsml:CodeValue xsi:type="adsml-cv:AdsMLPriceComponentCV"
							>Tax</adsml:CodeValue>
					</adsml:PriceComponentName>
					<!-- There are other AdsML PriceComponentName codes available to identify specific types of taxes -->
					<adsml:Amount>0.00</adsml:Amount>
					<adsml:DescriptionLine>Taxes</adsml:DescriptionLine>
					<adsml:CalculationSpecification>
						<adsml:Percent>0.000</adsml:Percent>
						<adsml:BasePrice>0</adsml:BasePrice>
					</adsml:CalculationSpecification>
				</adsml:PriceComponent>
			</PlacementPrice>
			<!-- The CostExempt element, if present, indicates that there will be no charge for this order and gives a reason-->
			<CostExempt>
				<ExemptionType>
					<adsml:CodeValue>MakeGood</adsml:CodeValue>
				</ExemptionType>
			</CostExempt>
			<!-- The buyer provides a caption for the ad -->
			<adsml:DescriptionLine>THE BEST BURGERS 2006</adsml:DescriptionLine>
			<!-- The  Status code in a Request message (from buyer to seller) can iden "New", "Unchanged", "Changed" placement statuses as shown here -->
			<adsml:Status>
				<adsml:CodeValue>New</adsml:CodeValue>
			</adsml:Status>
			<!-- Special requirements that apply only to this placement go here. Requirements applying to the entire order go at the bottom of the message -->
			<adsml:SpecialRequirements>
				<adsml:Text>WIND DOWN FOR THIS AD PLEASE DISREGARD INVOICING INSTRUCTIONS BELOW AND
					SEND INVOICES AS WELL AS TEARSHEETS TO THE ATTN OF ACCOUNTS PAYABLE 5111
					COMMERCE CROSSINGS SUITE 200 LOUISVILLE, KY 40229</adsml:Text>
			</adsml:SpecialRequirements>
			<!-- Notes that apply only to this placement go here. Notes applying to the entire order go at the bottom of the message -->
			<adsml:Notes>
				<!-- Any open-ended textual comments about this placement/insertion can go in this section; but not production instructions which go elsewhere -->
				<!-- AdsML requires that each note be stamped with creation time and author, but sending system can put whatever makes most sense in these attributes -->
				<adsml:NoteLine adsml:timeStamp="2006-06-01T09:15:00-05:00" adsml:author="DDS"
					>INSERTION APPROVED SEE ADDITIONAL INFORMATION FOR DATE</adsml:NoteLine>
				<!-- Multiple NoteLines are permitted in the message: if necessary the receiving system can concatenate them into a single long note. -->
			</adsml:Notes>
			<!-- The buyer provides the pubcode and name for the intended publication. -->
			<Publication>
				<PublicationCode>
					<adsml:CodeValue>03042200</adsml:CodeValue>
				</PublicationCode>
				<adsml:Name>Publication Name Goes Here</adsml:Name>
			</Publication>
			<InsertionPeriod>
				<ScheduleEntryIdentifier>dds.com:2006-06-01:M-05THC0015-REV000.219-1</ScheduleEntryIdentifier>
				<FirstPossibleTime>2006-08-05</FirstPossibleTime>
				<!-- As shown, these can be dates rather than times -->
				<LastPossibleTime>2006-09-05</LastPossibleTime>
				<!-- The dates can be the same to indicate a specific day, or a range of dates within which publication is permitted  -->
				<EventCount>1</EventCount>
				<adsml:SpecialRequirements>
					<adsml:Text>Best food day</adsml:Text>
					<!-- This text can describe the desired date in any appropriate way -->
				</adsml:SpecialRequirements>
			</InsertionPeriod>
			<!-- InsertionPeriod is repeatable to indicate multiple dates for the same placement -->
			<InsertionPeriod>
				<ScheduleEntryIdentifier>dds.com:2006-06-01:M-05THC0015-REV000.219-2</ScheduleEntryIdentifier>
				<FirstPossibleTime>2006-08-05</FirstPossibleTime>
				<LastPossibleTime>2006-09-05</LastPossibleTime>
				<EventCount>1</EventCount>
				<adsml:SpecialRequirements>
					<adsml:Text>Best Travel day</adsml:Text>
				</adsml:SpecialRequirements>
			</InsertionPeriod>
			<DistributionTarget>
				<Targeting>
					<!-- If the sender can provide a list of zone or edition codes, and especially if they are using the Seller's published zone or edition codes,
							then these codes should go in a Targeting structure as shown here. 
							However, targeting information can also be provided as free form text Special Requirements
						
							Putting all these codes in a single Targeting structure indicates that distribution should go to the intersection of the Zone and Edition codes, 
							that is, only to the specified editions in the specified zones -->
					<Target>
						<!-- If zoning information is included in the order (ie. PubZone), it goes in a Target element. 
								Multiple codes can be provided and distribution will go to all of them -->
						<Code>
							<adsml:CodeList xsi:type="adsml-cv:AdsMLTargetingTypeCodeCV"
								>Zone</adsml:CodeList>
							<adsml:CodeValue>01</adsml:CodeValue>
							<adsml:Description>MIDWEST</adsml:Description>
						</Code>
						<Code>
							<adsml:CodeList xsi:type="adsml-cv:AdsMLTargetingTypeCodeCV"
								>Zone</adsml:CodeList>
							<adsml:CodeValue>02</adsml:CodeValue>
							<adsml:Description>SOUTHWEST</adsml:Description>
						</Code>
					</Target>
					<!-- If edition information is included in the order it goes in a second, parallel Target element. 
							Multiple editions can be provided and distribution will go to all of them-->
					<Target>
						<Code>
							<adsml:CodeList xsi:type="adsml-cv:AdsMLTargetingTypeCodeCV"
								>Edition</adsml:CodeList>
							<adsml:CodeValue>M</adsml:CodeValue>
							<adsml:Description>Morning</adsml:Description>
						</Code>
					</Target>
				</Targeting>
			</DistributionTarget>
			<!-- The buyer provides production detail for the ad. -->
			<ProductionDetail.NewspaperMagazine>
				<Size>
					<AdSizeCode>
						<adsml:CodeValue>Half page full color bleed</adsml:CodeValue>
						<!-- In this case the "code" is apparently just an uncontrolled text string, which will have to be manually interpreted by the recipient -->
						<adsml:Description>Optional additional text description goes
							here</adsml:Description>
					</AdSizeCode>
				</Size>
				<Colors>
					<ColorType>
						<!-- If the buyer uses one code or string to describe both size and color, a copy of it goes here -->
						<adsml:CodeValue>PG4C</adsml:CodeValue>
						<adsml:Description>Optional longer text description goes
							here</adsml:Description>
					</ColorType>
				</Colors>
				<!-- Bleed information goes in the size code or its companion text description -->
				<Positioning>
					<PrimaryPositioning>
						<!-- Put all placement and positioning information in this area -->
						<PlacementInBook>
							<!-- An optional section code, or a section name if codes are not used -->
							<SectionCode>
								<adsml:CodeValue xsi:type="adsml-cv:AdsMLSectionCodeCV"
									>Food</adsml:CodeValue>
								<adsml:Description>Great Foods</adsml:Description>
							</SectionCode>
							<!-- Alternatively, textual placement instructions can be sent as Specifications -->
							<adsml:Specifications>
								<!-- If both Placement and Positioning instructions are in the same text string, put  them both HERE  -->
								<adsml:Text>PLACE IN ?GREAT FOODS? SECTION . RUN ON TOP HALF RIGHT
									HAND PAGE **** DO NOT RUN WITHIN SIX PAGES OF A COMPETITOR. TO
									DO SO WILL RESULT IN LOSS OF PAYMENT.</adsml:Text>
							</adsml:Specifications>
						</PlacementInBook>
						<PositionOnPage>
							<!-- Defined codes can be used to transmit machine-processable positioning instructions -->
							<!-- Multiple position codes are ANDed together -->
							<adsml:Code>
								<adsml:CodeValue xsi:type="adsml-cv:AdsMLPositionOnPagePrintCV"
									>TopOfPage</adsml:CodeValue>
							</adsml:Code>
							<adsml:Code>
								<adsml:CodeValue xsi:type="adsml-cv:AdsMLPositionOnPagePrintCV"
									>RightSideOfPage</adsml:CodeValue>
							</adsml:Code>
							<!-- Otherwise, textual positioning instructions go here -->
							<adsml:Text>RUN ON TOP HALF RIGHT HAND PAGE</adsml:Text>
						</PositionOnPage>
					</PrimaryPositioning>
					<CuttablePosition>false</CuttablePosition>
				</Positioning>
				<adsml:SpecialRequirements>
					<!-- Any general production requirements go here -->
					<adsml:Text/>
				</adsml:SpecialRequirements>
			</ProductionDetail.NewspaperMagazine>
			<!-- Pick-up instructions or related information. -->
			<PickUp>
				<PlacementReference>-0-</PlacementReference>
				<!-- -0- indicates that the value is unknown -->
				<adsml:Instructions>
					<adsml:Text>MATERIAL IS SAME AS PREVIOUS, AD IS A REPEAT OF JUL06 INSERTION, FOR
						AD CODE BURG01</adsml:Text>
				</adsml:Instructions>
			</PickUp>
			<!-- Any codes for the ad materials themselves go here, e.g. their Ad ID -->
			<adsml-ma:AdContent>
				<adsml-ma:AuxiliaryMaterialsReferences>
					<!-- This is where the buyer's primary ID for the materials goes, often called the Ad ID -->
					<adsml:BuyersReference>THCC45684568</adsml:BuyersReference>
					<!-- If the buyer has more than one ID for the art materials they go in the optional OtherReferences stack -->
					<adsml:OtherReference>
						<adsml:Value>BURG01</adsml:Value>
						<adsml:Label>AdCode</adsml:Label>
					</adsml:OtherReference>
				</adsml-ma:AuxiliaryMaterialsReferences>
			</adsml-ma:AdContent>
			<!-- Additional information about the materials, including who will provide them (if known) and when they will arrive (if known) -->
			<adsml-ma:MaterialsExpectations>
				<adsml-ma:MaterialsProviderParty>
					<adsml:Identifier>
						<!-- AdsML Schema requires a formal identifier, but if none is known, put "(none)" in both Label and Value -->
						<adsml:IDLabel xsi:type="adsml-cv:AdsMLOrganizationIDClassCV"
							>AssignedByBuyer</adsml:IDLabel>
						<!-- The ID 999 below was "assigned by buyer" -->
						<adsml:IDValue>999</adsml:IDValue>
					</adsml:Identifier>
					<adsml:Name>Production House Name goes here</adsml:Name>
					<!-- Production house main address -->
					<adsml:PartyAddress>
						<adsml:CommunicationChannel.PhysicalAddress>
							<adsml:Street>Street address 1</adsml:Street>
							<!-- repeatable -->
							<adsml:Street>NEW YORK, NY 10011</adsml:Street>
							<adsml:ZipPostalCode>10011</adsml:ZipPostalCode>
							<!-- optional -->
							<adsml:CountryName>USA</adsml:CountryName>
							<!-- optional -->
						</adsml:CommunicationChannel.PhysicalAddress>
						<adsml:CommunicationChannel.Other>
							<adsml:Type>
								<adsml:CodeValue>URL</adsml:CodeValue>
							</adsml:Type>
							<adsml:Specification>
								<adsml:Value>WWW.ADVANTAGE.COM</adsml:Value>
							</adsml:Specification>
						</adsml:CommunicationChannel.Other>
					</adsml:PartyAddress>
					<!-- Entire contact structure is available for use but it is all OPTIONAL -->
					<adsml:Contact>
						<adsml:Role>Optional role or title goes here</adsml:Role>
						<adsml:Name>Person Name</adsml:Name>
						<adsml:CommunicationChannel.Phone>
							<adsml:Type>Voice</adsml:Type>
							<adsml:PhoneNumber>212-633-0000</adsml:PhoneNumber>
						</adsml:CommunicationChannel.Phone>
						<adsml:CommunicationChannel.Phone>
							<adsml:Type>Fax</adsml:Type>
							<adsml:PhoneNumber>212-633-0001</adsml:PhoneNumber>
						</adsml:CommunicationChannel.Phone>
						<adsml:CommunicationChannel.EMail>
							<adsml:EMailAddress>person@company.com</adsml:EMailAddress>
						</adsml:CommunicationChannel.EMail>
					</adsml:Contact>
				</adsml-ma:MaterialsProviderParty>
				<adsml-ma:MaterialsDueDateTime>2006-08-03</adsml-ma:MaterialsDueDateTime>
			</adsml-ma:MaterialsExpectations>
		</Placement.NewspaperMagazine>
		<!-- Additional PLACEMENTS would go here -->
		<!-- ====== Placement details end here - we are back to information about the order as a whole ====== -->
		<adsml:SpecialRequirements>
			<adsml:Text>POSITIONING INSTRUCTIONS: NOTE CAREFULLY: IN THE ABSENCE OF A CONTRACT FROM
				US...YOU ARE NOT TO INSERT THIS ADVERTISING WITHOUT FIRST NOTIFYING US.</adsml:Text>
			<adsml:Text>COMPETITIVE SEPARATION: do not place ad within 6 pages of a compeitiors ad.
				For a list of competgitors please contact: Account Representative c/o Mediaplex
				Systems 5111 Commerce Crossings Louisville, KY 40229</adsml:Text>
		</adsml:SpecialRequirements>
	</AdOrder>
</AdsMLBookings>

