Star Logo

Implementation Guideline

Get Vehicle Remarketing
Repository Version Rev4.5.4












Copyright 2007 STAR – Standards for Technology in Automotive Retail. All rights reserved












Get Vehicle Remarketing

Table of Contents

top

Overview

This document is a guideline on how to use the Get Vehicle Remarketing Business Object Document (BOD). Get Vehicle Remarketing has been defined in the context of STAR for the Automotive Retail Industry. The scope of this BOD is to define the Get Vehicle Remarketing process for individual consumers who service their automobiles through their OEM’s authorized Dealers. The focus is on Dealer and OEM interactions, not third party organizations. NOTE: Although this is the traditional use of the Get Vehicle Remarketing, this BOD could be used to send Get Vehicle Remarketing information between any two business parties.

The Get Vehicle Remarketing Implementation Guidelines provide detailed information regarding the structure and meaning of the Get Vehicle Remarketing BOD and corresponds directly to the Get Vehicle Remarketing schema. In addition to structure and meaning, the Implementation Guidelines identify various business rules for specific fields/components that due to their nature, i.e. field interdependence, are not possible to express using schema. Please note that although these business rules are not included in the schema, they MUST be followed to be STAR Compliant. Therefore, the Get Vehicle Remarketing Implementation Guidelines must be used in concert with the Get Vehicle Remarketing schema during development and should NOT be considered a supplement or substitution to the schema. For more information regarding STAR XML Data Compliance, please review the STAR Data Compliance Guidelines document located on the STAR Web site.

For a copy of the corresponding Get Vehicle Remarketing schema, please download the appropriate STAR schema repository from the XML portion of the STAR website (www.starstandard.org). Prior to downloading the schema, users are encouraged to download the STAR XML Reference/Implementation document also located on the XML portion of the STAR website. This document provides an overview of the STAR BOD development methodology, how to download and read STAR schema, and various frequently asked questions related to the implementation of STAR BODs.

STAR has followed the Open Application Group’s Business Object Document methodology to develop the Get Vehicle Remarketing BOD. Where possible, STAR has mapped to existing OAGI fields and components. Note however that the STAR Get Vehicle Remarketing BOD is unique to the Retail Automotive industry and is not an extension of any existing OAGIS BODs.

For more information on the Open Applications Group's BODs and related documentation please refer to the Open Applications Group’s Web site at www.openapplications.org.

top

Schema Field Usage

STAR uses the same Noun in the schema for all the Noun/Verb combinations of the Get Vehicle Remarketing except the Get verb. Please refer to each Noun/Verb combination within this document to understand the requirements for each specific BOD. Although the Noun will always have every field defined for the Noun in the schema, each Noun/Verb combination may not use all of the fields. If a field is not used by a BOD, it will be noted in the business rules.

top

Business Scenario

BUSINESS SCENARIO MISSING. Please make sure it is defined in the build script.

top

Relationship Diagram

The relationship diagram identifies all of the various components or building blocks of information used in the Get Vehicle Remarketing BOD. This diagram visually depicts the relationships of the components using symbolic indentation and their occurrence in the BOD. Note: That this is an approximation of the Components, and may not reflect the exact implementation. Also, some fields are displayed in the diagram. This diagram should only be used as a starting point and not an absolute reference. Relationship Diagram for VehicleRemarketing

top

Schema Document Properties

Target Namespacehttp://www.starstandards.org/STAR
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations belong to this schema's target namespace.
  • By default, local attribute declarations have no namespace.
DocumentationThis schema is made available under an Eclipse Public Licenses 1.0. This license may be found in the STAR/License directory as well as the STAR BOD Guidelines.
More information at: http://www.starstandard.org/.

Declared Namespaces

PrefixNamespace
Default namespacehttp://www.starstandards.org/STAR
xmlhttp://www.w3.org/XML/1998/namespace
xsdhttp://www.w3.org/2001/XMLSchema

Schema Component Representation
<xsd:schema targetNamespace="http://www.starstandards.org/STAR" elementFormDefault="qualified" attributeFormDefault="unqualified">
...
</xsd:schema>
top

Global Declarations

Element: ApplicationArea

NameApplicationArea
TypeApplicationArea
Nillableno
Abstractno
DocumentationProvides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of.
More information at: http://www.openapplications.org/oagis.

Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of.
More information at: http://www.openapplications.org/oagis.

XML Instance Representation
<ApplicationArea>
<Sender> Sender </Sender> [1] ?
<CreationDateTime> DateTime </CreationDateTime> [1] ?
<Signature> Signature </Signature> [0..1] ?
<BODId> Code </BODId> [0..1] ?
<Destination> Destination </Destination> [1] ?
</ApplicationArea>
Schema Component Representation
<xsd:element name="ApplicationArea" type="ApplicationArea"/>
top

Element: Get

  • This element can be used wherever the following element is referenced:

NameGet
TypeGet
Nillableno
Abstractno
DocumentationThe Get verb is to communicate to a business software component a request for an existing piece of information to be returned. The Get may be paired with most of the nouns defined in the OAGIS specification.The response to this request is the Show verb. The behavior of a BOD with a Get verb is quite predictable across most of the nouns it may be paired with.The Get is designed to retrieve a single piece of information by using that information's primary retrieval field, or key field. The Get verb is not used to request several documents at once. The GetList verb is designed to achieve that purpose and will be covered in more detail later.Selection Criteria:There are two types of selection capabilities for most BOD's that use the Get verb.1) The first selection capability is called Field-Based Selection. Within a Get-based Business Object Document, the first Data Type that occurs in a specific BOD structure is commonly used to provide the Field-Based Selection criteria. This is always defined within the specific BOD and is commonly the required fields for that specific Data type.The Field-Based Selection enables the requester to provide a value or values (in the case of multiple required Field Identifiers), in the required fields. Then the responding component uses those values to find and return the requested information to the originating business software component.2) The second type of selection capability for Get-based BODs is called Data Type Selection. Data Type selection enables the requester to identify which Data Types within the noun are requested to be returned in the response. The use of this capability is described for each corresponding Data Type for all BODs that use the Get verb. The Data Types are identified for retrieval within the Get instance of a BOD by including the name of the Data Type in the meta data but without any Field Identifiers or Segments identified within the Data Type. This will signify to the responding application that all of the data that corresponds to that Data Type is to be included in the response.If the Data Type is not requested, the Data Type identifier is not included in the Get request and this will signify to the responding component that the Data Type is not to be returned.
More information at: http://www.openapplications.org/oagis.

XML Instance Representation
<Get
confirm="ConfirmType [0..1]"

show="Always [1]"
>
<ReturnCriteria> ... </ReturnCriteria> [1] ?
</Get>
Schema Component Representation
<xsd:element name="Get" type="Get" substitutionGroup="Verb"/>
top

Element: GetVehicleRemarketing

NameGetVehicleRemarketing
TypeGetVehicleRemarketing
Nillableno
Abstractno

XML Instance Representation
<GetVehicleRemarketing
revision="Text [0..1] ?"

release="8.1-Lite [0..1] ?"

environment="Text [0..1] ?"

lang="Language [0..1] ?"

bodVersion="Text [0..1] ?"
>
<DataArea> GetVehicleRemarketingDataArea </DataArea> [1]
</GetVehicleRemarketing>
Schema Component Representation
<xsd:element name="GetVehicleRemarketing" type="GetVehicleRemarketing"/>
top

Element: Header

NameHeader
TypeVehicleRemarketingHeader
Nillableno
Abstractno
Documentation More information at: http://www.starstandards.org.

XML Instance Representation
<Header>
<DocumentDateTime> DocumentDateTime </DocumentDateTime> [0..1] ?
<SecondaryPassword> SecondaryPassword </SecondaryPassword> [0..1] ?
<SecondaryDealerNumber> SecondaryDealerNumber </SecondaryDealerNumber> [0..1] ?
<DocumentId> DocumentId </DocumentId> [1] ?
<OrganizationId> OrganizationId </OrganizationId> [0..1] ?
<ContractStartDate> ContractStartDate </ContractStartDate> [0..1] ?
<ContractExpirationDate> ContractExpirationDate </ContractExpirationDate> [0..1] ?
<ContractId> ContractId </ContractId> [0..1] ?
</Header>
Schema Component Representation
<xsd:element name="Header" type="VehicleRemarketingHeader"/>
top

Element: Vehicle

NameVehicle
TypeVehicleRemarketingVehicle
Nillableno
Abstractno
Documentation More information at: http://www.starstandards.org.

XML Instance Representation
<Vehicle>
<Model> Model </Model> [0..1] ?
<ModelYear> ModelYear </ModelYear> [0..1] ?
<ModelDescription> ModelDescription </ModelDescription> [0..1] ?
<Make> Make </Make> [0..1] ?
<SaleClass> SaleClass </SaleClass> [0..1] ?
<Condition> Condition </Condition> [0..1] ?
<CertifiedPreownedInd> CertifiedPreownedInd </CertifiedPreownedInd> [0..1] ?
<VehicleNote> VehicleNote </VehicleNote> [0..*] ?
<VIN> VIN </VIN> [0..1] ?
<DeliveryMileage> DeliveryMileage </DeliveryMileage> [0..1] ?
<VehicleStock> VehicleStock </VehicleStock> [0..1] ?
<TrimCode> TrimCode </TrimCode> [0..1] ?
<DoorsQuantity> DoorsQuantity </DoorsQuantity> [0..1] ?
<BodyStyle> BodyStyle </BodyStyle> [0..1] ?
<InteriorColor> InteriorColor </InteriorColor> [0..*] ?
<ExteriorColor> ExteriorColor </ExteriorColor> [0..*] ?
<TransmissionType> TransmissionType </TransmissionType> [0..1] ?
<OdometerStatus> OdometerStatus </OdometerStatus> [0..1] ?
<NonUSVehicleInd> NonUSVehicleInd </NonUSVehicleInd> [0..1] ?
<VehicleDemoInd> VehicleDemoInd </VehicleDemoInd> [0..1] ?
<LicenseNumber> LicenseNumber </LicenseNumber> [0..1] ?
<BrandedInfo> BrandedInfo </BrandedInfo> [0..1] ?
<RestrictionInd> RestrictionInd </RestrictionInd> [0..1] ?
<RestrictionDescription> RestrictionDescription </RestrictionDescription> [0..1] ?
<TelematicsServiceInd> TelematicsServiceInd </TelematicsServiceInd> [0..1] ?
<Option> RemarketingOption </Option> [0..*] ?
<TransmissionCode> TransmissionCode </TransmissionCode> [0..1] ?
<DeliveryDate> DeliveryDate </DeliveryDate> [0..1] ?
<EngineNumber> EngineNumber </EngineNumber> [0..1] ?
<IgnitionKeyNumber> IgnitionKeyNumber </IgnitionKeyNumber> [0..1] ?
<DoorKeyNumber> DoorKeyNumber </DoorKeyNumber> [0..1] ?
<ExteriorColorCode> ExteriorColorCode </ExteriorColorCode> [0..1] ?
<InteriorColorCode> InteriorColorCode </InteriorColorCode> [0..1] ?
<VehicleLocation> VehicleLocation </VehicleLocation> [0..1] ?
<VehicleAcquisitionDate> VehicleAcquisitionDate </VehicleAcquisitionDate> [0..1] ?
<VehiclePricing> VehiclePricing </VehiclePricing> [0..*] ?
<Tax> Tax </Tax> [0..*] ?
<Dealer> DealerExtendedAddress </Dealer> [0..1] ?
<JobToDo> JobToDo </JobToDo> [0..*] ?
<JobCompleted> JobCompleted </JobCompleted> [0..*] ?
<Damage> RepairDamage </Damage> [0..*] ?
<TransmissionTypeName> TransmissionTypeName </TransmissionTypeName> [0..1] ?
<VehicleClass> VehicleClass </VehicleClass> [0..1] ?
<FuelType> FuelType </FuelType> [0..1] ?
<EngineDescription> EngineDescription </EngineDescription> [0..1] ?
<EngineConfiguration> EngineConfiguration </EngineConfiguration> [0..1] ?
<EngineInduction> EngineInduction </EngineInduction> [0..1] ?
<EngineDisplacement> EngineDisplacement </EngineDisplacement> [0..1] ?
<EngineCylinders> EngineCylinders </EngineCylinders> [0..1] ?
<EngineHorsepower> EngineHorsepower </EngineHorsepower> [0..1] ?
<DriveTrain> DriveTrain </DriveTrain> [0..1] ?
<DriveType> DriveType </DriveType> [0..1] ?
<Warranty> RemarketingWarranty </Warranty> [0..*] ?
<Financing> RemarketingFinancing </Financing> [0..*] ?
<PreviousIndividualOwner> IndividualPartyMinimal </PreviousIndividualOwner> [0..1] ?
<PreviousOrganizationalOwner> OrganizationPartyMinimal </PreviousOrganizationalOwner> [0..1] ?
<ImageAttachment> ImageAttachmentExtended </ImageAttachment> [0..*] ?
<VehiclePassengers> VehiclePassengers </VehiclePassengers> [0..1] ?
<VehicleInspections> VehicleInspections </VehicleInspections> [0..1] ?
<TireCondition> TireCondition </TireCondition> [0..1] ?
<VehicleReceivedDate> VehicleReceivedDate </VehicleReceivedDate> [0..1] ?
<LastModificationDate> LastModificationDate </LastModificationDate> [0..1] ?
<PreviousVehicleUse> PreviousVehicleUse </PreviousVehicleUse> [0..1] ?
<SoldDate> SoldDate </SoldDate> [0..1] ?
<CertificationIssuer> CertificationIssuer </CertificationIssuer> [0..1] ?
<CertificationValue> CertificationValue </CertificationValue> [0..1] ?
<Advertising> Advertising </Advertising> [0..*] ?
<FinancingAvailableInd> FinancingAvailableInd </FinancingAvailableInd> [0..1] ?
</Vehicle>
Schema Component Representation
<xsd:element name="Vehicle" type="VehicleRemarketingVehicle"/>
top

