OFFICE FOR HARMONIZATION IN THE INTERNAL MARKET (TRADE MARKS AND DESIGNS) CTM Download – Version 2 FUNCTIONAL DOCUMENTATION Draft 19/01/2004 IT Division Development Service Date: 20/08/2001 Dept: EDP Author: Noam Borovoy Title: IDI - Technical Specifications Page: 2 of 19 Code: IDI - TS Status: Version: 1.0 Reviewed by: Eamonn Kelly Document revisions: User Requirements: Version Number Date Author 1.0 Draft 19/01/2004 David Robertson Comments Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 3 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu Table of Contents 1 INTRODUCTION ..........................................................................................................................4 2 CHARACTERISTICS OF XML USED.......................................................................................4 3 XML SCHEMA FOR THE DISTRIBUTION OF THE DATABASE ......................................5 4 APPENDIXES ..............................................................................................................................18 Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 4 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 1 Introduction This document, which is part of the project “CTM-Download”, aims at describing the XML schema generated by the CTM Download Version 2.0(IDI) database extraction process. The previous version of CTM Download is deemed obsolete and a move was made to create a new data definition using XML as the standard. The distributed files will follow the XML standard (Extensible Markup Language) and, therefore they will be easily processed by any software able to deal with XML format. An XML parser was used to verify the correctness of the XML schemas contain herein this document. The database extraction will be broken down into different types of entities. These are listed below: • applicants • representatives • bulletin • marks(ctms) • oppositions • incremental A complete transmission will contain one or several files of each type of file(for instance ctms 1 to 10000 might appear in a first file, from 10001 to 20000 in the next file, etc...). The last type of file will be used for the incremental distribution of the modifications in the database. It will contain all the information, including that concerning the marks, that concerning the representatives, the applicants or the bulletins. The transmission will also contain one or several files. 2 Characteristics of XML used 2.1 2.1.1 XML Specific characteristics Namespaces The schema used to define the extraction will be linked to a namespace. Namespaces are used to give entities unique names so that they can be identified. The complete IDI schema is made up of re-useable modular components. Each component represents an entity in the context of the OHIM business areas and tend to be identified by their own namespace. 2.1.2 References References are used in XML files in order to replace in the texts characters which have a meaning in XML (Ex : <, &). 2.2 Special characters Some control characters may appear in the textual data of the XML file produced. Some of them may raise a parsing error if they are interpreted by an XML parser. In order to avoid this problem, the textual data is escaped and any special characters are replaced by their encoded equivalent. The table below shows the equivalence of given characters: Character Equivalent & & < < > > Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 5 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu Example : in a transmission the fictitious word mark representation “A is < & B is >” will be transmitted the following way : <word><representation>A is < & B is ></representation></word> 2.3 Codes Pages All data is encoded in UTF8. 3 XML Schema for the distribution of the database This chapter describes the XNL schema, that is, the format of the files that will be transmitted. An example of each type of file is provided in the annex (See chapter 4.5, 4.6, 4.7, 4.8, 4.9). These examples give a concrete application of the format described here and should help for a better understanding. 3.1 Transmission The schema can be used from two distinct transmissions: • complete • differential The first one allows the distribution of the complete database and the other the distribution of the incremental database. These two transmissions, although having very different functionalities, have many common structures. This is why a single schema is used in order to factorize the structures that both transmissions use and to optimise the treatments when reading the files. 3.2 Transmission of the complete database The transmission of the complete database consists of a number of files of different types. Each file contains one type of element. The possible elements are listed below: <xsd:element name = "ctms" type = "ctm:ctms"/> <xsd:element name = "applicants" type = "applicant:applicants"/> <xsd:element name = "representatives" type = "representative:representatives"/> <xsd:element name = "bulletins" type = "bulletin:bulletinreferences"/> These are explained in the table below. TAGS ctms applicants OBLIG REP. representatives bulletins 3.2.1 TYPE ctm:ctms applicant:applica nts representative:re presentatives bulletin:bulletins Description Contains one or more ctm. Contains one or more applicant Contains one or more representative Contains one or more bulletin Namespace Each of the files is sent out with under the idi namepsace. The complete namespace being: http://oami.eu.int/xml/v1.00/idi Each of the elements above belong to this namespace. 3.3 Transmission of the incremental database The incremental transmissions are grouped together in one file and come under one element: <xsd:element name = "differential"> <xsd:complexType> <xsd:sequence> <xsd:element ref = "applicants" minOccurs = "0"/> <xsd:element ref = "representatives" minOccurs = "0"/> <xsd:element ref = "bulletins" minOccurs = "0"/> <xsd:element ref = "ctms" minOccurs = "0"/> </xsd:sequence> </xsd:complexType> </xsd:element> The breakdown of the content of the element is as follows: Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 6 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu TAGS ctms applicants OBLIG REP. representatives bulletins TYPE ctm:ctms applicant:applica nts representative:re presentatives bulletin:bulletins Description Contains one or more ctm. Contains one or more applicant Contains one or more representative Contains one or more bulletin This element contains a sequence of elements which are in fact references to the elements described in 3.2. Therefore the differential element can contain lists of applicants, representatives, bulletins and ctms, however, these elements are optional it does not have to contain any of these elements. A graphical representation is show below: Differential extraction 3.4 Applicants This section describes the applicants element in more detail. The applicants’ xml type is described in the http://oami.eu.int/applicant namespace and it serves as a container for three types of elements: ¾ a list of applicant type elements. Used for complete extraction OR ¾ a list of modified applicant elements. Used for differential extraction ¾ a list of deleted applicant elements. Used for differential extraction This is shown graphically below: Applicants extraction 3.4.1 applicant The applicant element is used to contain everything related to an applicant(owners). The complete applicant element is shown below: Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 7 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.4.1.1 Top Level Elements The table below describes each top level element. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 8 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu Element Data Type id legalentity personid legalentity physicalperson physicalpers on association Y Y nationality undefinedper son string(2) otherdesignation contactinfo contactinfo association undefinedperson 3.4.1.2 Data Type number integer Data Type firstname name othername incorporationstate String(60) String(255) String(60) string(80) Data Type firstname name othername String(60) String(255) String(60) Optiona l N Description the person’s id number multiplic ity 1 1 1 1 Optio nal Y Y Y Y multiplic ity 1 1 1 Optio nal Y Y multiplic ity 1 1 1 Optio nal Y Y multiplic ity 1 1 1 Optio nal Y Y Description the person’s firstname The person’s name legal entity’s state of incorporation Description the person’s firstname The person’s name association Element/Attribute Data Type firstname name othername String(60) String(255) String(60) 3.4.1.6 Y Y physicalperson Element/Attribute 3.4.1.5 Y Contains the applicant’s official id number contains the information related to a legalentity type applicant(firstname, name, othername, incorporationstate). contains the information relating to a physicalperson type applicant(firstname, name, othername). contains the information relating to an association type applicant(firstname, name, othername). contains the information relating to a otherdesignation type applicant(firstname, name, othername). nationality of a person. One of a list of isocodes. See appendix for valid values NOT USED contains both address and communication data(email, phone numbers, fax etc…) legalentity Element/Attribute 3.4.1.4 Y Description personid Element 3.4.1.3 Optiona l N Y Description the person’s firstname The person’s name undefinedperson Element/Attribute Data Type firstname name othername String(60) String(255) String(60) Description the person’s firstname The person’s name Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 9 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.4.1.7 contactinfo Element/Attribute Data Type address com address com 3.4.1.8 multipli city 1 m Optio nal Y Y Optio nal Y Data Type street string(240) multipli city m city statecounty postalcode countrycode string(80) string(80) string(10) string(2) 1 1 1 1 Y Y Y Y countryname correspondenceaddress string(80) string(240) 1 1 Y Y Element/Attribute Data Type com string(20 – 250)* string(5) multipli city 1 Optio nal Y 1 Y @-type the address information relating to a person The list of contact information(telephone, fax, email etc.…) See appendix for valid values address Element/Attribute 3.4.1.9 Description Description List of adress information(street, building number, floor etc…) The city part of the address The state or county part of the address Postal code part of the address Two-character country ISO code. See appendix for valid values The country name The official correspondence address. com Description the actual contact information Enumerated string describing the type of the contact information(email, fax, phone etc….). See appendix for valid values *- our database currently only stores phone number/string(20), fax number/string(20)and email/string(250) 3.4.2 lstmodified The lstmodified element of the applicants type is used for the differential extraction. It contains a list of applicant elements(the same as that described in ) that have been modified since the last extraction. This is shown in the figure below: 3.4.3 lstdeleted The lstdeleted element of the applicants type is used for the differential extraction. It contains a list of applicant elements(the same as that described in ) that have been deleted since the last extraction. This is shown in the figure below: 3.5 representatives This section describes the representatives element in more detail. The representatives’ xml type is described in the http://oami.eu.int/representative namespace and it serves as a container for three types of elements: ¾ a list of representative type elements. Used for complete extraction OR ¾ a list of modified representative elements. Used for differential extraction ¾ a list of deleted representative elements. Used for differential extraction This is shown graphically below: Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 10 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.5.1 representative The representatives element is used to contain everything related to representatives(agents) The complete representatives element is shown below: 3.5.1.1 Top Level Elements The table below describes each top-level element. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 11 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu Element Data Type id legalperson personid legalperson naturalperson naturalperso n contactinfo Y Element Data Type number integer Optiona l N contactinfo 3.5.1.2 3.5.1.3 firstname name othername firmname String(60) String(255) String(60) string(120) Description the person’s id number multiplic ity 1 1 1 1 Optio nal Y Y Y Y Data Type firstname name othername firmname String(60) String(255) String(60) string(120) multiplic ity 1 1 1 1 Optio nal Y Y the person’s firstname The person’s name Y ntural person’s firmname multipli city 1 m Optio nal Y Y Description Optio nal Y Data Type address com address com legal person’s firmname Description the address information relating to a person The list of contact information(telephone, fax, email etc.…). See appendix for valid values address Element/Attribute Data Type street string(240) multipli city m city statecounty postalcode countrycode string(80) string(80) string(10) string(2) 1 1 1 1 Y Y Y Y countryname correspondenceaddress string(80) string(240) 1 1 Y Y Element/Attribute Data Type com string(20 – 250)* string(5) multipli city 1 Optio nal Y 1 Y @-type the person’s firstname The person’s name contactinfo Element/Attribute 3.5.1.7 Description naturalperson Element/Attribute 3.5.1.6 Contains the applicant’s official id number contains the information related to a legalperson type representative(firstname, name, othername, firmname). contains the information relating to a naturalperson type representative(firstname, name, othername, firmname). contains both address and communication data(email, phone numbers, fax etc…) legalperson Data Type 3.5.1.5 Y Description personid Element/Attribute 3.5.1.4 Optiona l N Y Description List of adress information(street, building number, floor etc…) The city part of the address The state or county part of the address Postal code part of the address Two-character country ISO code. See appendix for valid values. The country name The official correspondence address. com Description the actual contact information Enumerated string describing the type of the contact information(email, fax, phone etc….) Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 12 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu *- our database currently only stores phone number/string(20), fax number/string(20)and email/string(250) 3.5.2 lstmodified The lstmodified element of the representatives type is used for the differential extraction. It contains a list of representative elements(the same as that described in ) that have been modified since the last extraction. This is shown in the figure below: 3.5.3 lstdeleted The lstdeleted element of the representatives type is used for the differential extraction. It contains a list of representative elements(the same as that described in ) that have been deleted since the last extraction. This is shown in the figure below: 3.6 ctms This section describes the ctms element in more detail. The ctms’ xml type is described in the http://oami.eu.int/ctm namespace and it serves as a container for three types of elements: ¾ a list of ctm type elements. Used for complete extraction OR ¾ a list of modified ctm elements. Used for differential extraction ¾ a list of deleted ctm elements. Used for differential extraction This is shown graphically below: 3.6.1 ctm The ctm element is used to contain everything related to a ctm. The complete ctm element is shown below: Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 13 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 14 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.6.1.1 Top Level Elements The table below describes each top-level element. Element Data Type applicationumber string(12) legalinformation legalinforma tion date date date date filingdate registrationdate expirydate nationalofficereceptiondat e oamireceptiondate withdrawaldate* rejectiondate* mark applicationlanguages Optiona l N Y Y Y Y Y Description The application number for the ctm. Will be a zero padded number. Contains information regarding the current status of the trademark. The date of filing for ctm. Expiry of the ctm date Y Date arrived at OHIM date Y Withdrawal of ctm date Y Rejection of ctm mark Y Defines the characteristics of the actual mark. applicationla Y The languages of application for the ctm. nguages acquireddistinctiveness string(1) Y applicants list of Y The list of applicants applying for the ctm applicants representatives list of Y The list of representatives for the ctm representativ es publicationreferences list of Y References to publications publicationre ferences priorities list of Y priorities involved with the ctm priorities seniorities list of Y seniorities involved with the ctm seniorities *- these are currently not used and so will appear as null. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 15 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.6.1.2 legalinformation Element Data Type currentstatus string(5) Optiona l Y dateoflaststatus date Y Data Type Optiona l Y Y Y Y Y Y Y Y Y Y Y Description Optiona l Y Description Optiona l Y Description 3.6.1.3 Description The current legal publishable status of mark. Choice from an enumeration. The date last status was set. mark Element word* threed* figurative* colour* olfactory* sound* hologram* other* colourclaim collectivemark goodsandserviceslist word the word mark type threed 3-D mark type figurative figurative mark type colour colour mark type olfactory olfactory mark type sound sound mark type hologram hologram mark type other other mark type boolean boolean list of goods and services viennaclassification list of vienna Y List of vienna codes, applies to figurative marks codes/string( 8) translations list of Y A grouping of textual descriptions of facets of the mark. translations These are grouped together by eulanguage. *- choice of one of these. Each type contains a denomination/string(250) element and an alphabet attribute, always optional except in case of word type mark. 3.6.1.4 goodsandservices Element Data Type @classnumber integer The Nice class number. This is an enumeration of the valid values. See appendix for valid values description string* Y The list of goods and services that the ctm applies to. @eulanguage string(2) Y The eu language that the description is given in. This is the iso code of one of the eu languages. See appendix for valid values. *- unlimited amount of text, will be in excess of 255 characters. In our database it is stored as binary text. 3.6.1.5 translations Element Data Type @eulanguage string(2) The eu language that the translations are given in. This is the isocode of one of the eu languages. See appendix for valid values. colour string* Y The description of the colour of the mark. description string* Y The description of the mark disclaimer string* Y Disclaimer *- unlimited amount of text, will be in excess of 255 characters. In our database it si stored as binary text. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 16 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 3.6.1.6 applicationlanguages Element Data Type @firstlanguage string(2) Optiona l N @secondlanguage string(2) Y 3.6.1.7 Data Type bulletinnumber part rubric pagenumber string(8) string(1) integer integer Optiona l N N N N Description The bulletin number The bulletin part. Current valid values are ‘A’ or ‘B’ priority Element Data Type priorityindex country integer string(2) Optiona l Y Y prioritynumber prioritydate prioritystatus prioritytype string(15) date string string Y Y Y Y Element Data Type @senioritynature country string string(2) Optiona l N Y seniorityfilingnumber seniorityfilingdate seniorityregistrationnumb er seniorityregistrationdate prioritydate senioritytype senioritystatus string(15) date string(15) Y Y Y date date string string Y Y Y Y Element Data Type oppositionnumber receptiondate opponentname proceedinglanguage string(12) date string(255) string(2) Optiona l N Y Y Y earlierrightsregistrationdat e typeofright nationality date Y integer string(2) Y Y denomination figurativemark* status string(255) boolean string(5) Y Y Y statusdate date Y 3.6.1.9 The first language of application. ISOcode of one of the valid office languages. See appendix for valid values. The second language of application. ISOCode of one of the valid eulanguages. See appendix for valid values. publicationreference Element 3.6.1.8 Description Description The country of priority. ISOCode of country. See appendix for valid values. One of a list of values. See appendix for valid values. Either ‘Whole’ or ‘Partial’ seniority Description Either ‘UE’ or ‘Madrid’ The country of priority. ISOCode of country. See appendix for valid values. Either ‘Whole’ or ‘Partial’ One of a list of values. See appendix for valid values. 3.6.1.10 opposition Description ISOCode of a valid eulanguage. See appendix for valid values. ISOCode of a valid country. See appendix for valid values. Current publishable status of the opposition. See appendix for valid values. The date at which status was set. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 17 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu *- Not used currently, will always appear as ‘false’. Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 18 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 4 Appendixes 4.1 Appendix A – Lookup Values This appendix provides the list of possible lookup values for various elements and attributes used within the XML Schema. Note that this document will not be kept up to date. It is recommended that the users of the application consult the Schema for updates. 4.1.1 ¾ ¾ ¾ ¾ ¾ ¾ ¾ ¾ 4.1.2 Com types tel fax email gsm telex x400 beep ip Country Codes These are the ISO Country codes. ISO Code ENCountryName AD ANDORRA AE UNITED ARAB EMIRATES AF AFGHANISTAN AG ANTIGUA AND BARBUDA AI ANGUILLA AL ALBANIA AM ARMENIA AN NETHERLANDS ANTILLES AO ANGOLA AQ ANTARCTICA AR ARGENTINA AS AMERICAN SAMOA AT AUSTRIA AU AUSTRALIA AW ARUBA AZ AZERBAIJAN BA BOSNIA AND HERZEGOWINA BB BARBADOS BD BANGLADESH BE BELGIUM BF BURKINA FASO BG BULGARIA BH BAHRAIN BI BURUNDI BJ BENIN BM BERMUDA BN BRUNEI DARUSSALAM BO BOLIVIA BR BRAZIL BS BAHAMAS BT BHUTAN BV BOUVET ISLAND BW BOTSWANA BX BENELUX Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 19 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu BY BZ CA CC CD CF CG CH CI CK CL CM CN CO CR CU CV CX CY CZ DE DJ DK DM DO DZ EC EE EG EH ER ES ET FI FJ FK FM FO FR FX GA GB GD GE GF GH GI GL GM GN GP GQ GR GS BELARUS BELIZE CANADA COCOS (KEELING) ISLANDS CONGO, THE DEMOCRATIC CENTRAL AFRICAN REPUBLIC CONGO SWITZERLAND COTE D'IVOIRE COOK ISLANDS CHILE CAMEROON CHINA COLOMBIA COSTA RICA CUBA CAPE VERDE CHRISTMAS ISLAND CYPRUS CZECH REPUBLIC GERMANY DJIBOUTI DENMARK DOMINICA DOMINICAN REPUBLIC ALGERIA ECUADOR ESTONIA EGYPT WESTERN SAHARA ERITREA SPAIN ETHIOPIA FINLAND FIJI FALKLAND ISLANDS (MALVINAS) MICRONESIA, FEDERATED STATES FAROE ISLANDS FRANCE FRANCE, METROPOLITAN GABON UNITED KINGDOM GRENADA GEORGIA FRENCH GUIANA GHANA GIBRALTAR GREENLAND GAMBIA GUINEA GUADELOUPE EQUATORIAL GUINEA GREECE SOUTH GEORGIA, SOUTH Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 20 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu GT GU GW GY HK HM HN HR HT HU ID IE IL IN IO IQ IR IS IT JM JO JP KE KG KH KI KM KN KP KR KW KY KZ LA LB LC LI LK LR LS LT LU LV LY MA MC MD MG MH MK ML MM MN MO GUATEMALA GUAM GUINEA-BISSAU GUYANA HONG KONG HEARD AND MC DONALD ISLANDS HONDURAS CROATIA (local name: Hrvatska) HAITI HUNGARY INDONESIA IRELAND ISRAEL INDIA BRITISH INDIAN OCEAN TERRITORY IRAQ IRAN (ISLAMIC REPUBLIC OF) ICELAND ITALY JAMAICA JORDAN JAPAN KENYA KYRGYZSTAN CAMBODIA KIRIBATI COMOROS SAINT KITTS AND NEVIS KOREA, DEMOCRATIC PEOPLE'S KOREA, REPUBLIC OF KUWAIT CAYMAN ISLANDS KAZAKHSTAN LAO PEOPLE'S DEMOCRATIC LEBANON SAINT LUCIA LIECHTENSTEIN SRI LANKA LIBERIA LESOTHO LITHUANIA LUXEMBOURG LATVIA LIBYAN ARAB JAMAHIRIYA MOROCCO MONACO MOLDOVA, REPUBLIC OF MADAGASCAR MARSHALL ISLANDS MACEDONIA, FORMER YUGOSLAV MALI MYANMAR MONGOLIA MACAU Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 21 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu MP MQ MR MS MT MU MV MW MX MY MZ NA NC NE NF NG NI NL NO NP NR NU NZ OM PA PE PF PG PH PK PL PM PN PR PS PT PW PY QA RE RO RU RW SA SB SC SD SE SG SH SI SJ SK SL NORTHERN MARIANA ISLANDS MARTINIQUE MAURITANIA MONTSERRAT MALTA MAURITIUS MALDIVES MALAWI MEXICO MALAYSIA MOZAMBIQUE NAMIBIA NEW CALEDONIA NIGER NORFOLK ISLAND NIGERIA NICARAGUA NETHERLANDS NORWAY NEPAL NAURU NIUE NEW ZEALAND OMAN PANAMA PERU FRENCH POLYNESIA PAPUA NEW GUINEA PHILIPPINES PAKISTAN POLAND ST. PIERRE AND MIQUELON PITCAIRN PUERTO RICO PALESTINIAN TERRITORY, PORTUGAL PALAU PARAGUAY QATAR REUNION ROMANIA RUSSIAN FEDERATION RWANDA SAUDI ARABIA SOLOMON ISLANDS SEYCHELLES SUDAN SWEDEN SINGAPORE ST. HELENA SLOVENIA SVALBARD AND JAN MAYEN ISLANDS SLOVAKIA (Slovak Republic) SIERRA LEONE Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 22 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu SM SN SO SR ST SV SY SZ TC TD TF TG TH TJ TK TM TN TO TP TR TT TV TW TZ UA UG UM US UY UZ VA VC VE VG VI VN VU WF WS YE YT YU ZA ZM ZR ZW 4.1.3 SAN MARINO SENEGAL SOMALIA SURINAME SAO TOME AND PRINCIPE EL SALVADOR SYRIAN ARAB REPUBLIC SWAZILAND TURKS AND CAICOS ISLANDS CHAD FRENCH SOUTHERN TERRITORIES TOGO THAILAND TAJIKISTAN TOKELAU TURKMENISTAN TUNISIA TONGA EAST TIMOR TURKEY TRINIDAD AND TOBAGO TUVALU TAIWAN, PROVINCE OF CHINA TANZANIA, UNITED REPUBLIC OF UKRAINE UGANDA UNITED STATES MINOR OUTLYING UNITED STATES URUGUAY UZBEKISTAN VATICAN CITY STATE (HOLY SEE) SAINT VINCENT AND THE VENEZUELA VIRGIN ISLANDS (BRITISH) VIRGIN ISLANDS (U.S.) VIET NAM VANUATU WALLIS AND FUTUNA ISLANDS SAMOA YEMEN MAYOTTE YUGOSLAVIA SOUTH AFRICA ZAMBIA ZAIRE ZIMBABWE EULanguages The ISO Codes for EU languages. The descriptions are not part of the extraction, only the ISO codes. ISO Code Language CS Czech DA Danish DE German Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 23 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu EL EN ES ET FI FR HU IT LT LV MT NL PL PT SK SL SV 4.1.4 Greek English Spanish Estonian Finish French Hungarian Italian Lithuanian Latvian Maltese Dutch Polish Portuguese Slovak Slovene Swedish Office Language The ISO Codes for office languages. The descriptions are not part of the extraction, only the ISO codes. ISO Code Language DE German EN English ES Spanish FR French IT Italian 4.1.5 EU Country Codes The ISO Codes for the countries that are currently members of the EU. This will change when enlargement is made official. ISO Code Country AT AUSTRIA BE BELGIUM BX BENELUX DE GERMANY DK DENMARK ES SPAIN FI FINLAND FR FRANCE GB UNITED KINGDOM GR GREECE IE IRELAND IT ITALY LU LUXEMBOURG NL NETHERLANDS PT PORTUGAL SE SWEDEN 4.1.6 senioritystatus ¾ ¾ ¾ ¾ ¾ Abandonned Accepted Refused To determine Partially Refused Date: 19/01/2004 Title: CTM_DOWNLOAD_V2 Functional Docu Page: 24 of 19 Dept: EDP Code: IDI _ FD Status: Version: 1.0 Author: David Robertson Reviewed by: Diego Eguidazu 4.1.7 prioritystatus ¾ ¾ ¾ ¾ ¾ 4.1.8 Abandonned Accepted Refused To determine Partially Refused opposition/status Opposition Filed Admissibility Check OK Cooling-Off Period Commencement Of Proceedings Agreement Between Parties Final Decision - CTM Withdrawn Final Decision - CTM Limited Final Decision - Opposition Withdrawn Final Decision - CTM Rejected By ED Final Decision - CTM Rejected In Part Final Decision - CTM Rejected Final Decision - Opposition Rejected Final Decision - Opposition Not Duly Entered No Decision - Opposition Not Duly Entered 4.1.9 OFIOK OADOK OCOPE OCOMP OAGRE FCMWI FCMLI FOPWI FCMRD FCMRP FCMRE FOPRE FOPND NDNDE legalinformation/currentstatus Keyed-in Filing date accorded Classification checked Application accepted Application published Opposition pending Registration published Application refused Application withdrawn Appeal pending Interruption of proceeding Registration cancelled Conversion requested Registration surrendered KEYIN FILOK CLAOK AG-OK PUBOK OP-PE RPUOK REFUS WITHD AP-PE IN-PR CANCE CONOK SURRE
© Copyright 2026 Paperzz