CAR Report - xsl specification

Comprehensive Auto Report (CAR) V2.0 Specification
Functional Specification Document
Table Of Contents
Date Last Modified: 9/7/2014 1 of 20

CAR Overview
Overview
Car will have a main Xsl sheet which will be used to generate the CAR Template designed look. This will
include the main content/template section, a header section, menu nav bars, and a footer section.
Header Section
The Header section will contain the Title Graphic (Comprehensive Auto Report) and the year make model
and trim of the vehicle. The CarXml data points are listed below.
CARXml data point(s):
CAR Data Point Item CARXml Node Reference
Year vt:V node vt:VY attribute
Make vt:V node vt:VMa attribute
Model vt:V node vt:VMo attribute
Trim vt:V node vt:VTr attribute
Work To Be Done:
· None, Required CARXml elements available.
Navigation Bar
The CAR Navigation Bar will consist of 8 graphical elements corresponding to the 8 template sections in
CAR. Each of these elements will consist of TWO graphics (a primary graphic and a rollover graphic).
These will be located in the /images directory.

The Javascipt actions (onmouseover, onmouseout, other) will be coded into the Xsl template to be called
upon rendering.
Footer
The Footer section will contain a repeat of the Navigation Bar (as displayed at the top of each CAR
template page) and a footer content section. This content will be consist of 4 elements.
1. Area 1: Left most graphic – Contact Mota image (contact information)
2. Area 2: Link section (what is mota? What makes us different, find out more?) Links displayed as
defined on CAR_V5.0.pdf but subject to change.
3. Area 3: Open Section, as yet undefined
4. Area 4: Tell a Friend Form Section. Form will be coded into xsl with proper action page link to
execute submit functionality. Form consists of 3 form elements:
a. Email to a friend
b. Your email
c. Submit Button

Brochure Section
Overview
The Brochure section displays the Mota 2.0 EBay Listing Template (currently being finalized design/layout
and review). This template generates the EBay listing html for the current vehicle and display it in the
Content Section area. Therefore, this information will be generated by a SEPARATE XSL file and
“included” in that area when the page is called.
XSL Template File Name: CARBrochureTemplate.xsl

Inspection Section
Overview
The CAR Inspection Report section displays the results of a VIS/DataScan inspection report in the format
define for the CAR Template section (as defined in CAR_V5.0.pdf). This data is retrieved automatically
from the VIS server and the transformed and incorporated into a vehicle’s CARXml. The CARXml data
(in the vt:CR nodeSet) will then be read and formatted for display in CAR.
XSL Template File Name: CARInspectionReport.xsl
The following primary content sections are defined in CAR for the inspection report
Glamour Shot
The primary vehicle listing photo (known as the Glamour Shot) will be displayed in the top left area of the
Inspection Report template.
Glamour Shot Image: vt:V/vt:VPs/vt:VP vt:VPN="Overview"
Work To Be Done:
· Glamour Shot Image node element defined in CARXml
· Glamour Shot Data included in CARXml
· Process to Add Glamour Shot Node and Data during CARXml build must be created and
incorporated into existing system.
Tire Tread Measurements

The tire tread measurements section displays the wear amount (as a percentage) of the 5 (if spare tire
exists) or 4 tires (no spare) of the current vehicle. The HTML will be formatted as defined in the CAR
Design Spec and each tread wear amount will be calculated and displayed in the corresponding area on
the Tire Tread graphic.
Left Front Tire Wear: Not currently directly available in CARXml
Right Front Tire Wear: Not currently directly available in CARXml
Left Rear Tire Wear: Not currently directly available in CARXml
Right Rear Tire Wear: Not currently directly available in CARXml
Spare Tire Wear: Not currently directly available in CARXml
Work To Be Done:
· A node structure for all tire wear data elements will need to be created
· Process to calculate them and build them into the CARXml will need to be defined.
Wear & Tear
The Inspection Report Wear and Tear section is a graphical display of all DAMAGE photos that exist for
this vehicle. These images are available in the vt:VP section of the CARXml. There is no pre-defined
order to display these images and thus they can be displayed in the order listed in the CARXml.
An important functional element of this section must be noted. This functionality will display a large
“HOVERING” enlargement of a damage photo when a user’s mouse is placed over that image. This
functionality can be viewed for example in the CAR design specification.