Element: VehicleRemarketing

NameVehicleRemarketing
TypeVehicleRemarketing
Nillableno
Abstractno
Documentation More information at: http://www.starstandards.org.

XML Instance Representation
<VehicleRemarketing>
<Header> ... </Header> [1]
<Vehicle> ... </Vehicle> [0..*]
</VehicleRemarketing>
Schema Component Representation
<xsd:element name="VehicleRemarketing" type="VehicleRemarketing"/>
top

Element: Verb

  • The following elements can be used wherever this element is referenced:

NameVerb
TypeVerb
Nillableno
Abstractyes

XML Instance Representation
<Verb/>
Schema Component Representation
<xsd:element name="Verb" type="Verb" abstract="true"/>
top

Global Definitions

Components (Complex Type): AddressBase

Super-types:None
Sub-types:

NameAddressBase
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
AddressLineIndicates the multiple lines of an address. The first line is typically the street name and number. Required 
CityIs the City of the Address. Required 
CountyCounty in which the Address is in. Optional 
StateOrProvinceIs the State or Province of a given Address. Required 
CountryCountry in which the Address is in. Required 
PostalCodePostal Code of the Address. Required 

XML Instance Representation
<...>
<AddressLine> AddressLine </AddressLine> [1..*] ?
<City> City </City> [1] ?
<County> County </County> [0..1] ?
<StateOrProvince> StateOrProvince </StateOrProvince> [1] ?
<Country> Country </Country> [1] ?
<PostalCode> PostalCode </PostalCode> [1] ?
</...>
Schema Component Representation
<xsd:complexType name="AddressBase">
<xsd:sequence>
<xsd:element name="AddressLine" type="AddressLine" maxOccurs="unbounded"/>
<xsd:element name="City" type="City"/>
<xsd:element name="County" type="County" minOccurs="0"/>
<xsd:element name="StateOrProvince" type="StateOrProvince"/>
<xsd:element name="Country" type="Country"/>
<xsd:element name="PostalCode" type="PostalCode"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): Advertising

Super-types:None
Sub-types:None

NameAdvertising
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
AdvertisingCopyInformation that goes in the ad Optional 
AdvertisingMediaMedia where ad is placed. Ex: Internet, newspaper, etc. Optional 
CopyTypeType of copy used for ad. Ex: Teaser text, short description, long description Optional 
LanguageLanguage for the ad copy Optional 

XML Instance Representation
<...>
<AdvertisingCopy> AdvertisingCopy </AdvertisingCopy> [0..1] ?
<AdvertisingMedia> AdvertisingMedia </AdvertisingMedia> [0..1] ?
<CopyType> CopyType </CopyType> [0..1] ?
<Language> Language </Language> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="Advertising">
<xsd:sequence>
<xsd:element name="AdvertisingCopy" type="AdvertisingCopy" minOccurs="0"/>
<xsd:element name="AdvertisingMedia" type="AdvertisingMedia" minOccurs="0"/>
<xsd:element name="CopyType" type="CopyType" minOccurs="0"/>
<xsd:element name="Language" type="Language" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): Amount

Super-types:xsd:decimal < Amount (by extension)
Sub-types:None

NameAmount
Abstractno
DocumentationBased on OAGI Amount. Simple content with the currency as an attrbute
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
currency Required 

XML Instance Representation
<...
currency="Currency [1]"
>
xsd:decimal
</...>
Schema Component Representation
<xsd:complexType name="Amount">
<xsd:simpleContent>
<xsd:extension base="xsd:decimal">
<xsd:attribute name="currency" type="Currency" use="required"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): AnnualMilesAllowed

Super-types:xsd:integer < Count (by extension) < Mileage (by extension) < AnnualMilesAllowed (by extension)
Sub-types:None

NameAnnualMilesAllowed
Abstractno
DocumentationThe number allowed annually for a balloon contract.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
uom="MileageMeasure [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="AnnualMilesAllowed">
<xsd:simpleContent>
<xsd:extension base="Mileage"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): AnnualPercentageRate

Super-types:xsd:decimal < Percent (by extension) < AnnualPercentageRate (by extension)
Sub-types:None

NameAnnualPercentageRate
Abstractno
DocumentationAnnual percentage rate.
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="AnnualPercentageRate">
<xsd:simpleContent>
<xsd:extension base="Percent"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ApplicationArea

Super-types:None
Sub-types:None

NameApplicationArea
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
SenderIdentifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. Required 
CreationDateTimeis the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. Required
DateTime fields must be formatted as XML Schema Datetimes in UTC/GMT format without offsets. Example: 2003-11-05T13:15:30Z
 
SignatureIf the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs. Optional
Optional. "qualifyingAgency" attribute.
 
BODIdThe BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security. Optional 
DestinationInformation related to the receiver of the BOD Required
See Destination Component.
 

XML Instance Representation
<...>
<Sender> Sender </Sender> [1] ?
<CreationDateTime> DateTime </CreationDateTime> [1] ?
<Signature> Signature </Signature> [0..1] ?
<BODId> Code </BODId> [0..1] ?
<Destination> Destination </Destination> [1] ?
</...>
Schema Component Representation
<xsd:complexType name="ApplicationArea">
<xsd:sequence>
<xsd:element name="Sender" type="Sender"/>
<xsd:element name="CreationDateTime" type="DateTime"/>
<xsd:element name="Signature" type="Signature" minOccurs="0"/>
<xsd:element name="BODId" type="Code" minOccurs="0"/>
<xsd:element name="Destination" type="Destination"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): ApprovedAmount

Super-types:xsd:decimal < Amount (by extension) < ApprovedAmount (by extension)
Sub-types:None

NameApprovedAmount
Abstractno
DocumentationAmount pre-approved
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="ApprovedAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): BalanceAmount

Super-types:xsd:decimal < Amount (by extension) < BalanceAmount (by extension)
Sub-types:None

NameBalanceAmount
Abstractno
DocumentationRemaining balance on Current Vehicle
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="BalanceAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): BrandedInfo

Super-types:None
Sub-types:None

NameBrandedInfo
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
BrandedTitleIndThis tag indicates if a vehicle's title has been branded. (i.e., vehicle totaled and state registration title branded as such) Optional 
BrandedTitleDateBranding Date Optional 
BrandingStateCodeBranding State Code Optional 
BrandingStateReferenceBranding State Reference Number Optional 
BrandingSourceBranding source ƒ¢€“ (i.e., source who says that the vehicle is branded) Optional 

XML Instance Representation
<...>
<BrandedTitleInd> BrandedTitleInd </BrandedTitleInd> [0..1] ?
<BrandedTitleDate> BrandedTitleDate </BrandedTitleDate> [0..1] ?
<BrandingStateCode> BrandingStateCode </BrandingStateCode> [0..1] ?
<BrandingStateReference> BrandingStateReference </BrandingStateReference> [0..1] ?
<BrandingSource> BrandingSource </BrandingSource> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="BrandedInfo">
<xsd:sequence>
<xsd:element name="BrandedTitleInd" type="BrandedTitleInd" minOccurs="0"/>
<xsd:element name="BrandedTitleDate" type="BrandedTitleDate" minOccurs="0"/>
<xsd:element name="BrandingStateCode" type="BrandingStateCode" minOccurs="0"/>
<xsd:element name="BrandingStateReference" type="BrandingStateReference" minOccurs="0"/>
<xsd:element name="BrandingSource" type="BrandingSource" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): BrandingStateCode

Super-types:xsd:string < StateOrProvince (by restriction) < BrandingStateCode (by extension)
Sub-types:None

NameBrandingStateCode
Abstractno
DocumentationBranding State Code
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="BrandingStateCode">
<xsd:simpleContent>
<xsd:extension base="StateOrProvince"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): BusinessObjectDocument

Super-types:None
Sub-types:

NameBusinessObjectDocument
Abstractno

Attributes

AttributeDescriptionRequirementBusiness Rules
revisionThis should contain the STAR repository version in the following recommended format. 4.2.1_M20080416. Where the first part indicates the version of the STAR repository and anything after the _ indicates the Milestone build that is being used. If referring to an official published version then only the STAR Repository version is required. Optional 
releaseIndicates the OAGIS release that this BOD belongs. Optional 
environmentIndicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Optional 
langIndicates the language that the contents of the BOD is in unless otherwise stated. Optional 
bodVersionDeprecated as of STAR 4.2.2. It is recommended to use the revision attribute to identify the repository and the noun. May be removed in a new major version of the STAR repository. Optional 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
ApplicationAreaProvides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Required 

XML Instance Representation
<...
revision="Text [0..1] ?"

release="8.1-Lite [0..1] ?"

environment="Text [0..1] ?"

lang="Language [0..1] ?"

bodVersion="Text [0..1] ?"
>
</...>
Schema Component Representation
<xsd:complexType name="BusinessObjectDocument">
<xsd:sequence>
<xsd:element ref="ApplicationArea"/>
</xsd:sequence>
<xsd:attribute name="revision" use="optional">
<xsd:simpleType>
<xsd:restriction base="Text"/>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="release" type="Text" use="optional" fixed="8.1-Lite"/>
<xsd:attribute name="environment" use="optional" default="Production">
<xsd:simpleType>
<xsd:restriction base="Text">
<xsd:enumeration value="Test"/>
<xsd:enumeration value="Production"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="lang" type="Language" use="optional"/>
<xsd:attribute name="bodVersion" use="optional">
<xsd:simpleType>
<xsd:restriction base="Text"/>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
top

Components (Complex Type): CodeType

Super-types:xsd:string < CodeType (by extension)
Sub-types:None

NameCodeType
Abstractno
DocumentationUnique code name
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
listID Optional 
listName Optional 
listAgencyID Optional 
listAgencyName Optional 
listVersionID Optional 
listURI Optional 

XML Instance Representation
<...
listID="xsd:token [0..1]"

listName="xsd:string [0..1]"

listAgencyID="xsd:token [0..1]"

listAgencyName="xsd:string [0..1]"

listVersionID="xsd:token [0..1]"

listURI="xsd:anyURI [0..1]"
>
xsd:string
</...>
Schema Component Representation
<xsd:complexType name="CodeType">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="listID" type="xsd:token" use="optional"/>
<xsd:attribute name="listName" type="xsd:string" use="optional"/>
<xsd:attribute name="listAgencyID" type="xsd:token" use="optional"/>
<xsd:attribute name="listAgencyName" type="xsd:string" use="optional"/>
<xsd:attribute name="listVersionID" type="xsd:token" use="optional"/>
<xsd:attribute name="listURI" type="xsd:anyURI" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ConfirmableVerb

Super-types:Verb < ConfirmableVerb (by extension)
Sub-types:

NameConfirmableVerb
Abstractno

Attributes

AttributeDescriptionRequirementBusiness Rules
confirm Required 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
Verb Required 

XML Instance Representation
<...
confirm="ConfirmType [0..1]"
/>
Schema Component Representation
<xsd:complexType name="ConfirmableVerb">
<xsd:complexContent>
<xsd:extension base="Verb">
<xsd:attribute name="confirm" type="ConfirmType"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): ContractId

