SlideShare una empresa de Scribd logo
1 de 7
CLAIMS specification of RIPCIS output files characteristics 1/7
WORLD INTELLECTUAL PROPERTY ORGANIZATION
SPECIAL UNION FOR THE INTERNATIONAL PATENT
CLASSIFICATION
(IPC UNION)
Date By Version Status Modification
November 12, 2004 Fiévet 0.1 Draft Creation
May 30, 2005 Fiévet 1.0 Approved Approval by IPC and IT experts
August 23, 2005 Fiévet 1.1 Approved Reference to external files (e.g. images)
November 31,2005 Fiévet 1.2 Final Removed merge and statistics files
May 9, 2006 Fiévet 1.3 Final Reference hyperlinks update
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 2/7
Contact: WIPO: Patrick FIÉVET CLAIMS Project Manager (patrick.fievet@wipo.int)
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 3/7
1. General information
In general, RIPCIS produces one unique master file in XML format for each type of
information described under section, with the exception of the Revision Concordance List
for which two files are produced : one for the Core level and one for the Advanced level.
The name of each file contains the IPC version that it corresponds to. From this master
file any subset can be extracted for as many purpose as necessary to address business
requirements (language, symbol classification level, …). In some cases, the XML files
is used an index to refer to a list of files in different formats (e.g. images or chemical
formulae). XML files are compressed in zip format together with the appropriate version
of document type definition (DTD).
1.1. Location:
All output files (once outside the database) are exported to the “download area folder
under http://www.wipo.int/ibis/IPC8/ and later published under
http://www.wipo.int/classifications/ipc/en/download_area/ .
1.2. Language:
Where necessary language is attribute of the tagged information and where not
necessary (e.g. section, class, subclass parts of the IPC symbol ) the tagged
information is shared.
2. Inventory
2.1. IPC Scheme:
ipcr_scheme_YYYYMMDD.zip + ipcr_scheme_images_YYYYMMDD.zip
where YYYYMMD is the concerned version of the IPC.
For a specific version of the IPC, the dates, in the zipped XML file (used as index) and in
the image zip file, are the same.
The scheme is made of respectively text and image parts (figure encapsulated in the text).
They are embedded (for the text part) or referred to (for the image part) in the XML file
named ipcr_scheme_YYYYMMDD.xml (ipcr_scheme_YYYYMMDD.zip compressed
in zip format).
The figure part is made of several files zipped together in
ipcr_scheme_images_YYYYMMDD.zip.
2.1.1. Brief content description of the XML file:
• IPC Version and level
• Structured elements (section, class, subclass, maingroup and group)
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 4/7
• Non-structured element (subsection titles, guidance headings, notes, class-subclass
indexes)
• Structured elements, subsection titles and guidance headings contain title parts and
optional references for each title part.
• Notes contain nested sequence of paragraphs
• Class-subclass indexes contain nested tables of index entries
The textual part may contain links to embedded image files. The same image file may
appear several times in different parts of the IPC scheme. In this case, the image file
appears only once in ipcr_scheme_images_YYYYMMDD.zip but the link to this file
appears several times in the XML file.
2.1.2. Brief content description of ipcr_scheme_images_YYYYMMDD.zip
Set of image files in GIF format. As the same file may be used from different places in
the IPC, the name of the file is meaningless.
2.1.3. Time dependency:
Publication of version YYYYMMDD of the reformed IPC.
2.1.4. Specification:
See Document type definition ipcr_scheme_V-vv.dtd (V-vv is a version number).
2.2. E-layer (illustrations e.g. for chemical formulae
ipcr_elayer_illustrations_YYYYMMDD.xml +
ipcr_elayer_illustrations_images_YYYYMMDD.zip
where YYYYMMD is the concerned version of the IPC.
For a specific version of the IPC, the dates, in the zipped XML file (used as index) and in
the image zip file, are the same.
2.2.1. Brief content description of ipcr_elayer_illustrations_YYYYMMDD.xml
This file is used as an index for all illustrations in all formats handled by the
RIPCIS system. Each illustration is an external reference to a file which can be
found in ipcr_elayer_illustrations_images_YYYYMMDD.zip
2.2.2. Brief content description of
ipcr_elayer_illustrations_images_YYYYMMDD.zip :
The illustration files are named according the following convention :
SCCsMMMMGGGGGG_N.xxx
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 5/7
where
S=Section part of the IPC symbol,
CC=Class part of the IPC symbol,
s=subclass part of the IPC symbol,
MMMM=maingroup part of the IPC symbol, padded with left zero padding,
GGGGGG= group part part of the IPC symbol with right zero padding after
second position,
N = illustration number starting from 0 (there can be more than one per IPC
symbol), and
xxx = file extension : bitmap (bmp) or graphics interchange format (gif), or chem
sketch (skc), chem draw(cdx)
Example : C07C0275120000_0.gif for the gif file of the illustration for IPC
symbol C07C 275/12
2.2.3. Brief content description:
Illustration XML files contain a simple (flat) list of IPC symbols, with a list of file
names that contain the illustrations. The images of illustrations are saved into
separate files.
2.2.4. Time dependency:
None.
2.2.5. Specification:
See Document type definition ipcr_elayer_illustrations_V-vv.dtd (V-vv is a
version number).
2.3. E-layer (definitions)
ipcr_elayer_definitions_YYYYMMDD.xml
where YYYYMMD is the concerned version of the IPC
2.3.1. Brief content description:
Classification definitions for selected subclasses of the IPC. They are intended to
provide more detailed explanations of the contents of IPC entries than the official
text of the IPC. During further development of the IPC, classification definitions
will be elaborated for all of the more than 600 subclasses of the Classification.
The electronic layer will also include facilities for displaying main groups of the
IPC in the standardized order.
The definitions are provided in a form of a sequence of independent IPC
Definition elements, each of which contains a single definition.
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 6/7
2.3.2. Time dependency:
None.
2.3.3. Specification:
See Document type definition ipcr_elayer_ definitions _V-vv.dtd (V-vv is a
version number).
2.4. Validity file
ipcr_validity_YYYYMMDD_core_EEEE.xml
where YYYYMMD is the corresponding version of the IPC and EEEE is the
associated Core level edition.
2.4.1. Brief content description:
• All valid symbols until version YYYYMMDD of the reformed IPC.
• Notification (without description) of changes of IPC symbol properties over
time.
2.4.2. Time dependency:
Publication of version YYYYMMDD of the reformed IPC.
2.4.3. Specification:
See ipcr_validity_file_specs_V-vv.doc and Document type definition
ipcr_validity_V-vv.dtd (where V-vv is a version number).
2.5. Core and Advanced Concordance lists
ipcr_Core_concordancelist_YYYYMMDD.xml for the Core classifying level
ipcr_Advanced_concordancelist_YYYYMMDD.xml for the Advanced classifying level
where YYYYMMD is the concerned version of the IPC
2.5.1. Brief content description:
Concordance between symbols of two consecutive versions of the Reformed IPC (i.e. two
consecutive versions of the Advanced level or two consecutive versions of the Core
Level). A convention will be established to address the compatibility between the first
RCL files of the reformed IPC (i.e. 7 to 8) and the following versions of the RCL files
2.5.2. Time dependency:
Publication of version YYYYMMDD of the reformed IPC.
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2
CLAIMS specification of RIPCIS output files characteristics 7/7
2.5.3. Specification:
See IPCR_RCL file specs_V-vv.doc and Document Type Definition
ipcr_concordancelist_V-vv.dtd (where V-vv is a version number).
2.6. Catchword index
ipcr_catchwordindex_YYYYMMDD.xml
where YYYYMMD is the concerned edition of the IPC.
2.6.1. Brief content description:
Sequence of embedded catchword entries. Each catchword entry is composed of a
catchword, an optional “see also” part (referring to another catchword) and an optional
sequence of IPC symbols (references).
2.6.2. Time dependency:
Publication of the edition YYYMMDD of the reformed IPC
2.6.3. Specification:
See Document type definition ipcr_catchwordindex_V-vv.dtd (where V-vv is a version
number).
2.7. Compilation files
ipcr_compilation_YYYYMMDD.xml where YYYYMMD is the creation date of the file
2.7.1. Brief content description:
Modified and new entries with necessary markup (e.g. for translation).
It contains the list of IPC entries (groups, subclasses, notes etc.) that were several
times modified during the revision period (formerly known as Merge file)
From this file it is also possible to extract statistical information about number of
modified, new and deleted IPC entries (main groups, groups) within sections /
classes / subclasses (formerly known as Statistics file)
2.7.2. Time dependency:
Core level publications: 6 months before entry into force.
Advanced level publications: 3 months before entry into force.
2.7.3. Specification:
Document Type Definition ipcr_compilation_V-vv.dtd (where V-vv is a version
number).
End of document
ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15
ver 1.2

Más contenido relacionado

Más de guestbdd02b

Rashmi Xerox Parc
Rashmi Xerox ParcRashmi Xerox Parc
Rashmi Xerox Parcguestbdd02b
 
Ppdg Robust File Replication
Ppdg Robust File ReplicationPpdg Robust File Replication
Ppdg Robust File Replicationguestbdd02b
 
Os Timed Original
Os Timed OriginalOs Timed Original
Os Timed Originalguestbdd02b
 
Office 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes AllOffice 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes Allguestbdd02b
 
Office 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes AllOffice 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes Allguestbdd02b
 
How Stupid Can We Get Notes
How Stupid Can We Get NotesHow Stupid Can We Get Notes
How Stupid Can We Get Notesguestbdd02b
 
How Stupid Can We Get
How Stupid Can We GetHow Stupid Can We Get
How Stupid Can We Getguestbdd02b
 
Corporateblogging
CorporatebloggingCorporateblogging
Corporatebloggingguestbdd02b
 
Corporateblogging
CorporatebloggingCorporateblogging
Corporatebloggingguestbdd02b
 
Design For Social Sharing
Design For Social SharingDesign For Social Sharing
Design For Social Sharingguestbdd02b
 
Excellent Testcase
Excellent TestcaseExcellent Testcase
Excellent Testcaseguestbdd02b
 
How Stupid Can We Get
How Stupid Can We GetHow Stupid Can We Get
How Stupid Can We Getguestbdd02b
 
Anne Meininger Usa
Anne Meininger UsaAnne Meininger Usa
Anne Meininger Usaguestbdd02b
 

Más de guestbdd02b (20)

Rashmi Xerox Parc
Rashmi Xerox ParcRashmi Xerox Parc
Rashmi Xerox Parc
 
Ppdg Robust File Replication
Ppdg Robust File ReplicationPpdg Robust File Replication
Ppdg Robust File Replication
 
Os Timed Original
Os Timed OriginalOs Timed Original
Os Timed Original
 
Office 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes AllOffice 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes All
 
Office 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes AllOffice 2007 Service Pack 1 Changes All
Office 2007 Service Pack 1 Changes All
 
Miyagawa
MiyagawaMiyagawa
Miyagawa
 
Macro
MacroMacro
Macro
 
Life At Google
Life At GoogleLife At Google
Life At Google
 
Languages Test
Languages TestLanguages Test
Languages Test
 
How Stupid Can We Get Notes
How Stupid Can We Get NotesHow Stupid Can We Get Notes
How Stupid Can We Get Notes
 
How Stupid Can We Get
How Stupid Can We GetHow Stupid Can We Get
How Stupid Can We Get
 
Corporateblogging
CorporatebloggingCorporateblogging
Corporateblogging
 
Corporateblogging
CorporatebloggingCorporateblogging
Corporateblogging
 
Design For Social Sharing
Design For Social SharingDesign For Social Sharing
Design For Social Sharing
 
File Management
File ManagementFile Management
File Management
 
Excellent Testcase
Excellent TestcaseExcellent Testcase
Excellent Testcase
 
How Stupid Can We Get
How Stupid Can We GetHow Stupid Can We Get
How Stupid Can We Get
 
Free Culture
Free CultureFree Culture
Free Culture
 
File Management
File ManagementFile Management
File Management
 
Anne Meininger Usa
Anne Meininger UsaAnne Meininger Usa
Anne Meininger Usa
 

Último

Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostZilliz
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsPixlogix Infotech
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebUiPathCommunity
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Scott Keck-Warren
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024Stephanie Beckett
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfPrecisely
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyAlfredo García Lavilla
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):comworks
 
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 
Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Mattias Andersson
 
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfAddepto
 