Damage Photo Item: vt:VPs section, vt:VP node, vt:VPU attribute, check xslt condition:
VPN=”damage”
Work To Be Done:
· The html/javascript coding to display the enlarged version of a damage photo and have it
“HOVER” over the CAR template needed to be further defined and specified for implementation.
Inspection Overview
The inspection overview section is displayed in the top right section of the CAR Inspection Report
template. The purpose of this content is to summary the general properties of the vehicle for the user.
General descriptive data points and vehicle properties are included in this section.
Xsl Process Definition/Pseudo Code
The process to read the CARXml node structure and incorporate this data into CAR is the following:
VIN vt:V node vt:VIN property
Inspection Number N/A
Odometer Reading Vt:V node vt:VMi
Data Inspected N/A
City, State N/A
Transmission Type N/A
Drive Type N/A
Displacement N/A

# of Cylinders N/A
Body Type N/A
Exterior Color N/A
Interior Color N/A
Work To Be Done:
While all required section data points are available in our local DB (actual data point location varies
between tables and DBs and will require additional identification/specification), several data elements are
not currently available in the CARXml. Therefore, the following tasks must be completed to allow the
incorporation of this data into CAR.
· Mapping of local DB data fields to Required CARXml data (define in DB where required data for
missing points is located.
· Process to obtain data from DB for inclusion into CARXml during build process
· Definition of node elements/trees to store missing CARXml data points
· Process to create node structure during build CARXml process.
· Identification of data point storage in local db system (Database, table/field name, data type)
Primary Group Display and Description
The mota CARXml stores vehicle data into content sections broken into 3 levels of content. The
‘PRIMARY’ level consists of the vehicle content area. There are 3 areas, Exterior, Interior, and
Mechanical. Each of these sections has 1 or more ‘SECONDARY’ sections. These sections will be listed
in the section details below. These secondary sections are then further divided into ‘TERTIARY’ sections
correlating to sub-areas of the secondary section. It is the tertiary sections that contain the actual data
points to use/display on the CAR inspection report.

CARXml Data Point(s)
Primary Section Mechanical vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Mechanical’]
Primary Section Exterior vt:CR/vtLIGs/vt:LIPG[vt:LIGN= Exterior]
Primary Section Interior vt:CR/vtLIGs/vt:LIPG[vt:LIGN= Interior])
Work To Be Done:
· The Tertiary Structure for CARXml line item group data has been implemented and is available
for CAR use.
Mechanics
The mechanics section is one of three primary line item groups. This information is stored in its own line
item group in the CARXml (vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Mechanical’]). This nodelist section is further
broken down into 3 ‘Secondary’ Sections in the following nodelist group
(vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Mechanical’]/vt:LISGs/vt:LISG). These sections are identified by the
attribute LIGN as follows: Engineering, Fluid Levels, and Performance.
Engineering Section vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Engineering’]
Fluid Levels Section vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Fluid Levels’]
Performance vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Performance’]
Tertiary Section(s) vt:CR/vtLIGs/vt:LIPG[vt:LIGN= Interior]/vt:LISGs/vt:LISG[LIGN=’Sec
Group Name’]/vt:LITG/vt:LIGN=[‘Ter Group Name’]

Work To Be Done:
· Process to read through Primary/Seconary/Tertiary structure defined and implemented.
· Required CARXml data points and build processes have been defined and are implemented for
CAR use.
Exterior
The exterior section is one of three primary line item groups. This information is stored in its own line item
group in the CARXml (vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Exterior’]). This nodelist section is further broken
down into 5 ‘Secondary’ Sections in the following nodelist group
(vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Exteriorl’]/vt:LISGs/vt:LISG). These sections are identified by the attribute
LIGN as follows:
Exterior Group Secondary Sections: Collision, Front End, Rear, Side Panels, Tires and Wheels
Secondary Section vt:CR/vtLIGs/vt:LIPG[vt:LIGN= Interior]/vt:LISGs/vt:LISG[LIGN=’Sec
Group Name’]
* Sec Group name as defined above
* Sec Group Name as defined above, Ter Group Name(s) available
in CARXml
Work To Be Done:
CAR use.