Super-types:xsd:string < Id (by extension) < ContractId (by extension)
Sub-types:None

NameContractId
Abstractno
DocumentationIdentification of Contract
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="ContractId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Count

Super-types:xsd:integer < Count (by extension)
Sub-types:None

NameCount
Abstractno
DocumentationSimple quantity type with no attributes
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
xsd:integer
</...>
Schema Component Representation
<xsd:complexType name="Count">
<xsd:simpleContent>
<xsd:extension base="xsd:integer"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): DealerExtendedAddress

Super-types:PartyBase < DealerPartyBase (by extension) < DealerExtendedAddress (by extension)
Sub-types:None

NameDealerExtendedAddress
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
PartyIdParty Identification Number Optional 
DealerNameDealer name Optional 
DistrictCodeManufacturer Assigned District Code Optional 
URIDealer URI Optional 
ZoneCodeManufacturer Assigned Zone Code Optional 
AddressDealer party address Optional 

XML Instance Representation
<...>
<PartyId> PartyId </PartyId> [0..1] ?
<DealerName> DealerName </DealerName> [0..1] ?
<DistrictCode> DistrictCode </DistrictCode> [0..1] ?
<URI> URI </URI> [0..1] ?
<ZoneCode> ZoneCode </ZoneCode> [0..1] ?
<Address> OrganizationAddress </Address> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="DealerExtendedAddress">
<xsd:complexContent>
<xsd:extension base="DealerPartyBase">
<xsd:sequence>
<xsd:element name="Address" type="OrganizationAddress" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): DealerPartyBase

Super-types:PartyBase < DealerPartyBase (by extension)
Sub-types:

NameDealerPartyBase
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
PartyIdParty Identification Number Optional 
DealerNameDealer name Optional 
DistrictCodeManufacturer Assigned District Code Optional 
URIDealer URI Optional 
ZoneCodeManufacturer Assigned Zone Code Optional 

XML Instance Representation
<...>
<PartyId> PartyId </PartyId> [0..1] ?
<DealerName> DealerName </DealerName> [0..1] ?
<DistrictCode> DistrictCode </DistrictCode> [0..1] ?
<URI> URI </URI> [0..1] ?
<ZoneCode> ZoneCode </ZoneCode> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="DealerPartyBase">
<xsd:complexContent>
<xsd:extension base="PartyBase">
<xsd:sequence>
<xsd:element name="DealerName" type="DealerName" minOccurs="0"/>
<xsd:element name="DistrictCode" type="DistrictCode" minOccurs="0"/>
<xsd:element name="URI" type="URI" minOccurs="0"/>
<xsd:element name="ZoneCode" type="ZoneCode" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): DeliveryMileage

Super-types:xsd:integer < Count (by extension) < Mileage (by extension) < DeliveryMileage (by extension)
Sub-types:None

NameDeliveryMileage
Abstractno
DocumentationOdometer reading of vehicle at time of delivery
More information at: http://www.starstandard.org.

XML Instance Representation
<...
uom="MileageMeasure [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="DeliveryMileage">
<xsd:simpleContent>
<xsd:extension base="Mileage"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Description

Super-types:xsd:string < Description (by extension)
Sub-types:None

NameDescription
Abstractno
DocumentationDescription
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
languageThe ISO language code that the description is written. Optional 

XML Instance Representation
<...
language="Language [0..1] ?"
>
xsd:string
</...>
Schema Component Representation
<xsd:complexType name="Description">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="language" type="Language" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Destination

Super-types:None
Sub-types:None

NameDestination
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DestinationNameCodeCode for destination of file (i.e.Short Manufacturer or DSP code) Optional
Must use a valid code from the ShortMfg/RSP list on http://www.starstandards.org
 
DestinationURIPhysical address of the destination Optional 
DestinationSoftwareCodeAdditional information about the destination application Optional 
DestinationSoftwareFor which software destination file is intended (may not be known). Optional 
DealerNumberTarget Dealer Code receiving information Optional 
StoreNumberDealer code store number (DMS assigned) Optional 
AreaNumberDealer code area number (DMS vendor assigned) Optional 
DealerCountryTarget Dealer country location Optional 
PartyIdThe Party Id field uniquely identifies the Receiver of the message. This element can be used for parties within the Automotive Community as well as external parties. Party Id is not intended as a replacement for the Dealer Number. Suggested formats for OEMs or other large institutions include: DUNs Number, ShortMfgCode + DUNs, or ShortMfgCode. The suggested format for Dealers is: ShortMfgCode+Dealer Number. Optional 
LocationIdThe Location Id field uniquely identifies the location of the Receiver of a message. This Id may be aligned with a physical address or data centers. This field provides an additional level of granularity beyond the usage of the Party Id for additional routing and deliver of data. Optional 
ServiceIdThe Service Id field identifies the particular service to which a message is being sent, e.g., an inventory service. Optional 

XML Instance Representation
<...>
<DestinationNameCode> ShortMfg </DestinationNameCode> [0..1] ?
<DestinationURI> URI </DestinationURI> [0..1] ?
<DestinationSoftwareCode> Text </DestinationSoftwareCode> [0..1] ?
<DestinationSoftware> Text </DestinationSoftware> [0..1] ?
<DealerNumber> PartyId </DealerNumber> [0..1] ?
<StoreNumber> Text </StoreNumber> [0..1] ?
<AreaNumber> Text </AreaNumber> [0..1] ?
<DealerCountry> Country </DealerCountry> [0..1] ?
<PartyId> PartyId </PartyId> [0..1] ?
<LocationId> LocationId </LocationId> [0..1] ?
<ServiceId> ServiceId </ServiceId> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="Destination">
<xsd:sequence>
<xsd:element name="DestinationNameCode" type="ShortMfg" minOccurs="0"/>
<xsd:element name="DestinationURI" type="URI" minOccurs="0"/>
<xsd:element name="DestinationSoftwareCode" type="Text" minOccurs="0"/>
<xsd:element name="DestinationSoftware" type="Text" minOccurs="0"/>
<xsd:element name="DealerNumber" type="PartyId" minOccurs="0"/>
<xsd:element name="StoreNumber" type="Text" minOccurs="0"/>
<xsd:element name="AreaNumber" type="Text" minOccurs="0"/>
<xsd:element name="DealerCountry" type="Country" minOccurs="0"/>
<xsd:element name="PartyId" type="PartyId" minOccurs="0"/>
<xsd:element name="LocationId" type="LocationId" minOccurs="0"/>
<xsd:element name="ServiceId" type="ServiceId" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): DocumentId

Super-types:xsd:string < Id (by extension) < DocumentId (by extension)
Sub-types:None

NameDocumentId
Abstractno
DocumentationIs the identifier for the document.
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="DocumentId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): DoorsQuantity

Super-types:xsd:integer < Count (by extension) < DoorsQuantity (by restriction)
Sub-types:None

NameDoorsQuantity
Abstractno
DocumentationNumber of doors on vehicle
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="DoorsQuantity">
<xsd:simpleContent>
<xsd:restriction base="Count"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): DownPaymentAmount

Super-types:xsd:decimal < Amount (by extension) < DownPaymentAmount (by extension)
Sub-types:None

NameDownPaymentAmount
Abstractno
DocumentationDown Payment amount or amount of cap cost reduction.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="DownPaymentAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): EmbeddedData

Super-types:None
Sub-types:None

NameEmbeddedData
Abstractno
Documentationembedded data witin a BOD
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
encoding Required 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DataContainer to carry the embedded data Required 

XML Instance Representation
<...
encoding="EncodingBase [0..1]"
>
<Data> Data </Data> [1] ?
</...>
Schema Component Representation
<xsd:complexType name="EmbeddedData">
<xsd:sequence>
<xsd:element name="Data" type="Data"/>
</xsd:sequence>
<xsd:attribute name="encoding" type="EncodingBase"/>
</xsd:complexType>
top

Components (Complex Type): EngineCylinders

Super-types:xsd:integer < Count (by extension) < EngineCylinders (by restriction)
Sub-types:None

NameEngineCylinders
Abstractno
DocumentationEngine cylinder count
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="EngineCylinders">
<xsd:simpleContent>
<xsd:restriction base="Count"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): EngineDescription

Super-types:xsd:string < Description (by extension) < EngineDescription (by extension)
Sub-types:None

NameEngineDescription
Abstractno
DocumentationText description of engine (e.g. dohc, 32 valves)
More information at: http://www.starstandard.org.

XML Instance Representation
<...
language="Language [0..1] ?"
>
</...>
Schema Component Representation
<xsd:complexType name="EngineDescription">
<xsd:simpleContent>
<xsd:extension base="Description"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ExcessMileageRate

Super-types:xsd:decimal < Amount (by extension) < ExcessMileageRate (by extension)
Sub-types:None

NameExcessMileageRate
Abstractno
DocumentationThe rate charged per mile over the annual miles allowed.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="ExcessMileageRate">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ExpressionCriteria

Super-types:None
Sub-types:None

NameExpressionCriteria
Abstractno

Attributes

AttributeDescriptionRequirementBusiness Rules
expressionLanguage Optional 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
SelectExpressionAllows the 1-n number of selection expressions for the information to be returned. Required 

XML Instance Representation
<...
expressionLanguage="ExpressionLanguage [0..1]"
>
<SelectExpression> Expression </SelectExpression> [1..*] ?
</...>
Schema Component Representation
<xsd:complexType name="ExpressionCriteria">
<xsd:sequence>
<xsd:element name="SelectExpression" type="Expression" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="expressionLanguage" type="ExpressionLanguage" use="optional" default="XPath"/>
</xsd:complexType>
top

Components (Complex Type): FinalAmount

Super-types:xsd:decimal < Amount (by extension) < FinalAmount (by extension)
Sub-types:None

NameFinalAmount
Abstractno
DocumentationLast month payment amount
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="FinalAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): FinanceCharge

Super-types:xsd:decimal < Amount (by extension) < FinanceCharge (by extension)
Sub-types:None

NameFinanceCharge
Abstractno
DocumentationThe total interest paid on the contract.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="FinanceCharge">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Get

Super-types:Verb < ConfirmableVerb (by extension) < RequestVerb (by extension) < Get (by extension)
Sub-types:None

NameGet
Abstractno

Attributes

AttributeDescriptionRequirementBusiness Rules
show Required 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
Verb Required 
ReturnCriteriaReturnCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned. ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar. ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns. That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated. The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies. Required 

XML Instance Representation
<...
confirm="ConfirmType [0..1]"

show="Always [1]"
>
<ReturnCriteria> ... </ReturnCriteria> [1] ?
</...>
Schema Component Representation
<xsd:complexType name="Get">
<xsd:complexContent>
<xsd:extension base="RequestVerb">
<xsd:attribute name="show" type="xsd:string" use="required" fixed="Always"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): GetVehicleRemarketing

Super-types:BusinessObjectDocument < GetVehicleRemarketing (by extension)
Sub-types:None

NameGetVehicleRemarketing
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
ApplicationAreaProvides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Required 
DataArea Required 

XML Instance Representation
<...
revision="Text [0..1] ?"

release="8.1-Lite [0..1] ?"

environment="Text [0..1] ?"

lang="Language [0..1] ?"

bodVersion="Text [0..1] ?"
>
<DataArea> GetVehicleRemarketingDataArea </DataArea> [1]
</...>
Schema Component Representation
<xsd:complexType name="GetVehicleRemarketing">
<xsd:complexContent>
<xsd:extension base="BusinessObjectDocument">
<xsd:sequence>
<xsd:element name="DataArea" type="GetVehicleRemarketingDataArea"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): GetVehicleRemarketingDataArea

Super-types:None
Sub-types:None

