Added the field compensation to the existing Job DTD version
Changelog:
IADIF-job80.dtd changed 25.09.24
- Added COMPENSATION
Major changes to Job DTDs
New job DTD - IADIF-job80.dtd
FINN.no is releasing this DTD version with the aim of cleaning up and simplifying the data format of XML files to make the task of integrating with our API much easier for our partners in the jobs vertical.
Changes:
- Inlined HEAD and OBJECT_HEAD elements into a single file.
- Removed unused elements and attributes.
- Clearly marked fields as mandatory or optional.
- Updated comments to reflect existing restrictions.
Removed elements and attributes (do not use these anymore):
- From HEAD element: UPLOAD_REFERENCE, EMAIL_FEEDBACK
- From OBJECT_HEAD element: PROVIDER_REFERENCE, PROJECT_REFERENCE, VERSIONNO, SEGMENT
- From OBJECT_LOCATION element: ADDRESS2, ADDRESS3, ADDRESS4, MAP_COORDINATE
- From all job ad types (JOB, JOB_EXECUTIVE, JOB_PARTTIME): APPLICATION_ADDRESS, MOREINFO
- From OVERWRITE_MMO element MODUS: attribute option "urls"
Changes to mandatory/optional fields in all job ad types (JOB, JOB_EXECUTIVE, JOB_PARTTIME):
- GENERAL and SPECIALIZATION in the OCCUPATION element are now optional, but at least one of them is required: GENERAL if the value has no SPECIALIZATION, SPECIALIZATION otherwise
- COMPANY is now a mandatory singular element.
- APPLICATION_URL is now required.
- At least one JOB_CONTACT is now required.
New job-specific DTD for multimedia upload - IADIF-job_mmo1.dtd
Changes:
- Inlined HEAD and OBJECT_HEAD elements into a single file.
- Removed unused elements and attributes.
Removed elements and attributes (do not use these anymore):
- From HEAD element: UPLOAD_REFERENCE, EMAIL_FEEDBACK
- From OBJECT_HEAD element: PROVIDER_REFERENCE
- From OVERWRITE_MMO element: MODUS attribute options "urls" and "docs"
- From MMO_TYPE element: all options except "image" and "logo"
- From MO element: PRIORITY, VERSION_ID
Note: With the removal of PRIORITY from the MO element, images will be displayed in the order they appear in the XML file. To change the order, re-upload the full list.
New job-specific DTD for stopping ads - IADIF-job_stop1.dtd
Changes:
- Inlined HEAD and OBJECT_HEAD elements into a single file.
- Removed unused elements and attributes.
Removed elements (do not use these anymore):
- From IAD.IF.STOP element: PRODUCT
- From HEAD element: UPLOAD_REFERENCE, EMAIL_FEEDBACK
- From OBJECT_HEAD element: PROVIDER_REFERENCE
New job-specific DTD for response - IADIF-job_objectresponse1.dtd
Removed unused elements:
- From HEAD element: UPLOAD_REFERENCE
- From OBJECT element: VERSION,USERREFERENCE,SYSTEMREFERENCE
- From FILESTATUS element: PAYMENT
Note: SYSTEMREFERENCE was sent in the response previously, but it was a duplicate of the FINNKODE element.
Visual changes to the Jobs advert view
Read this pdf for the changes : Changes to advert page
Added field REFUGEES_WELCOME to Estate for rent ads
Changelog for https://www.iad.no/dtd/IADIF-estateforrent75.dtd
23.02.2024 Add REFUGEES_WELCOME
this is a field for making it easier for people and businesses renting out estates to show that they want to help refugees. In Norwegian we have called it FINN hjerterom. Read more here : https://hjelpesenter.finn.no/hc/no/articles/115001536449-Hjerterom-Hjelp-til-flyktninger
New size definitions and tags for all real estate ad types.
Changelog:
01.11.2023 Add new estate sizes USEABLE_AREA_I, USEABLE_AREA_E, USEABLE_AREA_B, OPEN_AREA
https://www.norsktakst.no/viktig-informasjon-om-arealmaling/
All updated DTDs can be found here : https://www.iad.no/dtd/
New URL for fetching predefined values for Job ads
The FINN.no system for letting users and external Job systems fetch predefined values for some of the fields in the XML (such as DURATION, OCCUPATION and INDUSTRY) was old and outdated.
Example of the old URL is https://www.finn.no/finn/referencevalue?adType=JOB&xmlCode=DURATION
We have made a new URL for this : http://www.finn.no/job/v1/referencevalue
An example for DURATION values would look like this :
https://www.finn.no/job/v1/referencevalue?xmlCode=DURATION
The new API has an identical interface, so the clients only need to change the URL in their configuration, but migrating to it will bring lots of opportunities.
While maintaining backward compatibility, we are adding one long awaited feature to the API.
So far clients had to retrieve OCCUPATION/GENERAL and OCCUPATION/SPECIALIZATION values in separate calls.
By calling the new endpoint with parameter OCCUPATION, they will receive everything together, with specializations nested under the general values.
A more detailed specification of the endpoint is available at: https://www.finn.no/job/v1/referencevalue/documentation
In addition, the new endpoint will soon provide even more job-specific features, such as:
- JSON format in addition to XML
- More selectable fields related to FINN products
Updates to all motor DTDs to unify the CONTACT_INFO fields
We noticed that we had differences in the CONTACT_INFO fields for the different DTDs for motor ad types.
Some had FAX, others did not. Some had URL and again others not. We have now unified all to have the same fields.
Now all have this : <!ELEMENT CONTACT (NAME?, PHONE?, MOBILE?, EMAIL?, URL?)>
(for cars, buses, mc, caravan,mobilehome, etc)
The updated DTDs can be found here : https://www.iad.no/dtd/
New version of the Bus DTD
we have updated the bus DTD (version 4)
The change is that the BUS_EQUIPMENT tag can now be duplicated so you can have as many equipment values as needed.
https://www.iad.no/dtd/IADIF-bus4.dtd
New version of the estateprojectsingle and estateprojectunit DTDs
we have published a new DTD version for the following ad-types.
Enkelt Prosjekt (IADIF-estateprojectsingle11.dtd)
Prosjekter til salgs enheter (IADIF-estateprojectunit14.dtd)
The change is that the field TOTAL_PRICE
has now been removed.
It is computed as sum of PRICE_SUGGESTION, COLLECTIVE_DEBT and SALES_COST_SUM
New version of the estateproject DTD
Changelog:
06.03.2023 : Added new optional field LOCAL_AREA_NAME.
https://www.finn.no/dtd/IADIF-estateproject14.dtd
New contruction (nybygg) release of leisure project and unit DTDs for testing
We have released new DTDs for leisure projects and leisure units.
The files can be found here : https://finn.no/dtd or in the article posted in the new contruction post.
IADIF-estateprojectleisure10.dtd
IADIF-estateprojectunitleisure10.dtd
NEW statistics API
We have launched a new statistics API where you can get statistics for classified ads.
This includes number of clicks, email notifications, push notifications and favorite markings. You can either get statistics for a single ad, or for all ads owned by an organisation.
Sign up and get access here : Statistics_API_information_page
NEW DTD for Realestate for sale
Here is the changeling:
26.10.2022 Add ESTATE_PRICE/ESTATE_TAX
https://www.iad.no/dtd/IADIF-estateforsale83.dtd
New DTD for Job
Here is the changelog :
IADIF-job79.dtd, 19.05.22
- Added WORKING_LANGUAGE
https://www.iad.no/dtd/IADIF-job79.dtd
Here are the predefined values that can de used :
https://www.finn.no/finn/referencevalue?adType=JOB&xmlCode=WORKING_LANGUAGE
New DTD for car
Here is the changelog :
- 28.03.2022 : Add EU_CHECK_LAST and EU_CHECK_NEXT
- 05.05.2022 : Add new CONDITION_REPORT_URL
https://www.iad.no/dtd/IADIF-car37.dtd
Ad types and corresponding property types
In FINN we have a connection between an adtype and the property types.
This applies to ads published from FINN Admin or the FINN web (private users).
What we see is that we do not have the same limitation for imported ads.
The consequences of this is that some ads are placed in the wrong place.
The most obvious example is cottage “hytte” that may be placed under “bolig til salgs” when they should have been placed under “fritidsbolig til salgs”.
This causes
- A bad user experience
- Wrong effect on ads / not high intention traffic
We want customers to publish their ads in the correct place.
In edge cases it is the realestate broker that must decide what is the best choice (helårs fritidsboliger etc)
We will start moving ads that are placed in the wrong place, but we want external systems (Meglersystemer etc) to send the correct data.
We will in a while stop ads that do not use the correct values, so it is essential that all systems check that they are sending correct data.
An overview of all adtypes and their corresponding property types can be found here :
https://docs.google.com/spreadsheets/d/1M_psOkfpDjYP1y-ozRyWlE8bk6GoOo1chLPfmTGtNd8/edit?usp=sharing
NEW DTD for uploading media (images/logo etc.)
Here is the changeling:
- 10.11.2020 : Bump HEAD tag to v4.0
- 18.12.2020 : Updated tag descriptions.
Add SEARCHKEY to MMO_TYPE attribute
- 16.11.2021 : Add floorplan as a mmo type
NEW DTD for Jobs
IADIF-job78.dtd, 29.10.21
- Added REMOTE_OPTIONS
Option for showing home office or part home office values.
Here are the options that can be used : https://www.finn.no/finn/referencevalue?adType=ESTATE_SALE&xmlCode=REMOTE_OPTIONS
New DTD for Car leasing
- 26.03.2020 : Update HEAD DTD reference to version 30.
Update OBJECT_HEAD DTD reference to version 22
Removed attribute REGISTRATIONTAX_INCLUDED, REREGISTRATION_EXEMPTION, VAT_INCLUDED from MOTOR_PRICE
Removed attribute PHONESALESRESERVATION from CONTACT
Removed elements MOTOR_PRICE/CURRENCY, MOTOR_PRICE/REGISTRATION, CONTACT/FAX
Added TRANSMISSION_SPECIFICATION, WHEEL_DRIVE_SPECIFICATION
- 12.10.2020 : Added CAR_CONDITION_DOC
New DTD for Job
We have published a new FINN Job DTD with several changes
Here are the changes and the new DTD name :
IADIF-job76.dtd,
- Removed SALARY
- Removed APPLICATION_MOBILE_URL
- Removed APPLICATION_LABEL
- Removed START_DATE
- Removed PLEASE_REFER
- Added APPLICATION_URL. The address of the application web page should use the new APPLICATION_URL field, instead of MOREINFO/URL.
Get the new DTD here : https://www.finn.no/dtd/IADIF-job76.dtd
Ny DTD for MC
<!-- MC_CONDITION replaces object model NEW_MC -->
<!ELEMENT MC_CONDITION (#PCDATA)> <!--Reference value NEW|USED -->
"Ny MC" vil ikke lengre ha en egen objektmodell, men vil heller bare være et felt i MC.
Ny DTD for bil
https://www.iad.no/dtd/IADIF-car33.dtd
Endringen er
02.03.2020 : Remove REGNO_HIDE attribute
Det betyr at det ikke lengre er mulig å skjule regnummer i annonsen.
Nye DTD filer for caravan og bobil
https://www.iad.no/dtd/IADIF-mobilehome-9.dtd
https://www.iad.no/dtd/IADIF-caravan-27.dtd
Endringer for caravan er :
12-02-2020 Added CARAVAN_LOCATION
Added CARAVAN_CONDITION
Removed EXTERIOR_LENGTH_CM
Added MOTOR_PRICE/REGISTRATION
Removed MOTOR_PRICE/CURRENCY
Added MOTOR_PRICE attribute REREGISTRATION_EXEMPTION
Removed MOTOR_PRICE attribute REGISTRATIONTAX_INCLUDED
Endringer for bobil er :
12-02-2020 Added MOBILE_HOME_CONDITION
Added MOTOR_PRICE/REGISTRATION
Removed MOTOR_PRICE/CURRENCY
Added MOTOR_PRICE attribute REREGISTRATION_EXEMPTION
Removed MOTOR_PRICE attribute REGISTRATIONTAX_INCLUDED
Ny DTD for jobb
Removed the APPLICATION_EMAIL tag. Use URL to external form with MOREINFO/URL instead.
FINN Eiendom - lademulighet som fasilitet.
FINN har nå lagt til lademulighet for elbil som fasilitet for bolig til salgs, bolig til leie, nybygg og fritidsbolig.
<xmlvalue>CHARGING</xmlvalue>
<displayvalue>Lademulighet</displayvalue>
FINN Eiendom - gammelt nybygg annonseformat fjernes helt - 8.Nov 2019
I 2012 lanserte FINN eiendom prosjektannonser med en boligvelger og enkelthus. I perioden etter har vi tilbudt kundene en kostnadsfri overgang til den nye modellen for eksisterende prosjekter.
De aller fleste har takket ja til dette tilbudet, men det ligger et fåtall aktive prosjekter/enkeltboliger (23) på FINN eiendom på den gamle modellen,.
Vi jobber nå med et større løft på vår nybyggvertikal, for å ikke forsinke dette arbeidet vil vi fase ut den gamle kategorien fra 1/1-2020. Disse vil da ikke lenger være søkbare hos oss.
Dette er annonser som bruker ESTATE_DEVELOPMENT elementet i vår IADIF-estateforsale DTD.
Vi vil informerer våre kunder om dette og gi de mulighet til å erstatte disse med nye annonser innen midten av desember.
Alle nye annonser skal overføres på disse elementene:
ESTATE_DEVELOPMENT_SINGLE - enkelthus
PROJECTDATA - prosjekter med boligvelger
Vi ser at det kommer noen annonser der megler endrer annonsetype f.eks. Fra bolig til salgs til Nybygg som bruker det gamle elementet. Dette må dere endre så fort som mulig.
Nye DTD filer for bil
https://www.finn.no/dtd/IADIF-car-leasing17.dtd
https://www.finn.no/dtd/IADIF-car32.dtd
https://www.finn.no/dtd/IADIF-newcar36.dtd
Nye DTD filer for leasing bil, camping, bobil og mc.
Leasingbil og MC har fått et felt for NBF.
Bobil og camping har fått mulighet for legge til at kjøretøyet har tilstandsrapport.
http://www.finn.no/dtd/IADIF-mobilehome-7.dtd
https://www.finn.no/dtd/IADIF-mc74.dtd
https://www.finn.no/dtd/IADIF-caravan-25.dtd
https://www.finn.no/dtd/IADIF-car-leasing16.dtd
Ny DTD fil for bobil og mc.
https://www.finn.no/dtd/IADIF-mobilehome-6.dtd
https://www.finn.no/dtd/IADIF-mc73.dtd
Ny DTD fil for eiendom på FINN.no: IADIF-estateforsale75
Ny DTD fil for eiendom på FINN.no: IADIF-estateforsale75.dtd
FINN.no har opprettet og tilgjengeliggjort nye felter for import og i admin.
Følgende endringer er gjort og produksjonssettes 11.12.2018:
Navn i admin: Totalpris
Feltnavn DTD:
<!--ELEMENT TOTAL_PRICE (#PCDATA)-->
Kommentar: Summert totalpris inkludert alle øvrige omkostninger ved boligkjøpet som f.eks. eventuell dokumentavgift
Navn i admin: Omkostninger
Feltnavn DTD:
<!-- sum of all property costs -->
<!--ELEMENT SALES_COST_SUM (#PCDATA)-->
Kommentar: Omkostninger summert
--------------------------------------------------------------------------------------------
Ny DTD fil for båt og nybåt.
http://www.iad.no/dtd/IADIF-boat42.dtd
Mulighet for å legge til video i annonsene.
Added VIDEO_URL for BOAT and NEWBOAT
---------------------------------------------------------------------------------------------
Ny DTD fil for bolig og fritidsbolig til salgs - endringer av boligannonsene på FINN.no: IADIF-estateforsale74
FINN.no har opprettet og tilgjengeliggjort nye felter for import og i admin.
Følgende endringer er gjort og produksjonssettes 15.08:
----------------------------------------------------------------------------------------------
Navn i admin: Kort om eiendommen
Feltnavn DTD:
<!-- Text - Short summary of the property→
<!ELEMENT ESTATE_SUMMARY (#PCDATA)>
Kommentarer: Dersom feltet er utfylt i meglersystemet og kommer med via importen vil FINN.no skjule teksten fra GENERAL_TEXT i annonsen. Meglersystemene legger til rette for at det er en begrensning på 800 tegn i dette feltet. FINN.no opprettholder importen av GENRAL_TEXT for å ivareta meglerkjedene som benytter FINN.no som grunnlag for publisering på egne hjemmesider, og for kunder som ønsker mer utfyllende tekst på FINN.
----------------------------------------------------------------------------------------------
Navn i admin: Lokalområde
Feltnavn DTD:
<!-- Text - Short name of local area - eg Birkelunden→
<!ELEMENT LOCAL_AREA_NAME (#PCDATA)>
Kommentar: Mulighet for å legge inn lokalområde for eiendommen. Feltet har en begrensning på 40 tegn i annonsen. Lokalområde vil vises før tittelen på eiendommen.
----------------------------------------------------------------------------------------------
Navn i admin: Se komplett salgsoppgave (URL)
Feltnavn DTD:
<!-- Link to web page (or pdf) where you can see the estate prospectus -->
<!ELEMENT PROSPECTUS_VIEW (#PCDATA)>
Kommentar: Feltet skal inneholde URL til nettside eller fil hvor brukeren finner komplett informasjon om eiendommen. URL’en kan peke til eiendommens objektside som inneholder all informasjon eller en PDF-fil.
----------------------------------------------------------------------------------------------
Navn i admin: Bestill komplett salgsoppgave (URL)
Feltnavn DTD:
<!-- Link to web page where to order/download the estate prospectus -->
<!ELEMENT PROSPECTUS_ORDER (#PCDATA)>
Kommentar: Feltet skal inneholde URL til en side hvor brukeren ved å legge inn kontaktinformasjon kan bestille en nedlastbar versjon av den komplette informasjonen om eiendommen.
----------------------------------------------------------------------------------------------
Navn i admin: Vesentlige opplysninger om eiendommen
Feltnavn DTD:
<!-- Text - Important information goes here -->
<!ELEMENT ESSENTIAL_INFO (#PCDATA)>
Kommentar: Feltet skal inneholde informasjon om vesentlige forhold om eiendommen (feil og mangler). Kunder som bruker estate_summary fyller ikke ut noe her
----------------------------------------------------------------------------------------------
Navn i admin: Tittel
Feltnavn DTD:
<!--ELEMENT HEADING (#PCDATA)-->
Kommentar: Det er lagt til en begrensning på 120 tegn for tittelfeltet på annonsen.
----------------------------------------------------------------------------------------------
Panoramic /virtual viewing image in Realestate ads
The tag is called :
<VIRTUAL_VIEWING_URL> and you can send an URL to the image in this tag.
The tag is available in the latest Realestate DTD.
https://www.finn.no/dtd/IADIF-estateforsale78.dtd
Only these providers of virtual viewing are allowed :
https://cdn.diakrit.com/product/panorama/
https://tours.h5property.com/tour/
https://www.inviso.no/360/
https://my.matterport.com/show/
https://tours.stormcam.no/stormcam/tours/
https://youriguide.com
Stormcam
Imageday / pixxip.no
Superoh Shots
Image Desktours
Kuula.co / Robert Rudnik Fotograftjenester
Pannomax Studio
Updates for the Agri-tool and Threshing machine dtd files
It is now possible to specify VAT_INCLUDED (yes | no) for agri-tool and threshing machine adverts.
This is includes in the new dtd files http://www.iad.no/dtd/IADIF-threshing_machine-21.dtd and
http://www.iad.no/dtd/IADIF-agri_tool-22.dtd
The files can also be downloaded from the DTD & example XML file page.
Change notification: «variant» field on FINN Motor
Dear customer of FINN motor and dear provider of a system/solution for publishing car ads on FINN.no
FINN cars has together with NBF (faggruppe bilsalg) decided to reduce the allowed number of signs in the «variant” field to 55. Moreover, we have decided to clarify what advertisers are allowed to write in this field.
The changes will be effective of February 1, 2017 and will include all cateogires and sub categories on “Bil til salgs”:
- Biler i Norge
- Biler i utlandet
- Bobiler
- Campingvogner
- Varebiler i Norge
- Varebiler i utlandet
This decision is made based on user testing conducted by FINN, showing that «viriant» fields with over 55 signs are confusing to the users.
From February 1, 2017 it will only be possible to write a maximum of 55 signs in the «variant» field. All charactes beyond number 55 will not be visible on the live ad on FINN. We emphasize that this change will affect all new and existing ads, effective of February 1, 2017.
Furthermore, we emphasize that the «variant” field is meant for an elaboration of the type of car, not a selling text or other words not intended for describing the type of car which is being advertised. It is allowed to write single words to describe, e.g.: engine size, horsepower, wheel drive, gearbox, equipment level/package (S-line, Summum, Highline and so on), Etc.
We ask all system providers to adjust their ad insertion so that no ads coming from your system to FINN.no contains more than 55 characters.
We emphasize, once more, that we are making these changes in order to improve both user experience and ad effect on FINN motor.
Kind Regards,
FINN.no AS – motor team
Using the <PROVIDER> tag and providerID
FINN Motor demands either registration number og VIN on all car ads from March 3, 2017
Dear customer/partner,
FINN have decided to demand either a Norwegian registration number or a vehicle identification number (VIN/Chassis number) in order for a user/partner to publish a car classified ad on FINN.
The change will be effective of March 3, 2017 according to FINNs notification obligation of such changes.
The reason for this change is related to repeated occurrences where private- or professional users of FINN advertise cars which are not in their possession on FINN motor. This is a violation of FINNs advertising rules.
This change will be effective for all users of FINN.no, both private users and car dealers, regardless of the method for publishing ads on FINN motor. The change will incur that it will not be possible to publish a car ad on FINN.no without typing in either a valid, Norwegian registration number or a vehicle identification number (VIN) in the ad insertion scheme.
From March 1, 2017 the following rules will apply to all ads on «bil til salgs» on FINN:
1. The advertiser must enter either the Norwegian registration number or the vehicle identification number (VIN) of the car her or she is selling
2. The field «chassisnummer» will be mandatory for all advertisers (this field gets auto-filled if the user enters a valid Norwegian registration number).
3. The field «chassisnummer» must contain at least 8 signs – numbers and letters (veteran cars have a 8-sign VIN).
Ads that don’t fulfil these rules will not be published.
If you are publishing cars via a third party system like e.g. CARWEB2, your system provider has been informed about these changes and are responsible for adjusting the system accordingly
For third party system providers, we ask that you adjust your ad insertion so that all ads coming from your system contains a «chassisnummer» (Vehicle identification number).
Our goal is that these changes will make it even safer for buyers and sellers to purchase and sell cars via FINN.no
Kind regards,
FINN.no AS – motor department
Important update on feedback/ object respons (31.05.2016)
We at FINN.no are making and important update on the object response (feedback on transferred files to FINN.no).
We would like to inform you that we are making the url to our new statistics module available in the object response. You will find this url in the new tag called STATISTICS_URL.
If you already are receiving object response as xml you must make sure that the xml don't break when the changes is put into production.
Here is an example on how the new response will look like:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE FINN.IF.OBJECTRESPONSE SYSTEM "http://www.finn.no/dtd/FINNIF-objectresponse11.dtd">
<FINN.IF.OBJECTRESPONSE>
<HEAD PARSESTATUS="ok">
<PARTNER>MypartnerIDhere</PARTNER>
<IMPORTTYPE>STORING AD
</IMPORTTYPE>
</HEAD>
<OBJECT STATUS ="ok">
<ORDERNO>123-order-123</ORDERNO>
<VERSION>1</VERSION>
<USERREFERENCE>A userreference here </USERREFERENCE>
<URL>http://www.finn.no/finn/object?finnkode=88888888</URL>
<STATISTICS_URL>http://www.finn.no/a-new-URL-to-our_statistics</ STATISTICS_URL>
</OBJECT>
</FINN.IF.OBJECTRESPONSE>
This is an example on how it will look visually:
Here you can see the new DTD for Object response:
<!-- DOCTYPE IAD.IF objectresponse Finntech
Changelogg:
23.06.2006 Iad-version created EAS
21.02.2008 Added systemreference EAS
-->
<!-- All objects are unique identified by partner + orderno -->
<!ELEMENT IAD.IF.OBJECTRESPONSE (HEAD, OBJECT*,FILESTATUS)>
<!-- HEAD consists of an identification of a partner -->
<!ELEMENT HEAD (PARTNER,PROVIDER?,UPLOAD_REFERENCE?,IMPORTTYPE,PROCESSEDTIME,SOURCE?)>
<!ELEMENT PARTNER (#PCDATA)>
<!ELEMENT PROVIDER (#PCDATA)>
<!ELEMENT UPLOAD_REFERENCE (#PCDATA)>
<!ELEMENT IMPORTTYPE (#PCDATA)>
<!ELEMENT PROCESSEDTIME (#PCDATA)>
<!ELEMENT SOURCE (#PCDATA)>
<!-- The element OBJECT consists of a reference number, -->
<!-- this number is unique for each partner -->
<!ELEMENT OBJECT (ORDERNO,VERSION?,USERREFERENCE?,SYSTEMREFERENCE?,ERRORMESSAGE*,IMAGE*,URL?,STATISTICS_URL?)>
<!ATTLIST OBJECT
STATUS (ok | fault) #REQUIRED>
<!-- ORDERNO is the partners own reference number, e.g. internal ID in a backoffice solution -->
<!ELEMENT ORDERNO (#PCDATA)>
<!-- VERSION is set by the partner and is not changed by importing system -->
<!ELEMENT VERSION (#PCDATA)>
<!-- USERREFERENCE is a reference for the partner, allow not unique references -->
<!ELEMENT USERREFERENCE (#PCDATA)>
<!-- SYSTEMREFERENCE is a unique reference within the iad platform -->
<!ELEMENT SYSTEMREFERENCE (#PCDATA)>
<!-- ERRORMESSAGE returns errormessages,warnings and infomessages -->
<!ELEMENT ERRORMESSAGE (ELEMENTNAME, VALUE?,MESSAGE)>
<!ATTLIST ERRORMESSAGE
ERRORLEVEL (fatal | error | warning | info) #REQUIRED>
<!ELEMENT ELEMENTNAME (#PCDATA)>
<!ELEMENT VALUE (#PCDATA)>
<!ELEMENT MESSAGE (#PCDATA)>
<!ELEMENT IMAGE (IMAGENAME, IMAGEMESSAGE?)>
<!ATTLIST IMAGE
STATUS (ok | fault) #REQUIRED>
<!-- IMAGENAME is the partners name on the image -->
<!ELEMENT IMAGENAME (#PCDATA)>
<!ELEMENT IMAGEMESSAGE (#PCDATA)>
<!-- URL is a direct link to the object on the website -->
<!ELEMENT URL (#PCDATA)>
<!ELEMENT STATISTICS_URL (#PCDATA)>
<!-- HEAD consists of an identification of a partner -->
<!ELEMENT FILESTATUS (PARSEMESSAGE*)>
<!ATTLIST FILESTATUS
PARSESTATUS (ok | fault) #REQUIRED
NUMBEROFOBJECTS CDATA #IMPLIED>
<!ELEMENT PARSEMESSAGE (#PCDATA)>
<!ATTLIST PARSEMESSAGE
ERRORLEVEL (fatalerror | error | warning) #REQUIRED>
If you have any questions please contact import@finn.no