Interior
The interior section is one of three primary line item groups. This information is stored in its own line item
group in the CARXml (vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Exterior’]). This nodelist section is further broken
down into 9 ‘Secondary’ Sections in the following nodelist group
(vt:CR/vtLIGs/vt:LIPG[vt:LIGN=’Exteriorl’]/vt:LISGs/vt:LISG). These sections are identified by the attribute
LIGN as follows:
Interior Group Secondary Sections: Audio, Climate Control, Convenience, Dashboard and Trim,
Odometer, Release Switches, Safety, Standard Features, Steering Column
Engineering Section vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Engineering’]
Fluid Levels Section vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Fluid Levels’]
Performance vt:CR/vtLIGs/vt:LIPG[vt:LIGN=
Interior]/vt:LISGs/vt:LISG[LIGN=’Performance’]
Work To Be Done:
CAR use.

Vehicle History Report Section
Overview
The vehicle history report is a stand-alone HTML download that we obtain from Experian. Experian
provides multiple formats for requested vehicle history data. The primary format is a Xml file which is
used to review and evaluate the results of the vehicle history request. A separate HTML file is also
provided and downloaded locally to our servers during the GetVehicleHistoryWorkFlowStep process.
This HTML file will be read entirely and displayed in its unmodified version in the CAR GUI shell.
Vehicle History Report HTML string vt:VH node vt:VHU element (contains path to HTML file)
Work To Be Done:
· Xsl template/Code process to read HTML from file and display on CAR (encapsulated in the CAR
shell). NOTE: this process has been developed to some degree, still need to determine what
reuse, modification and integration work is left to be done.

Auto Biography Section
Overview
CAR will contain a section to display the seller auto-biography information gathered during the Fsbo
WorkFlow process. The CAR auto-biography displays THREE groups of information.
· Condition & Maintenance (Vehicle Details): Presently this information is gathered in Step 3 (Enter
Vehicle Details) and stored in our local DB in the UnitVehicle Table (field UnitVehiclesXml).
· Features & Options:
· Free Seller Audio Description (IVR):
Condition & Maintenance Section
SellerVehicleDetails Root Node vt:SVD (SellerVehicleDetails)
Overall Condition vt:SVD node vt:
Interior Condition vt:SVD node vt: VDIC
Exterior Condition vt:SVD node vt: VDEXC
Accident Status vt:SVD node vt: VDAD
Engine and Transmission vt:SVD node vt: VDEC
Starts Regularly vt:SVD node vt: VDSR
Check engine light ??

AC working vt:SVD node vt: VDAC
Heater working vt:SVD node vt: VDHW
Passed Emissions Test vt:SVD node vt: VDPET
Power Options working vt:SVD node vt: VDPOW
Breaks/Rotors Replaced Last vt:SVD node vt: VDLTRB
Last Oil Change ??
Vehicle Driven Daily vt:SVD node vt: VDCTW
Mostly Highway Miles vt:SVD node vt: VDMHC
Detectable Odors vt:SVD node vt: VDDO
Spare Key Available vt:SVD node vt: VDHEK
Service Records Available vt:SVD node vt: VDHSR
Owner’s Manual Available vt:SVD node vt: VDHOM
Car Jack/Tire Tools Available ??
Spare Tire Available vt:SVD node vt: VDSTE
XmlNode spareInfoXmlNode = "VDSI" – needs to be identified
Features & Options Section
The aftermarket parts and standard features are both stored in the same CarXml node structure. The
code will read the FOD (Feature Option Description Attribute) and determine the option and display it
correctly on the CAR HTML Page.
Root Node: vt:FOs
Navigation System vt:FOs vt:FO node vt:FOD attribute = “NavigationSystemCheckBox”
Telematics vt:FOs vt:FO node vt:FOD attribute = “TelematicsCheckBox”
Satellite Radio vt:FOs vt:FO node vt:FOD attribute = “SatelliteRadioCheckBox”
Awd4wd vt:FOs vt:FO node vt:FOD attribute = “Awd4wdCheckBox”