NameGetVehicleRemarketingDataArea
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
GetThe Get verb is to communicate to a business software component a request for an existing piece of information to be returned. The Get may be paired with most of the nouns defined in the OAGIS specification.The response to this request is the Show verb. The behavior of a BOD with a Get verb is quite predictable across most of the nouns it may be paired with.The Get is designed to retrieve a single piece of information by using that information's primary retrieval field, or key field. The Get verb is not used to request several documents at once. The GetList verb is designed to achieve that purpose and will be covered in more detail later.Selection Criteria:There are two types of selection capabilities for most BOD's that use the Get verb.1) The first selection capability is called Field-Based Selection. Within a Get-based Business Object Document, the first Data Type that occurs in a specific BOD structure is commonly used to provide the Field-Based Selection criteria. This is always defined within the specific BOD and is commonly the required fields for that specific Data type.The Field-Based Selection enables the requester to provide a value or values (in the case of multiple required Field Identifiers), in the required fields. Then the responding component uses those values to find and return the requested information to the originating business software component.2) The second type of selection capability for Get-based BODs is called Data Type Selection. Data Type selection enables the requester to identify which Data Types within the noun are requested to be returned in the response. The use of this capability is described for each corresponding Data Type for all BODs that use the Get verb. The Data Types are identified for retrieval within the Get instance of a BOD by including the name of the Data Type in the meta data but without any Field Identifiers or Segments identified within the Data Type. This will signify to the responding application that all of the data that corresponds to that Data Type is to be included in the response.If the Data Type is not requested, the Data Type identifier is not included in the Get request and this will signify to the responding component that the Data Type is not to be returned. Required 
VehicleRemarketing Required 

XML Instance Representation
<...>
<Get> ... </Get> [1]
</...>
Schema Component Representation
<xsd:complexType name="GetVehicleRemarketingDataArea">
<xsd:sequence>
<xsd:element ref="Get"/>
<xsd:element ref="VehicleRemarketing" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): HeaderBase

Super-types:None
Sub-types:

NameHeaderBase
Abstractno
DocumentationUsed on all STAR BODs
More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DocumentDateTimeIs the date and time the document was last created. This is not the date and time that the BOD message instance was created. Optional
DateTime fields must be formatted as XML Schema DateTimes in UTC/GMT format without offsets. Example: 2003-11-05T13:15:30Z
 
SecondaryPasswordSecondary password used to validate access to the dealer information Optional 
SecondaryDealerNumberIdentifies secondary dealer number if different than primary "Dealer Number" Optional 

XML Instance Representation
<...>
<DocumentDateTime> DocumentDateTime </DocumentDateTime> [0..1] ?
<SecondaryPassword> SecondaryPassword </SecondaryPassword> [0..1] ?
<SecondaryDealerNumber> SecondaryDealerNumber </SecondaryDealerNumber> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="HeaderBase">
<xsd:sequence>
<xsd:element name="DocumentDateTime" type="DocumentDateTime" minOccurs="0"/>
<xsd:element name="SecondaryPassword" type="SecondaryPassword" minOccurs="0"/>
<xsd:element name="SecondaryDealerNumber" type="SecondaryDealerNumber" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): Id

Super-types:xsd:string < Id (by extension)
Sub-types:None

NameId
Abstractno
DocumentationParty Identification number
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
xsd:string
</...>
Schema Component Representation
<xsd:complexType name="Id">
<xsd:simpleContent>
<xsd:extension base="xsd:string"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ImageAttachment

Super-types:None
Sub-types:

NameImageAttachment
Abstractno
Documentationrepresents information about the location of on-line vehicle photos.
More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
URIURI Optional 
ImageWidthImage tag width. Example: "100" Optional 
ImageHeightImage tag height Example: "120" Optional 
ImageAlternateTextImage alternate text. Example: "1997 Honda Accord" Optional 

XML Instance Representation
<...>
<URI> URI </URI> [0..1] ?
<ImageWidth> ImageWidth </ImageWidth> [0..1] ?
<ImageHeight> ImageHeight </ImageHeight> [0..1] ?
<ImageAlternateText> ImageAlternateText </ImageAlternateText> [0..*] ?
</...>
Schema Component Representation
<xsd:complexType name="ImageAttachment">
<xsd:sequence>
<xsd:element name="URI" type="URI" minOccurs="0"/>
<xsd:element name="ImageWidth" type="ImageWidth" minOccurs="0"/>
<xsd:element name="ImageHeight" type="ImageHeight" minOccurs="0"/>
<xsd:element name="ImageAlternateText" type="ImageAlternateText" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): ImageAttachmentExtended

Super-types:ImageAttachment < ImageAttachmentExtended (by extension)
Sub-types:None

NameImageAttachmentExtended
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
URIURI Optional 
ImageWidthImage tag width. Example: "100" Optional 
ImageHeightImage tag height Example: "120" Optional 
ImageAlternateTextImage alternate text. Example: "1997 Honda Accord" Optional 
ImageAttachmentTitleImage attachment title Optional 
EmbeddedDataHolder for embedded data. (Will have an attribute for type of enbedded document) Optional 

XML Instance Representation
<...>
<URI> URI </URI> [0..1] ?
<ImageWidth> ImageWidth </ImageWidth> [0..1] ?
<ImageHeight> ImageHeight </ImageHeight> [0..1] ?
<ImageAlternateText> ImageAlternateText </ImageAlternateText> [0..*] ?
<ImageAttachmentTitle> ImageAttachmentTitle </ImageAttachmentTitle> [0..1] ?
<EmbeddedData> EmbeddedData </EmbeddedData> [0..*] ?
</...>
Schema Component Representation
<xsd:complexType name="ImageAttachmentExtended">
<xsd:complexContent>
<xsd:extension base="ImageAttachment">
<xsd:sequence>
<xsd:element name="ImageAttachmentTitle" type="ImageAttachmentTitle" minOccurs="0"/>
<xsd:element name="EmbeddedData" type="EmbeddedData" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): ImageHeight

Super-types:xsd:integer < Count (by extension) < ImageHeight (by restriction)
Sub-types:None

NameImageHeight
Abstractno
DocumentationImage tag height Example: "120"
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="ImageHeight">
<xsd:simpleContent>
<xsd:restriction base="Count"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): ImageWidth

Super-types:xsd:integer < Count (by extension) < ImageWidth (by restriction)
Sub-types:None

NameImageWidth
Abstractno
DocumentationImage tag width. Example: "100"
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="ImageWidth">
<xsd:simpleContent>
<xsd:restriction base="Count"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): IndividualPartyMinimal

Super-types:PartyBase < IndividualPartyMinimal (by extension)
Sub-types:None

NameIndividualPartyMinimal
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
PartyIdParty Identification Number Optional 
PersonNameIndividual party name Optional 

XML Instance Representation
<...>
<PartyId> PartyId </PartyId> [0..1] ?
<PersonName> IndividualPartyPersonName2 </PersonName> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="IndividualPartyMinimal">
<xsd:complexContent>
<xsd:extension base="PartyBase">
<xsd:sequence>
<xsd:element name="PersonName" type="IndividualPartyPersonName2" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): IndividualPartyPersonName2

Super-types:None
Sub-types:None

NameIndividualPartyPersonName2
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
SalutationTitle or greeting of business party Optional 
GivenNameFirst Name of business party Required 
MiddleNameMiddle Initial of business party Optional 
FamilyNameLast Name of business party Required 
SuffixBusiness Party name suffix designation if individual Ex: Sr, Jr, III, etc. Optional 
FormattedNameFull Name of business party. Format for name should be "First Last" with no commas between first and last name Optional 

XML Instance Representation
<...>
<Salutation> Salutation </Salutation> [0..1] ?
<GivenName> GivenName </GivenName> [1] ?
<MiddleName> MiddleName </MiddleName> [0..1] ?
<FamilyName> FamilyName </FamilyName> [1] ?
<Suffix> Suffix </Suffix> [0..1] ?
<FormattedName> FormattedName </FormattedName> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="IndividualPartyPersonName2">
<xsd:sequence>
<xsd:element name="Salutation" type="Salutation" minOccurs="0"/>
<xsd:element name="GivenName" type="GivenName"/>
<xsd:element name="MiddleName" type="MiddleName" minOccurs="0"/>
<xsd:element name="FamilyName" type="FamilyName"/>
<xsd:element name="Suffix" type="Suffix" minOccurs="0"/>
<xsd:element name="FormattedName" type="FormattedName" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): JobCompleted

Super-types:None
Sub-types:None

NameJobCompleted
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
RepairOrderNumberIdentification number of repair order assigned by dealer or DMS Optional 
DescriptionDescription of work completed on vehicle Optional 
TotalAmountTotal amount for operation Optional 

XML Instance Representation
<...>
<RepairOrderNumber> RepairOrderNumber </RepairOrderNumber> [0..1] ?
<Description> Description </Description> [0..1] ?
<TotalAmount> TotalAmount </TotalAmount> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="JobCompleted">
<xsd:sequence>
<xsd:element name="RepairOrderNumber" type="RepairOrderNumber" minOccurs="0"/>
<xsd:element name="Description" type="Description" minOccurs="0"/>
<xsd:element name="TotalAmount" type="TotalAmount" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): JobToDo

Super-types:None
Sub-types:None

NameJobToDo
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DescriptionDescription of work to be completed on vehicle Optional 
TotalAmountTotal amount for operation Optional 

XML Instance Representation
<...>
<Description> Description </Description> [0..1] ?
<TotalAmount> TotalAmount </TotalAmount> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="JobToDo">
<xsd:sequence>
<xsd:element name="Description" type="Description" minOccurs="0"/>
<xsd:element name="TotalAmount" type="TotalAmount" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): LocationId

Super-types:xsd:string < Id (by extension) < LocationId (by extension)
Sub-types:None

NameLocationId
Abstractno
DocumentationCode identifying a physical location
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="LocationId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Mileage

Super-types:xsd:integer < Count (by extension) < Mileage (by extension)
Sub-types:None

NameMileage
Abstractno
DocumentationMileage definition
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
uom Optional 

XML Instance Representation
<...
uom="MileageMeasure [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="Mileage">
<xsd:simpleContent>
<xsd:extension base="Count">
<xsd:attribute name="uom" type="MileageMeasure" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): NewFinancing

Super-types:None
Sub-types:

NameNewFinancing
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
FinanceTypeType of financing Examples may be F- Finance, L - Lease, C-Cash, 1-Retail, 2-Lease, 3-Balloon, etc.. Optional 
PaymentAmountMonthly Payment Amount Optional 
BalanceAmountRemaining balance on Current Vehicle Optional 
FinalAmountLast month payment amount Optional 
ResidualAmountRemaining residual on current vehicle Optional 
TermNumber of months of contract term Optional 
MaturityDateMonth and year of contract maturity Optional 
FinanceCompanyNameName of Finance Company Optional 
DownPaymentAmountDown Payment amount or amount of cap cost reduction. Optional 
PurchasePricePurchase Price or Gross Cap cost specified in deal. Total payments at end of purchase Optional 
ApprovedIndApproved Indicator Optional 
ApprovedAmountAmount pre-approved Optional 
ExpirationDateDate pre-approval expires Optional 
RatingIndexRating Index Used for Credit Approval Optional 

XML Instance Representation
<...>
<FinanceType> FinanceType </FinanceType> [0..1] ?
<PaymentAmount> PaymentAmount </PaymentAmount> [0..1] ?
<BalanceAmount> BalanceAmount </BalanceAmount> [0..1] ?
<FinalAmount> FinalAmount </FinalAmount> [0..1] ?
<ResidualAmount> ResidualAmount </ResidualAmount> [0..1] ?
<Term> Term </Term> [0..1] ?
<MaturityDate> MaturityDate </MaturityDate> [0..1] ?
<FinanceCompanyName> FinanceCompanyName </FinanceCompanyName> [0..1] ?
<DownPaymentAmount> DownPaymentAmount </DownPaymentAmount> [0..1] ?
<PurchasePrice> PurchasePrice </PurchasePrice> [0..1] ?
<ApprovedInd> ApprovedInd </ApprovedInd> [0..1] ?
<ApprovedAmount> ApprovedAmount </ApprovedAmount> [0..1] ?
<ExpirationDate> ExpirationDate </ExpirationDate> [0..1] ?
<RatingIndex> RatingIndex </RatingIndex> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="NewFinancing">
<xsd:sequence>
<xsd:element name="FinanceType" type="FinanceType" minOccurs="0"/>
<xsd:element name="PaymentAmount" type="PaymentAmount" minOccurs="0"/>
<xsd:element name="BalanceAmount" type="BalanceAmount" minOccurs="0"/>
<xsd:element name="FinalAmount" type="FinalAmount" minOccurs="0"/>
<xsd:element name="ResidualAmount" type="ResidualAmount" minOccurs="0"/>
<xsd:element name="Term" type="Term" minOccurs="0"/>
<xsd:element name="MaturityDate" type="MaturityDate" minOccurs="0"/>
<xsd:element name="FinanceCompanyName" type="FinanceCompanyName" minOccurs="0"/>
<xsd:element name="DownPaymentAmount" type="DownPaymentAmount" minOccurs="0"/>
<xsd:element name="PurchasePrice" type="PurchasePrice" minOccurs="0"/>
<xsd:element name="ApprovedInd" type="ApprovedInd" minOccurs="0"/>
<xsd:element name="ApprovedAmount" type="ApprovedAmount" minOccurs="0"/>
<xsd:element name="ExpirationDate" type="ExpirationDate" minOccurs="0"/>
<xsd:element name="RatingIndex" type="RatingIndex" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): NonTaxableAmount