Human Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsHuman Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsMark Billinghurst
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupFlorian Wilhelm
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenHervé Boutemy
 
Search Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfSearch Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfRankYa
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxLoriGlavin3
 
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024Lonnie McRorey
 

Último (20)

Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and Cons
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio Web
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024What's New in Teams Calling, Meetings and Devices March 2024
What's New in Teams Calling, Meetings and Devices March 2024
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easy
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):
 
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 
Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?
 
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data PrivacyTrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
 
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptxE-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdf
 
Human Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsHuman Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR Systems
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project Setup
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache Maven
 
Search Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfSearch Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdf
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
 
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
 

Ipcr Ripcis Outputfiles Specification 20060509 Copy

  • 1. CLAIMS specification of RIPCIS output files characteristics 1/7 WORLD INTELLECTUAL PROPERTY ORGANIZATION SPECIAL UNION FOR THE INTERNATIONAL PATENT CLASSIFICATION (IPC UNION) Date By Version Status Modification November 12, 2004 Fiévet 0.1 Draft Creation May 30, 2005 Fiévet 1.0 Approved Approval by IPC and IT experts August 23, 2005 Fiévet 1.1 Approved Reference to external files (e.g. images) November 31,2005 Fiévet 1.2 Final Removed merge and statistics files May 9, 2006 Fiévet 1.3 Final Reference hyperlinks update ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 2. CLAIMS specification of RIPCIS output files characteristics 2/7 Contact: WIPO: Patrick FIÉVET CLAIMS Project Manager (patrick.fievet@wipo.int) ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 3. CLAIMS specification of RIPCIS output files characteristics 3/7 1. General information In general, RIPCIS produces one unique master file in XML format for each type of information described under section, with the exception of the Revision Concordance List for which two files are produced : one for the Core level and one for the Advanced level. The name of each file contains the IPC version that it corresponds to. From this master file any subset can be extracted for as many purpose as necessary to address business requirements (language, symbol classification level, …). In some cases, the XML files is used an index to refer to a list of files in different formats (e.g. images or chemical formulae). XML files are compressed in zip format together with the appropriate version of document type definition (DTD). 1.1. Location: All output files (once outside the database) are exported to the “download area folder under http://www.wipo.int/ibis/IPC8/ and later published under http://www.wipo.int/classifications/ipc/en/download_area/ . 1.2. Language: Where necessary language is attribute of the tagged information and where not necessary (e.g. section, class, subclass parts of the IPC symbol ) the tagged information is shared. 2. Inventory 2.1. IPC Scheme: ipcr_scheme_YYYYMMDD.zip + ipcr_scheme_images_YYYYMMDD.zip where YYYYMMD is the concerned version of the IPC. For a specific version of the IPC, the dates, in the zipped XML file (used as index) and in the image zip file, are the same. The scheme is made of respectively text and image parts (figure encapsulated in the text). They are embedded (for the text part) or referred to (for the image part) in the XML file named ipcr_scheme_YYYYMMDD.xml (ipcr_scheme_YYYYMMDD.zip compressed in zip format). The figure part is made of several files zipped together in ipcr_scheme_images_YYYYMMDD.zip. 2.1.1. Brief content description of the XML file: • IPC Version and level • Structured elements (section, class, subclass, maingroup and group) ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 4. CLAIMS specification of RIPCIS output files characteristics 4/7 • Non-structured element (subsection titles, guidance headings, notes, class-subclass indexes) • Structured elements, subsection titles and guidance headings contain title parts and optional references for each title part. • Notes contain nested sequence of paragraphs • Class-subclass indexes contain nested tables of index entries The textual part may contain links to embedded image files. The same image file may appear several times in different parts of the IPC scheme. In this case, the image file appears only once in ipcr_scheme_images_YYYYMMDD.zip but the link to this file appears several times in the XML file. 2.1.2. Brief content description of ipcr_scheme_images_YYYYMMDD.zip Set of image files in GIF format. As the same file may be used from different places in the IPC, the name of the file is meaningless. 2.1.3. Time dependency: Publication of version YYYYMMDD of the reformed IPC. 2.1.4. Specification: See Document type definition ipcr_scheme_V-vv.dtd (V-vv is a version number). 2.2. E-layer (illustrations e.g. for chemical formulae ipcr_elayer_illustrations_YYYYMMDD.xml + ipcr_elayer_illustrations_images_YYYYMMDD.zip where YYYYMMD is the concerned version of the IPC. For a specific version of the IPC, the dates, in the zipped XML file (used as index) and in the image zip file, are the same. 2.2.1. Brief content description of ipcr_elayer_illustrations_YYYYMMDD.xml This file is used as an index for all illustrations in all formats handled by the RIPCIS system. Each illustration is an external reference to a file which can be found in ipcr_elayer_illustrations_images_YYYYMMDD.zip 2.2.2. Brief content description of ipcr_elayer_illustrations_images_YYYYMMDD.zip : The illustration files are named according the following convention : SCCsMMMMGGGGGG_N.xxx ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 5. CLAIMS specification of RIPCIS output files characteristics 5/7 where S=Section part of the IPC symbol, CC=Class part of the IPC symbol, s=subclass part of the IPC symbol, MMMM=maingroup part of the IPC symbol, padded with left zero padding, GGGGGG= group part part of the IPC symbol with right zero padding after second position, N = illustration number starting from 0 (there can be more than one per IPC symbol), and xxx = file extension : bitmap (bmp) or graphics interchange format (gif), or chem sketch (skc), chem draw(cdx) Example : C07C0275120000_0.gif for the gif file of the illustration for IPC symbol C07C 275/12 2.2.3. Brief content description: Illustration XML files contain a simple (flat) list of IPC symbols, with a list of file names that contain the illustrations. The images of illustrations are saved into separate files. 2.2.4. Time dependency: None. 2.2.5. Specification: See Document type definition ipcr_elayer_illustrations_V-vv.dtd (V-vv is a version number). 2.3. E-layer (definitions) ipcr_elayer_definitions_YYYYMMDD.xml where YYYYMMD is the concerned version of the IPC 2.3.1. Brief content description: Classification definitions for selected subclasses of the IPC. They are intended to provide more detailed explanations of the contents of IPC entries than the official text of the IPC. During further development of the IPC, classification definitions will be elaborated for all of the more than 600 subclasses of the Classification. The electronic layer will also include facilities for displaying main groups of the IPC in the standardized order. The definitions are provided in a form of a sequence of independent IPC Definition elements, each of which contains a single definition. ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 6. CLAIMS specification of RIPCIS output files characteristics 6/7 2.3.2. Time dependency: None. 2.3.3. Specification: See Document type definition ipcr_elayer_ definitions _V-vv.dtd (V-vv is a version number). 2.4. Validity file ipcr_validity_YYYYMMDD_core_EEEE.xml where YYYYMMD is the corresponding version of the IPC and EEEE is the associated Core level edition. 2.4.1. Brief content description: • All valid symbols until version YYYYMMDD of the reformed IPC. • Notification (without description) of changes of IPC symbol properties over time. 2.4.2. Time dependency: Publication of version YYYYMMDD of the reformed IPC. 2.4.3. Specification: See ipcr_validity_file_specs_V-vv.doc and Document type definition ipcr_validity_V-vv.dtd (where V-vv is a version number). 2.5. Core and Advanced Concordance lists ipcr_Core_concordancelist_YYYYMMDD.xml for the Core classifying level ipcr_Advanced_concordancelist_YYYYMMDD.xml for the Advanced classifying level where YYYYMMD is the concerned version of the IPC 2.5.1. Brief content description: Concordance between symbols of two consecutive versions of the Reformed IPC (i.e. two consecutive versions of the Advanced level or two consecutive versions of the Core Level). A convention will be established to address the compatibility between the first RCL files of the reformed IPC (i.e. 7 to 8) and the following versions of the RCL files 2.5.2. Time dependency: Publication of version YYYYMMDD of the reformed IPC. ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2
  • 7. CLAIMS specification of RIPCIS output files characteristics 7/7 2.5.3. Specification: See IPCR_RCL file specs_V-vv.doc and Document Type Definition ipcr_concordancelist_V-vv.dtd (where V-vv is a version number). 2.6. Catchword index ipcr_catchwordindex_YYYYMMDD.xml where YYYYMMD is the concerned edition of the IPC. 2.6.1. Brief content description: Sequence of embedded catchword entries. Each catchword entry is composed of a catchword, an optional “see also” part (referring to another catchword) and an optional sequence of IPC symbols (references). 2.6.2. Time dependency: Publication of the edition YYYMMDD of the reformed IPC 2.6.3. Specification: See Document type definition ipcr_catchwordindex_V-vv.dtd (where V-vv is a version number). 2.7. Compilation files ipcr_compilation_YYYYMMDD.xml where YYYYMMD is the creation date of the file 2.7.1. Brief content description: Modified and new entries with necessary markup (e.g. for translation). It contains the list of IPC entries (groups, subclasses, notes etc.) that were several times modified during the revision period (formerly known as Merge file) From this file it is also possible to extract statistical information about number of modified, new and deleted IPC entries (main groups, groups) within sections / classes / subclasses (formerly known as Statistics file) 2.7.2. Time dependency: Core level publications: 6 months before entry into force. Advanced level publications: 3 months before entry into force. 2.7.3. Specification: Document Type Definition ipcr_compilation_V-vv.dtd (where V-vv is a version number). End of document ipcr-ripcisoutputfilesspecification20060509-copy-1228978917483123-1.doc 28/01/15 ver 1.2