TrailerHitch vt:FOs vt:FO node vt:FOD attribute = “TrailerHitchCheckBox”
Sunroof/Moonroof vt:FOs vt:FO node vt:FOD attribute = “SunroofMoonroofCheckBox”
CD Changer vt:FOs vt:FO node vt:FOD attribute = “CdChangerCheckBox”
Leather Seats vt:FOs vt:FO node vt:FOD attribute = “LeatherSeatsCheckBox”
Aero Sport Package vt:FOs vt:FO node vt:FOD attribute =
“AeroSportPackageCheckBox”
Premium Audio System vt:FOs vt:FO node vt:FOD attribute =
“PremiumAudioSystemCheckBox”
RoofRackCheckBox vt:FOs vt:FO node vt:FOD attribute = “RoofRackCheckBox”
Additional Features and Options can be read (looped through) in the vt:FOs node list and, when
determined NOT to be an AFTERMARKET part, can be displayed in the Standard Features section of the
Features & Options section.
Free Audio Description IVR Section
CarXml indication of whether the user entered a phone number for an IVR clip. If true, display IVR
Section information (Play Seller IVR Clip Form)
Work To Be Done:

KBB (Kelly Blue Book) Section
Overview
TBD
· Load Car.xsl global template
· Load CarKBBSection.xsl section template
· Apply Xsl transformations to generate required CAR Html output
TBD
Work To Be Done:
· TBD

mota Section
Overview
The CAR mota page contains static content relating to the mota online automotive sales process and any
pertinent information to better inform a user about Mota as an organization. This content will be static and
should be coded directly into the Xsl template that generates this page.
· Load CarMotaSection.xsl section template
Presently, the content for this page will be static authored content directly coded into the Xsl files.
Therefore, no CARXml or other dynamic data is required to render this page.
Work To Be Done:
· The content to be coded and generated in this section has yet to be finalized and is pending.
Mark Liu is managing the completion of this information

Warranty Section
Overview
The CAR warranty section page displays static content describing the warranty program that is provided
with the purchase of this vehicle. The content and format of this information is being generated by Mark
Liu and it currently pending. One important functional requirement to note is that this section should be
displayed conditionally, and only if the vehicle has a warranty provided. If this is not the case, this section
should be omitted.
· DETERMINE if warranty is available/provided for this vehicle
· If (TRUE)
o Load Car.xsl global template
o Load CarWarrantySection.xsl section template
o Apply Xsl transformations to generate required CAR Html output
· If (FALSE)
o Handle CAR output to omit this section from display
o NOTE: This method will most likely be handled at an earlier stage to all for global
handling of this omission.
Does Warranty Exist Need to be defined/added to CARXml
Work To Be Done:
Mark Liu is managing the completion of this information

· Check for Warranty existence and inclusion of warranty section (globally and page section) needs
to be coded.

Terms & Conditions Section
Overview
The CAR Terms & Conditions page will display very important statically authored and coded vehicle seller
terms & conditions relating to the terms of sale, legal issues, liability concerns, and other contractual and
commercial stipulations that govern mota’s provision of this service and the boundaries of its relationship
with its customers. This content is defined on the mota.net corporate site. The final copy for CAR,
however, is still being determined between Jason Stagliano/Mark Liu.
· Load CarTermsAndConditions.xsl section template
Presently, the content for this page will be static authored content directly coded into the Xsl files.
Therefore, no CARXml or other dynamic data is required to render this page.
Work To Be Done:
Jason Stagliano/Mark Liu is managing the completion of this information.

CAR Report - xsl specification

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (13)

Similar to CAR Report - xsl specification

Similar to CAR Report - xsl specification (20)

More from Gregory Weiss

More from Gregory Weiss (20)

Recently uploaded

Recently uploaded (20)

CAR Report - xsl specification