Super-types:xsd:decimal < Amount (by extension) < NonTaxableAmount (by extension)
Sub-types:None

NameNonTaxableAmount
Abstractno
DocumentationTotal non-taxable price.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="NonTaxableAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): OptionBase

Super-types:None
Sub-types:

NameOptionBase
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
OptionTypeAn option type for a vehicle or other component. Usually references an OEM supplied list of codes. Optional 
OptionNameName of vehicle option Optional 
OptionStockNumberStock Number of Vehicle Option Optional 
ManufacturerManufacturer of Vehicle Option Optional 

XML Instance Representation
<...>
<OptionType> OptionType </OptionType> [0..1] ?
<OptionName> OptionName </OptionName> [0..1] ?
<OptionStockNumber> OptionStockNumber </OptionStockNumber> [0..1] ?
<Manufacturer> Manufacturer </Manufacturer> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="OptionBase">
<xsd:sequence>
<xsd:element name="OptionType" type="OptionType" minOccurs="0"/>
<xsd:element name="OptionName" type="OptionName" minOccurs="0"/>
<xsd:element name="OptionStockNumber" type="OptionStockNumber" minOccurs="0"/>
<xsd:element name="Manufacturer" type="Manufacturer" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): OptionType

Super-types:xsd:string < CodeType (by extension) < OptionType (by extension)
Sub-types:None

NameOptionType
Abstractno
DocumentationOption Type from an OEM or other sources list of codes.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
listID="xsd:token [0..1]"

listName="xsd:string [0..1]"

listAgencyID="xsd:token [0..1]"

listAgencyName="xsd:string [0..1]"

listVersionID="xsd:token [0..1]"

listURI="xsd:anyURI [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="OptionType">
<xsd:simpleContent>
<xsd:extension base="CodeType"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): OrganizationAddress

Super-types:AddressBase < OrganizationAddress (by extension)
Sub-types:None

NameOrganizationAddress
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
AddressLineIndicates the multiple lines of an address. The first line is typically the street name and number. Required 
CityIs the City of the Address. Required 
CountyCounty in which the Address is in. Optional 
StateOrProvinceIs the State or Province of a given Address. Required 
CountryCountry in which the Address is in. Required 
PostalCodePostal Code of the Address. Required 
UrbanizationCodeGeographic definition of a metropolitan or suburban area Optional 

XML Instance Representation
<...>
<AddressLine> AddressLine </AddressLine> [1..*] ?
<City> City </City> [1] ?
<County> County </County> [0..1] ?
<StateOrProvince> StateOrProvince </StateOrProvince> [1] ?
<Country> Country </Country> [1] ?
<PostalCode> PostalCode </PostalCode> [1] ?
<UrbanizationCode> UrbanizationCode </UrbanizationCode> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="OrganizationAddress">
<xsd:complexContent>
<xsd:extension base="AddressBase">
<xsd:sequence>
<xsd:element name="UrbanizationCode" type="UrbanizationCode" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): OrganizationId

Super-types:xsd:string < Id (by extension) < OrganizationId (by extension)
Sub-types:None

NameOrganizationId
Abstractno
DocumentationMember Identification number of affiliate organization
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="OrganizationId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): OrganizationPartyMinimal

Super-types:PartyBase < OrganizationPartyMinimal (by extension)
Sub-types:None

NameOrganizationPartyMinimal
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
PartyIdParty Identification Number Optional 
NameCompany name of organizational party Optional 

XML Instance Representation
<...>
<PartyId> PartyId </PartyId> [0..1] ?
<Name> CompanyName </Name> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="OrganizationPartyMinimal">
<xsd:complexContent>
<xsd:extension base="PartyBase">
<xsd:sequence>
<xsd:element name="Name" type="CompanyName" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): PartyBase

Super-types:None
Sub-types:

NamePartyBase
Abstractno
DocumentationDerived from oa:Party
More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
PartyIdParty Identification Number Optional 

XML Instance Representation
<...>
<PartyId> PartyId </PartyId> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="PartyBase">
<xsd:sequence>
<xsd:element name="PartyId" type="PartyId" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): PartyId

Super-types:xsd:string < Id (by extension) < PartyId (by extension)
Sub-types:None

NamePartyId
Abstractno
DocumentationParty Identification Number
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="PartyId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): PaymentAmount

Super-types:xsd:decimal < Amount (by extension) < PaymentAmount (by extension)
Sub-types:None

NamePaymentAmount
Abstractno
DocumentationMonthly Payment Amount
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="PaymentAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Percent

Super-types:xsd:decimal < Percent (by extension)
Sub-types:None

NamePercent
Abstractno
DocumentationPercent
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
xsd:decimal
</...>
Schema Component Representation
<xsd:complexType name="Percent">
<xsd:simpleContent>
<xsd:extension base="xsd:decimal"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): PurchasePrice

Super-types:xsd:decimal < Amount (by extension) < PurchasePrice (by extension)
Sub-types:None

NamePurchasePrice
Abstractno
DocumentationPurchase Price or Gross Cap cost specified in deal. Total payments at end of purchase
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="PurchasePrice">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Rating

Super-types:xsd:string < Rating (by extension)
Sub-types:None

NameRating
Abstractno
DocumentationStanding or position on a scale, e.g. credit score.
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
score Optional 

XML Instance Representation
<...
score="Decimal [0..1]"
>
xsd:string
</...>
Schema Component Representation
<xsd:complexType name="Rating">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="score" type="Decimal" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): RatingIndex

Super-types:xsd:string < Rating (by extension) < RatingIndex (by extension)
Sub-types:None

NameRatingIndex
Abstractno
DocumentationRating Index Used for Credit Approval
More information at: http://www.starstandard.org.

XML Instance Representation
<...
score="Decimal [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="RatingIndex">
<xsd:simpleContent>
<xsd:extension base="Rating"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): RemarketingFinancing

Super-types:NewFinancing < RemarketingFinancing (by extension)
Sub-types:None

NameRemarketingFinancing
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
FinanceTypeType of financing Examples may be F- Finance, L - Lease, C-Cash, 1-Retail, 2-Lease, 3-Balloon, etc.. Optional 
PaymentAmountMonthly Payment Amount Optional 
BalanceAmountRemaining balance on Current Vehicle Optional 
FinalAmountLast month payment amount Optional 
ResidualAmountRemaining residual on current vehicle Optional 
TermNumber of months of contract term Optional 
MaturityDateMonth and year of contract maturity Optional 
FinanceCompanyNameName of Finance Company Optional 
DownPaymentAmountDown Payment amount or amount of cap cost reduction. Optional 
PurchasePricePurchase Price or Gross Cap cost specified in deal. Total payments at end of purchase Optional 
ApprovedIndApproved Indicator Optional 
ApprovedAmountAmount pre-approved Optional 
ExpirationDateDate pre-approval expires Optional 
RatingIndexRating Index Used for Credit Approval Optional 
MiscellaneousNotesFree form miscellaneous comments. Optional 
AnnualPercentageRateAnnual percentage rate. Optional 
FleetAccountLessor Fleet Account number indicating that this is a Fleet Transaction Optional 
PromotionalRateIndPromotional lease rate was used Optional 
TaxTax related to Financing Optional 
AnnualMilesAllowedLease mileage limit per year Optional 
ExcessMileageRateThe rate charged per mile over the annual miles allowed Optional 
FinanceChargeThe total interest paid on the contract Optional 

XML Instance Representation
<...>
<FinanceType> FinanceType </FinanceType> [0..1] ?
<PaymentAmount> PaymentAmount </PaymentAmount> [0..1] ?
<BalanceAmount> BalanceAmount </BalanceAmount> [0..1] ?
<FinalAmount> FinalAmount </FinalAmount> [0..1] ?
<ResidualAmount> ResidualAmount </ResidualAmount> [0..1] ?
<Term> Term </Term> [0..1] ?
<MaturityDate> MaturityDate </MaturityDate> [0..1] ?
<FinanceCompanyName> FinanceCompanyName </FinanceCompanyName> [0..1] ?
<DownPaymentAmount> DownPaymentAmount </DownPaymentAmount> [0..1] ?
<PurchasePrice> PurchasePrice </PurchasePrice> [0..1] ?
<ApprovedInd> ApprovedInd </ApprovedInd> [0..1] ?
<ApprovedAmount> ApprovedAmount </ApprovedAmount> [0..1] ?
<ExpirationDate> ExpirationDate </ExpirationDate> [0..1] ?
<RatingIndex> RatingIndex </RatingIndex> [0..1] ?
<MiscellaneousNotes> MiscellaneousNotes </MiscellaneousNotes> [0..1] ?
<AnnualPercentageRate> AnnualPercentageRate </AnnualPercentageRate> [0..1] ?
<FleetAccount> FleetAccount </FleetAccount> [0..1] ?
<PromotionalRateInd> PromotionalRateInd </PromotionalRateInd> [0..1] ?
<Tax> Tax </Tax> [0..*] ?
<AnnualMilesAllowed> AnnualMilesAllowed </AnnualMilesAllowed> [0..1] ?
<ExcessMileageRate> ExcessMileageRate </ExcessMileageRate> [0..1] ?
<FinanceCharge> FinanceCharge </FinanceCharge> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="RemarketingFinancing">
<xsd:complexContent>
<xsd:extension base="NewFinancing">
<xsd:sequence>
<xsd:element name="MiscellaneousNotes" type="MiscellaneousNotes" minOccurs="0"/>
<xsd:element name="AnnualPercentageRate" type="AnnualPercentageRate" minOccurs="0"/>
<xsd:element name="FleetAccount" type="FleetAccount" minOccurs="0"/>
<xsd:element name="PromotionalRateInd" type="PromotionalRateInd" minOccurs="0"/>
<xsd:element name="Tax" type="Tax" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="AnnualMilesAllowed" type="AnnualMilesAllowed" minOccurs="0"/>
<xsd:element name="ExcessMileageRate" type="ExcessMileageRate" minOccurs="0"/>
<xsd:element name="FinanceCharge" type="FinanceCharge" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): RemarketingOption

Super-types:OptionBase < RemarketingOption (by extension)
Sub-types:None

NameRemarketingOption
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
OptionTypeAn option type for a vehicle or other component. Usually references an OEM supplied list of codes. Optional 
OptionNameName of vehicle option Optional 
OptionStockNumberStock Number of Vehicle Option Optional 
ManufacturerManufacturer of Vehicle Option Optional 
OptionOriginIdentifies the option installer Optional 
OptionSerialNumberSerial number of Option Optional 
OptionNotesFree form text related to option Optional 

XML Instance Representation
<...>
<OptionType> OptionType </OptionType> [0..1] ?
<OptionName> OptionName </OptionName> [0..1] ?
<OptionStockNumber> OptionStockNumber </OptionStockNumber> [0..1] ?
<Manufacturer> Manufacturer </Manufacturer> [0..1] ?
<OptionOrigin> OptionOrigin </OptionOrigin> [0..1] ?
<OptionSerialNumber> OptionSerialNumber </OptionSerialNumber> [0..1] ?
<OptionNotes> OptionNotes </OptionNotes> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="RemarketingOption">
<xsd:complexContent>
<xsd:extension base="OptionBase">
<xsd:sequence>
<xsd:element name="OptionOrigin" type="OptionOrigin" minOccurs="0"/>
<xsd:element name="OptionSerialNumber" type="OptionSerialNumber" minOccurs="0"/>
<xsd:element name="OptionNotes" type="OptionNotes" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): RemarketingWarranty

Super-types:None
Sub-types:None

NameRemarketingWarranty
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
WarrantyTypeCodeType of warranty (Ex: OEM new, OEM used or third party) Optional 
WarrantyTypeDescriptionDescription of type of warranty Example: Basic /Powertrain, etc Optional 
WarrantyStartMileageMileage at start date of vehicle warranty Optional 
WarrantyEndMileageMileage limit for vehicle warranty coverage for warranty currently in force at time of repair Optional 
WarrantyStartDateStart date of vehicle warranty Optional 
WarrantyExpirationDateLast date of vehicle warranty coverage for warranty currently in force at time of repair Optional 
RoadsideAssistanceIndIndicates whether coverage includes roadside assistance Optional 
WarrantyTransferIndFlag indicating if warranty is transferable Optional 
WarrantyNotesAny Warranty related Notes Optional 
WarrantyClassA classification of warranty specifications that the warranty must address such as 'tires, power train, rust 'or 'power train only' and can be based on the age or mileage Optional 

XML Instance Representation
<...>
<WarrantyTypeCode> WarrantyTypeCode </WarrantyTypeCode> [0..1] ?
<WarrantyTypeDescription> WarrantyTypeDescription </WarrantyTypeDescription> [0..1] ?
<WarrantyStartMileage> WarrantyStartMileage </WarrantyStartMileage> [0..1] ?
<WarrantyEndMileage> WarrantyEndMileage </WarrantyEndMileage> [0..1] ?
<WarrantyStartDate> WarrantyStartDate </WarrantyStartDate> [0..1] ?
<WarrantyExpirationDate> WarrantyExpirationDate </WarrantyExpirationDate> [0..1] ?
<RoadsideAssistanceInd> RoadsideAssistanceInd </RoadsideAssistanceInd> [0..1] ?
<WarrantyTransferInd> WarrantyTransferInd </WarrantyTransferInd> [0..1] ?
<WarrantyNotes> WarrantyNotes </WarrantyNotes> [0..1] ?
<WarrantyClass> WarrantyClass </WarrantyClass> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="RemarketingWarranty">
<xsd:sequence>
<xsd:element name="WarrantyTypeCode" type="WarrantyTypeCode" minOccurs="0"/>
<xsd:element name="WarrantyTypeDescription" type="WarrantyTypeDescription" minOccurs="0"/>
<xsd:element name="WarrantyStartMileage" type="WarrantyStartMileage" minOccurs="0"/>
<xsd:element name="WarrantyEndMileage" type="WarrantyEndMileage" minOccurs="0"/>
<xsd:element name="WarrantyStartDate" type="WarrantyStartDate" minOccurs="0"/>
<xsd:element name="WarrantyExpirationDate" type="WarrantyExpirationDate" minOccurs="0"/>
<xsd:element name="RoadsideAssistanceInd" type="RoadsideAssistanceInd" minOccurs="0"/>
<xsd:element name="WarrantyTransferInd" type="WarrantyTransferInd" minOccurs="0"/>
<xsd:element name="WarrantyNotes" type="WarrantyNotes" minOccurs="0"/>
<xsd:element name="WarrantyClass" type="WarrantyClass" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): RepairDamage

Super-types:None
Sub-types:None

NameRepairDamage
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DescriptionDescription of damage on vehicle Optional 
TotalAmountTotal amount to repair damage Optional 

XML Instance Representation
<...>
<Description> Description </Description> [0..1] ?
<TotalAmount> TotalAmount </TotalAmount> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="RepairDamage">
<xsd:sequence>
<xsd:element name="Description" type="Description" minOccurs="0"/>
<xsd:element name="TotalAmount" type="TotalAmount" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): RequestVerb

Super-types:Verb < ConfirmableVerb (by extension) < RequestVerb (by extension)
Sub-types:
  • Get (by extension)

NameRequestVerb
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
Verb Required 
ReturnCriteriaReturnCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned. ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar. ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns. That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated. The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies. Required 

XML Instance Representation
<...
confirm="ConfirmType [0..1]"
>
<ReturnCriteria> ... </ReturnCriteria> [1] ?
</...>
Schema Component Representation
<xsd:complexType name="RequestVerb">
<xsd:complexContent>
<xsd:extension base="ConfirmableVerb">
<xsd:sequence>
<xsd:element name="ReturnCriteria"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): ResidualAmount

Super-types:xsd:decimal < Amount (by extension) < ResidualAmount (by extension)
Sub-types:None

NameResidualAmount
Abstractno
DocumentationRemaining residual on current vehicle
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="ResidualAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): RestrictionDescription

Super-types:xsd:string < Description (by extension) < RestrictionDescription (by extension)
Sub-types:None

NameRestrictionDescription
Abstractno
DocumentationDescription of vehicle use restrictions
More information at: http://www.starstandard.org.

XML Instance Representation
<...
language="Language [0..1] ?"
>
</...>
Schema Component Representation
<xsd:complexType name="RestrictionDescription">
<xsd:simpleContent>
<xsd:extension base="Description"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): SecondaryDealerNumber

Super-types:xsd:string < Id (by extension) < SecondaryDealerNumber (by extension)
Sub-types:None

NameSecondaryDealerNumber
Abstractno
DocumentationIdentifies secondary dealer number if different than primary "Dealer Number"
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="SecondaryDealerNumber">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Sender

Super-types:SenderBase < Sender (by extension)
Sub-types:None

NameSender
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
LogicalIdProvides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Optional 
ComponentProvides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. For STAR's use this is the DCS Software code name Required 
TaskDescribes the business event that initiated the need for the Business Object Document to be created. For STAR, the task is defined in the Implementation Guidelines for each BOD. It is usually a short description of the BOD. Ex: SalesLead, CreditDecision, etc. Required 
ReferenceIdEnables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This is used to correlate a response BOD to an originating BOD Optional 
AuthorizationIdIdentifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system. For STAR, this is the User ID. Optional 
CreatorNameCodeDCS Software Creator Code Required 
SenderNameCodeAdditional information about the sending platform (i.e., Short MFG or DSP code). Required
Must use a valid code from the ShortMfg/RSP list on http://www.starstandards.org
 
SenderURIPhysical address of the sender Optional 
DealerNumberDealer Code of source of information Optional
Dealer Number is Required if originating from DMS.
 
StoreNumberDealer code store number (DMS assigned) Optional 
AreaNumberDealer code area number (DMS vendor assigned) Optional 
DealerCountrySource Dealer country location Optional
Reference Country enumerator.
 
LanguageThis code is used to define the language of the data used in this transaction Optional
Reference Language enumerator.
 
DeliverPendingMailIndIndicates if the user requests to receive pending mail that has been stored and has yet not been delivered yet. By selecting 0, the user will only receive the response for the current transaction the user is performing. Optional
1 - Receive Pending Mail. 0 - Do not receive pending mail.
 
PasswordToken for application specific authentication. Used to authenticate dealership/users through application specific security Optional 
SystemVersionThe sender's software version number. Optional 
PartyIdThe Party Id field uniquely identifies the Sender of the message. This element can be used for parties within the Automotive Community as well as external parties. Party Id is not intended as a replacement for the Dealer Number. Suggested formats for OEMs or other large institutions include: DUNs Number, ShortMfgCode + DUNs, or ShortMfgCode. The suggested format for Dealers is: ShortMfgCode+Dealer Number. Optional 
LocationIdThe Location Id field uniquely identifies the location of the Sender of a message. This Id may be aligned with a physical address or data centers. This field provides an additional level of granularity beyond the usage of the Party Id for additional routing and deliver of data. Optional 
ServiceIdThe Service Id field identifies the particular service from which a message is being sent, e.g., an inventory service. Optional 

XML Instance Representation
<...>
<LogicalId> Text </LogicalId> [0..1] ?
<Component> Text </Component> [1] ?
<Task> Text </Task> [1] ?
<ReferenceId> Reference </ReferenceId> [0..1] ?
<AuthorizationId> Id </AuthorizationId> [0..1] ?
<CreatorNameCode> Text </CreatorNameCode> [1] ?
<SenderNameCode> ShortMfg </SenderNameCode> [1] ?
<SenderURI> URI </SenderURI> [0..1] ?
<DealerNumber> PartyId </DealerNumber> [0..1] ?
<StoreNumber> Text </StoreNumber> [0..1] ?
<AreaNumber> Text </AreaNumber> [0..1] ?
<DealerCountry> Country </DealerCountry> [0..1] ?
<Language> Language </Language> [0..1] ?
<DeliverPendingMailInd> Indicator </DeliverPendingMailInd> [0..1] ?
<Password> Text </Password> [0..1] ?
<SystemVersion> SystemVersion </SystemVersion> [0..1] ?
<PartyId> PartyId </PartyId> [0..1] ?
<LocationId> LocationId </LocationId> [0..1] ?
<ServiceId> ServiceId </ServiceId> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="Sender">
<xsd:complexContent>
<xsd:extension base="SenderBase">
<xsd:sequence>
<xsd:element name="CreatorNameCode" type="Text"/>
<xsd:element name="SenderNameCode" type="ShortMfg"/>
<xsd:element name="SenderURI" type="URI" minOccurs="0"/>
<xsd:element name="DealerNumber" type="PartyId" minOccurs="0"/>
<xsd:element name="StoreNumber" type="Text" minOccurs="0"/>
<xsd:element name="AreaNumber" type="Text" minOccurs="0"/>
<xsd:element name="DealerCountry" type="Country" minOccurs="0"/>
<xsd:element name="Language" type="Language" minOccurs="0"/>
<xsd:element name="DeliverPendingMailInd" type="Indicator" minOccurs="0"/>
<xsd:element name="Password" type="Text" minOccurs="0"/>
<xsd:element name="SystemVersion" type="SystemVersion" minOccurs="0"/>
<xsd:element name="PartyId" type="PartyId" minOccurs="0"/>
<xsd:element name="LocationId" type="LocationId" minOccurs="0"/>
<xsd:element name="ServiceId" type="ServiceId" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): SenderBase

Super-types:None
Sub-types:

NameSenderBase
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
LogicalIdProvides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Optional 
ComponentProvides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. For STAR's use this is the DCS Software code name Required 
TaskDescribes the business event that initiated the need for the Business Object Document to be created. For STAR, the task is defined in the Implementation Guidelines for each BOD. It is usually a short description of the BOD. Ex: SalesLead, CreditDecision, etc. Required 
ReferenceIdEnables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This is used to correlate a response BOD to an originating BOD Optional 
AuthorizationIdIdentifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system. For STAR, this is the User ID. Optional 

XML Instance Representation
<...>
<LogicalId> Text </LogicalId> [0..1] ?
<Component> Text </Component> [1] ?
<Task> Text </Task> [1] ?
<ReferenceId> Reference </ReferenceId> [0..1] ?
<AuthorizationId> Id </AuthorizationId> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="SenderBase">
<xsd:sequence>
<xsd:element name="LogicalId" type="Text" minOccurs="0"/>
<xsd:element name="Component" type="Text"/>
<xsd:element name="Task" type="Text"/>
<xsd:element name="ReferenceId" type="Reference" minOccurs="0"/>
<xsd:element name="AuthorizationId" type="Id" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): ServiceId

Super-types:xsd:string < Id (by extension) < ServiceId (by extension)
Sub-types:None

NameServiceId
Abstractno
DocumentationThe Service Id field identifies the particular service to or from which a message is being sent, e.g., an inventory service.
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
Id
</...>
Schema Component Representation
<xsd:complexType name="ServiceId">
<xsd:simpleContent>
<xsd:extension base="Id"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Signature

Super-types:None
Sub-types:None

NameSignature
Abstractno

Attributes

AttributeDescriptionRequirementBusiness Rules
qualifyingAgency Optional 

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules

XML Instance Representation
<...
qualifyingAgency="Text [0..1]"
>
Allow any elements from any namespace (strict validation). [0..1]
</...>
Schema Component Representation
<xsd:complexType name="Signature">
<xsd:sequence>
<xsd:any namespace="##any" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="qualifyingAgency" type="Text" use="optional"/>
</xsd:complexType>
top

Components (Complex Type): Tax

Super-types:None
Sub-types:None

NameTax
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
TaxTypeIdentifies the type tax. Required 
TaxDescriptionFree form text description of tax amount. Optional 
TaxAmountActual amount of tax paid. Optional 
UnitSalesTaxAmountUnit amount of sales tax. Optional 
TaxRateTax Percentage Rate Optional 
TotalTaxableAmountTotal taxble price Optional 
NonTaxableAmountTotal non-taxble price Optional 
TaxTypeIdTax type identification Optional 
TaxabilityIndDetermines whether the dealer wants to claim tax on the cost. Optional 

XML Instance Representation
<...>
<TaxType> TaxType </TaxType> [1] ?
<TaxDescription> TaxDescription </TaxDescription> [0..1] ?
<TaxAmount> TaxAmount </TaxAmount> [0..1] ?
<UnitSalesTaxAmount> UnitSalesTaxAmount </UnitSalesTaxAmount> [0..1] ?
<TaxRate> TaxRate </TaxRate> [0..1] ?
<TotalTaxableAmount> TotalTaxableAmount </TotalTaxableAmount> [0..1] ?
<NonTaxableAmount> NonTaxableAmount </NonTaxableAmount> [0..1] ?
<TaxTypeId> TaxTypeId </TaxTypeId> [0..1] ?
<TaxabilityInd> TaxabilityInd </TaxabilityInd> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="Tax">
<xsd:sequence>
<xsd:element name="TaxType" type="TaxType"/>
<xsd:element name="TaxDescription" type="TaxDescription" minOccurs="0"/>
<xsd:element name="TaxAmount" type="TaxAmount" minOccurs="0"/>
<xsd:element name="UnitSalesTaxAmount" type="UnitSalesTaxAmount" minOccurs="0"/>
<xsd:element name="TaxRate" type="TaxRate" minOccurs="0"/>
<xsd:element name="TotalTaxableAmount" type="TotalTaxableAmount" minOccurs="0"/>
<xsd:element name="NonTaxableAmount" type="NonTaxableAmount" minOccurs="0"/>
<xsd:element name="TaxTypeId" type="TaxTypeId" minOccurs="0"/>
<xsd:element name="TaxabilityInd" type="TaxabilityInd" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): TaxAmount

Super-types:xsd:decimal < Amount (by extension) < TaxAmount (by extension)
Sub-types:None

NameTaxAmount
Abstractno
DocumentationActual amount of tax paid.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="TaxAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): TaxDescription

Super-types:xsd:string < Description (by extension) < TaxDescription (by extension)
Sub-types:None

NameTaxDescription
Abstractno
DocumentationFree form text description of tax amount.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
language="Language [0..1] ?"
>
</...>
Schema Component Representation
<xsd:complexType name="TaxDescription">
<xsd:simpleContent>
<xsd:extension base="Description"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): TaxRate

Super-types:xsd:decimal < Percent (by extension) < TaxRate (by extension)
Sub-types:None

NameTaxRate
Abstractno
DocumentationTax Percentage rate.
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="TaxRate">
<xsd:simpleContent>
<xsd:extension base="Percent"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Term

Super-types:xsd:integer < Count (by extension) < Term (by extension)
Sub-types:None

NameTerm
Abstractno
DocumentationNumber of months of contract term
More information at: http://www.starstandard.org.

Attributes

AttributeDescriptionRequirementBusiness Rules
length Required 

XML Instance Representation
<...
length="TermLength [0..1]"
>
</...>
Schema Component Representation
<xsd:complexType name="Term">
<xsd:simpleContent>
<xsd:extension base="Count">
<xsd:attribute name="length" type="TermLength"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): TotalAmount

Super-types:xsd:decimal < Amount (by extension) < TotalAmount (by extension)
Sub-types:None

NameTotalAmount
Abstractno
DocumentationTotal price (cost + markup)
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="TotalAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): TotalTaxableAmount

Super-types:xsd:decimal < Amount (by extension) < TotalTaxableAmount (by extension)
Sub-types:None

NameTotalTaxableAmount
Abstractno
DocumentationTotal taxable price.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="TotalTaxableAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): UnitSalesTaxAmount

Super-types:xsd:decimal < Amount (by extension) < UnitSalesTaxAmount (by extension)
Sub-types:None

NameUnitSalesTaxAmount
Abstractno
DocumentationUnit amount of sales tax.
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="UnitSalesTaxAmount">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): Vehicle

Super-types:None
Sub-types:

NameVehicle
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
ModelManufacturer-assigned model code of vehicle - Usually available in the VIN number (use NCIC code) Optional 
ModelYearVehicle designated model year Optional 
ModelDescriptionDescriptive vehicle model name Optional 
MakeVehicle make code - Usually available in the VIN number (use NCIC code). Optional 

XML Instance Representation
<...>
<Model> Model </Model> [0..1] ?
<ModelYear> ModelYear </ModelYear> [0..1] ?
<ModelDescription> ModelDescription </ModelDescription> [0..1] ?
<Make> Make </Make> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="Vehicle">
<xsd:sequence>
<xsd:element name="Model" type="Model" minOccurs="0"/>
<xsd:element name="ModelYear" type="ModelYear" minOccurs="0"/>
<xsd:element name="ModelDescription" type="ModelDescription" minOccurs="0"/>
<xsd:element name="Make" type="Make" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): VehicleBase

Super-types:Vehicle < VehicleBase (by extension)
Sub-types:

NameVehicleBase
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
ModelManufacturer-assigned model code of vehicle - Usually available in the VIN number (use NCIC code) Optional 
ModelYearVehicle designated model year Optional 
ModelDescriptionDescriptive vehicle model name Optional 
MakeVehicle make code - Usually available in the VIN number (use NCIC code). Optional 
SaleClassClass of Sale Optional 
ConditionCondition of Vehicle - Example: Excellent, Good, Fair, Poor, Unknown Optional 
CertifiedPreownedIndIdentifies as a certified Pre-Owned Vehicle Optional 
VehicleNoteAny vehicle related notes Optional 
VINFederally defined 17 position vehicle identification number Optional 
DeliveryMileageOdometer reading of vehicle at time of delivery Optional 
VehicleStockDealer assigned vehicle stock number Optional 
TrimCodeManufacturer assigned trim code Optional 
DoorsQuantityNumber of doors on vehicle Optional 
BodyStyleManufacturer-assigned vehicle body style Optional 
InteriorColorVehicle Interior Color(s) Optional 
ExteriorColorVehicle Exterior Color(s) Optional 
TransmissionTypeVehicle Transmission type Optional 
OdometerStatusStatus of odometer at trade-in. Example:: Replaced, Tampered, Miles> 90,000, etc. Optional 
NonUSVehicleIndIndicates whether the vehicle was produced for the United States or not Optional 
VehicleDemoIndIndicates whether vehicle was ever a demo Optional 
LicenseNumberState License plate number of vehicle Optional 
BrandedInfoVehicle Branding Information Optional 
RestrictionIndIndication that vehicle has restrictions on its use Optional 
RestrictionDescriptionDescription of vehicle use restrictions Optional 
TelematicsServiceIndIndication whether Telematics Service Subscription is turned on Optional 

XML Instance Representation
<...>
<Model> Model </Model> [0..1] ?
<ModelYear> ModelYear </ModelYear> [0..1] ?
<ModelDescription> ModelDescription </ModelDescription> [0..1] ?
<Make> Make </Make> [0..1] ?
<SaleClass> SaleClass </SaleClass> [0..1] ?
<Condition> Condition </Condition> [0..1] ?
<CertifiedPreownedInd> CertifiedPreownedInd </CertifiedPreownedInd> [0..1] ?
<VehicleNote> VehicleNote </VehicleNote> [0..*] ?
<VIN> VIN </VIN> [0..1] ?
<DeliveryMileage> DeliveryMileage </DeliveryMileage> [0..1] ?
<VehicleStock> VehicleStock </VehicleStock> [0..1] ?
<TrimCode> TrimCode </TrimCode> [0..1] ?
<DoorsQuantity> DoorsQuantity </DoorsQuantity> [0..1] ?
<BodyStyle> BodyStyle </BodyStyle> [0..1] ?
<InteriorColor> InteriorColor </InteriorColor> [0..*] ?
<ExteriorColor> ExteriorColor </ExteriorColor> [0..*] ?
<TransmissionType> TransmissionType </TransmissionType> [0..1] ?
<OdometerStatus> OdometerStatus </OdometerStatus> [0..1] ?
<NonUSVehicleInd> NonUSVehicleInd </NonUSVehicleInd> [0..1] ?
<VehicleDemoInd> VehicleDemoInd </VehicleDemoInd> [0..1] ?
<LicenseNumber> LicenseNumber </LicenseNumber> [0..1] ?
<BrandedInfo> BrandedInfo </BrandedInfo> [0..1] ?
<RestrictionInd> RestrictionInd </RestrictionInd> [0..1] ?
<RestrictionDescription> RestrictionDescription </RestrictionDescription> [0..1] ?
<TelematicsServiceInd> TelematicsServiceInd </TelematicsServiceInd> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="VehicleBase">
<xsd:complexContent>
<xsd:extension base="Vehicle">
<xsd:sequence>
<xsd:element name="SaleClass" type="SaleClass" minOccurs="0"/>
<xsd:element name="Condition" type="Condition" minOccurs="0"/>
<xsd:element name="CertifiedPreownedInd" type="CertifiedPreownedInd" minOccurs="0"/>
<xsd:element name="VehicleNote" type="VehicleNote" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="VIN" type="VIN" minOccurs="0"/>
<xsd:element name="DeliveryMileage" type="DeliveryMileage" minOccurs="0"/>
<xsd:element name="VehicleStock" type="VehicleStock" minOccurs="0"/>
<xsd:element name="TrimCode" type="TrimCode" minOccurs="0"/>
<xsd:element name="DoorsQuantity" type="DoorsQuantity" minOccurs="0"/>
<xsd:element name="BodyStyle" type="BodyStyle" minOccurs="0"/>
<xsd:element name="InteriorColor" type="InteriorColor" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ExteriorColor" type="ExteriorColor" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="TransmissionType" type="TransmissionType" minOccurs="0"/>
<xsd:element name="OdometerStatus" type="OdometerStatus" minOccurs="0"/>
<xsd:element name="NonUSVehicleInd" type="NonUSVehicleInd" minOccurs="0"/>
<xsd:element name="VehicleDemoInd" type="VehicleDemoInd" minOccurs="0"/>
<xsd:element name="LicenseNumber" type="LicenseNumber" minOccurs="0"/>
<xsd:element name="BrandedInfo" type="BrandedInfo" minOccurs="0"/>
<xsd:element name="RestrictionInd" type="RestrictionInd" minOccurs="0"/>
<xsd:element name="RestrictionDescription" type="RestrictionDescription" minOccurs="0"/>
<xsd:element name="TelematicsServiceInd" type="TelematicsServiceInd" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): VehiclePassengers

Super-types:xsd:integer < Count (by extension) < VehiclePassengers (by restriction)
Sub-types:None

NameVehiclePassengers
Abstractno
DocumentationPassenger/seat capacity count of vehicle
More information at: http://www.starstandard.org.

XML Instance Representation
<...>
</...>
Schema Component Representation
<xsd:complexType name="VehiclePassengers">
<xsd:simpleContent>
<xsd:restriction base="Count"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): VehiclePrice

Super-types:xsd:decimal < Amount (by extension) < VehiclePrice (by extension)
Sub-types:None

NameVehiclePrice
Abstractno
DocumentationCustomer price of vehicle
More information at: http://www.starstandard.org.

XML Instance Representation
<...
currency="Currency [1]"
>
</...>
Schema Component Representation
<xsd:complexType name="VehiclePrice">
<xsd:simpleContent>
<xsd:extension base="Amount"/>
</xsd:simpleContent>
</xsd:complexType>
top

Components (Complex Type): VehiclePricing

Super-types:None
Sub-types:None

NameVehiclePricing
Abstractno
Documentation More information at: http://www.starstandard.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
VehiclePriceCustomer price of vehicle Required 
PriceExplanationExplanatory Note for Pricing Example: Anniversary Edition Optional 
VehiclePricingTypeDesignates type of pricing for vehicle transaction Optional 
PricingTypeSourceSource from which pricing type data originated (i.e. Blue Book, NADA, etc.) Optional 

XML Instance Representation
<...>
<VehiclePrice> VehiclePrice </VehiclePrice> [1] ?
<PriceExplanation> PriceExplanation </PriceExplanation> [0..1] ?
<VehiclePricingType> VehiclePricingType </VehiclePricingType> [0..1] ?
<PricingTypeSource> PricingTypeSource </PricingTypeSource> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="VehiclePricing">
<xsd:sequence>
<xsd:element name="VehiclePrice" type="VehiclePrice"/>
<xsd:element name="PriceExplanation" type="PriceExplanation" minOccurs="0"/>
<xsd:element name="VehiclePricingType" type="VehiclePricingType" minOccurs="0"/>
<xsd:element name="PricingTypeSource" type="PricingTypeSource" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): VehicleRemarketing

Super-types:None
Sub-types:None

NameVehicleRemarketing
Abstractno
DocumentationSTAR Version 2.0 - Draft
More information at: http://www.starstandards.org.

STAR Version 1.0, STAR approved 04/20/2005; OAGI approved 03/03/2005; effective date 07/04/2005
More information at: http://www.starstandards.org.

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
Header Required 
Vehicle Optional 

XML Instance Representation
<...>
<Header> ... </Header> [1]
<Vehicle> ... </Vehicle> [0..*]
</...>
Schema Component Representation
<xsd:complexType name="VehicleRemarketing">
<xsd:sequence>
<xsd:element ref="Header"/>
<xsd:element ref="Vehicle" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
top

Components (Complex Type): VehicleRemarketingHeader

Super-types:HeaderBase < VehicleRemarketingHeader (by extension)
Sub-types:None

NameVehicleRemarketingHeader
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
DocumentDateTimeIs the date and time the document was last created. This is not the date and time that the BOD message instance was created. Optional
DateTime fields must be formatted as XML Schema DateTimes in UTC/GMT format without offsets. Example: 2003-11-05T13:15:30Z
 
SecondaryPasswordSecondary password used to validate access to the dealer information Optional 
SecondaryDealerNumberIdentifies secondary dealer number if different than primary "Dealer Number" Optional 
DocumentIdSender (Source) Identification of this vehicle Required 
OrganizationIdMember identification number affiliate organization (i.e., association number) Optional 
ContractStartDateThe date the advertising contract starts Optional 
ContractExpirationDateThe date the advertising contract ends Optional 
ContractIdUnique identifier for the particular advertising activity Optional 

XML Instance Representation
<...>
<DocumentDateTime> DocumentDateTime </DocumentDateTime> [0..1] ?
<SecondaryPassword> SecondaryPassword </SecondaryPassword> [0..1] ?
<SecondaryDealerNumber> SecondaryDealerNumber </SecondaryDealerNumber> [0..1] ?
<DocumentId> DocumentId </DocumentId> [1] ?
<OrganizationId> OrganizationId </OrganizationId> [0..1] ?
<ContractStartDate> ContractStartDate </ContractStartDate> [0..1] ?
<ContractExpirationDate> ContractExpirationDate </ContractExpirationDate> [0..1] ?
<ContractId> ContractId </ContractId> [0..1] ?
</...>
Schema Component Representation
<xsd:complexType name="VehicleRemarketingHeader">
<xsd:complexContent>
<xsd:extension base="HeaderBase">
<xsd:sequence>
<xsd:element name="DocumentId" type="DocumentId"/>
<xsd:element name="OrganizationId" type="OrganizationId" minOccurs="0"/>
<xsd:element name="ContractStartDate" type="ContractStartDate" minOccurs="0"/>
<xsd:element name="ContractExpirationDate" type="ContractExpirationDate" minOccurs="0"/>
<xsd:element name="ContractId" type="ContractId" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Components (Complex Type): VehicleRemarketingVehicle

Super-types:Vehicle < VehicleBase (by extension) < VehicleRemarketingVehicle (by extension)
Sub-types:None

NameVehicleRemarketingVehicle
Abstractno

Data Elements and Components

Field/ComponentDescriptionRequirementBusiness Rules
ModelManufacturer-assigned model code of vehicle - Usually available in the VIN number (use NCIC code) Optional 
ModelYearVehicle designated model year Optional 
ModelDescriptionDescriptive vehicle model name Optional 
MakeVehicle make code - Usually available in the VIN number (use NCIC code). Optional 
SaleClassClass of Sale Optional 
ConditionCondition of Vehicle - Example: Excellent, Good, Fair, Poor, Unknown Optional 
CertifiedPreownedIndIdentifies as a certified Pre-Owned Vehicle Optional 
VehicleNoteAny vehicle related notes Optional 
VINFederally defined 17 position vehicle identification number Optional 
DeliveryMileageOdometer reading of vehicle at time of delivery Optional 
VehicleStockDealer assigned vehicle stock number Optional 
TrimCodeManufacturer assigned trim code Optional 
DoorsQuantityNumber of doors on vehicle Optional 
BodyStyleManufacturer-assigned vehicle body style Optional 
InteriorColorVehicle Interior Color(s) Optional 
ExteriorColorVehicle Exterior Color(s) Optional 
TransmissionTypeVehicle Transmission type Optional 
OdometerStatusStatus of odometer at trade-in. Example:: Replaced, Tampered, Miles> 90,000, etc. Optional 
NonUSVehicleIndIndicates whether the vehicle was produced for the United States or not Optional 
VehicleDemoIndIndicates whether vehicle was ever a demo Optional 
LicenseNumberState License plate number of vehicle Optional 
BrandedInfoVehicle Branding Information Optional 
RestrictionIndIndication that vehicle has restrictions on its use Optional 
RestrictionDescriptionDescription of vehicle use restrictions Optional 
TelematicsServiceIndIndication whether Telematics Service Subscription is turned on Optional 
OptionVehicle Remarketing Vehicle Options Optional 
TransmissionCodeTransmission Serial Number Optional 
DeliveryDateThe date of original retail vehicle sale Optional 
EngineNumberSerial number of the engine if vehicle not made for US sale Optional 
IgnitionKeyNumberVehicle Ignition Key Number Optional 
DoorKeyNumberDoor key number Optional 
ExteriorColorCodeVehicle exterior color code Optional 
InteriorColorCodeVehicle Interior color code Optional 
VehicleLocationIndicates the physical location of the vehicle Optional 
VehicleAcquisitionDateActual date vehicle was acquired by Dealership Optional 
VehiclePricingVehicle Pricing Optional 
TaxVehicle Tax Optional 
DealerVehicle Dealer Optional 
JobToDoRepairs to be done on vehicle Optional 
JobCompletedRepairs completed on vehicle Optional 
DamageDamage to the vehicle that needs repaired Optional 
TransmissionTypeNameName of transmission type (i.e., Hydromatic, Shiftronic, Manual, Automatic, etc.) Optional 
VehicleClassVehicleClass Optional 
FuelTypeType of vehicle fuel Optional 
EngineDescriptionText description of engine (e.g. dohc, 32 valves) Optional 
EngineConfigurationType of engine configuration Optional 
EngineInductionEngine induction Optional 
EngineDisplacementDisplacement of engine (i.e., amount of volume in the cylinders) Optional 
EngineCylindersEngine cylinder count Optional 
EngineHorsepowerEngine horsepower rating Optional 
DriveTrainIndicates whether the vehicle is 2 or 4 wheel drive (i.e., 2WD, 4WD, 4x4, 4x2) Optional 
DriveTypeDesignates Vehicle drive type Optional 
WarrantyVehicle warranty Optional 
FinancingVehicle financing Optional 
PreviousIndividualOwnerPrevious Individual owner of vehicle Optional 
PreviousOrganizationalOwnerPrevious organization owner of vehicle Optional 
ImageAttachmentContains vehicle photo and image information Optional 
VehiclePassengersPassenger/seat capacity count of vehicle Optional 
VehicleInspectionsDescription of inspections done to the vehicle Optional 
TireConditionCondition of tires Optional 
VehicleReceivedDateDate vehicle was received at the dealer Optional 
LastModificationDateDate vehicle was last modified in the sender's inventory Optional 
PreviousVehicleUsePrevious vehicle use, eg. ambulance, rental, etc Optional 
SoldDateDate vehicle was sold (useful when dealer wishes to show the car as "SOLD" on his website ) Optional 
CertificationIssuerName of issuer of vehicle certification, eg. honda, gm, government, etc Optional 
CertificationValueVehicle certification name, eg. gold, optimum Optional 
AdvertisingMedia advertising information Optional 
FinancingAvailableIndIndicates is someone is offering financing on this vehicle Optional 

XML Instance Representation
<...>
<Model> Model </Model> [0..1] ?
<ModelYear> ModelYear </ModelYear> [0..1] ?
<ModelDescription> ModelDescription </ModelDescription> [0..1] ?
<Make> Make </Make> [0..1] ?
<SaleClass> SaleClass </SaleClass> [0..1] ?
<Condition> Condition </Condition> [0..1] ?
<CertifiedPreownedInd> CertifiedPreownedInd </CertifiedPreownedInd> [0..1] ?
<VehicleNote> VehicleNote </VehicleNote> [0..*] ?
<VIN> VIN </VIN> [0..1] ?
<DeliveryMileage> DeliveryMileage </DeliveryMileage> [0..1] ?
<VehicleStock> VehicleStock </VehicleStock> [0..1] ?
<TrimCode> TrimCode </TrimCode> [0..1] ?
<DoorsQuantity> DoorsQuantity </DoorsQuantity> [0..1] ?
<BodyStyle> BodyStyle </BodyStyle> [0..1] ?
<InteriorColor> InteriorColor </InteriorColor> [0..*] ?
<ExteriorColor> ExteriorColor </ExteriorColor> [0..*] ?
<TransmissionType> TransmissionType </TransmissionType> [0..1] ?
<OdometerStatus> OdometerStatus </OdometerStatus> [0..1] ?
<NonUSVehicleInd> NonUSVehicleInd </NonUSVehicleInd> [0..1] ?
<VehicleDemoInd> VehicleDemoInd </VehicleDemoInd> [0..1] ?
<LicenseNumber> LicenseNumber </LicenseNumber> [0..1] ?
<BrandedInfo> BrandedInfo </BrandedInfo> [0..1] ?
<RestrictionInd> RestrictionInd </RestrictionInd> [0..1] ?
<RestrictionDescription> RestrictionDescription </RestrictionDescription> [0..1] ?
<TelematicsServiceInd> TelematicsServiceInd </TelematicsServiceInd> [0..1] ?
<Option> RemarketingOption </Option> [0..*] ?
<TransmissionCode> TransmissionCode </TransmissionCode> [0..1] ?
<DeliveryDate> DeliveryDate </DeliveryDate> [0..1] ?
<EngineNumber> EngineNumber </EngineNumber> [0..1] ?
<IgnitionKeyNumber> IgnitionKeyNumber </IgnitionKeyNumber> [0..1] ?
<DoorKeyNumber> DoorKeyNumber </DoorKeyNumber> [0..1] ?
<ExteriorColorCode> ExteriorColorCode </ExteriorColorCode> [0..1] ?
<InteriorColorCode> InteriorColorCode </InteriorColorCode> [0..1] ?
<VehicleLocation> VehicleLocation </VehicleLocation> [0..1] ?
<VehicleAcquisitionDate> VehicleAcquisitionDate </VehicleAcquisitionDate> [0..1] ?
<VehiclePricing> VehiclePricing </VehiclePricing> [0..*] ?
<Tax> Tax </Tax> [0..*] ?
<Dealer> DealerExtendedAddress </Dealer> [0..1] ?
<JobToDo> JobToDo </JobToDo> [0..*] ?
<JobCompleted> JobCompleted </JobCompleted> [0..*] ?
<Damage> RepairDamage </Damage> [0..*] ?
<TransmissionTypeName> TransmissionTypeName </TransmissionTypeName> [0..1] ?
<VehicleClass> VehicleClass </VehicleClass> [0..1] ?
<FuelType> FuelType </FuelType> [0..1] ?
<EngineDescription> EngineDescription </EngineDescription> [0..1] ?
<EngineConfiguration> EngineConfiguration </EngineConfiguration> [0..1] ?
<EngineInduction> EngineInduction </EngineInduction> [0..1] ?
<EngineDisplacement> EngineDisplacement </EngineDisplacement> [0..1] ?
<EngineCylinders> EngineCylinders </EngineCylinders> [0..1] ?
<EngineHorsepower> EngineHorsepower </EngineHorsepower> [0..1] ?
<DriveTrain> DriveTrain </DriveTrain> [0..1] ?
<DriveType> DriveType </DriveType> [0..1] ?
<Warranty> RemarketingWarranty </Warranty> [0..*] ?
<Financing> RemarketingFinancing </Financing> [0..*] ?
<PreviousIndividualOwner> IndividualPartyMinimal </PreviousIndividualOwner> [0..1] ?
<PreviousOrganizationalOwner> OrganizationPartyMinimal </PreviousOrganizationalOwner> [0..1] ?
<ImageAttachment> ImageAttachmentExtended </ImageAttachment> [0..*] ?
<VehiclePassengers> VehiclePassengers </VehiclePassengers> [0..1] ?
<VehicleInspections> VehicleInspections </VehicleInspections> [0..1] ?
<TireCondition> TireCondition </TireCondition> [0..1] ?
<VehicleReceivedDate> VehicleReceivedDate </VehicleReceivedDate> [0..1] ?
<LastModificationDate> LastModificationDate </LastModificationDate> [0..1] ?
<PreviousVehicleUse> PreviousVehicleUse </PreviousVehicleUse> [0..1] ?
<SoldDate> SoldDate </SoldDate> [0..1]