A Standard Communication Format One Format There is





















![Data Extraction from Invoices [under development] • A highly-scalable cloud service to be used Data Extraction from Invoices [under development] • A highly-scalable cloud service to be used](https://slidetodoc.com/presentation_image/26f4aecf530440f973639796982c608b/image-22.jpg)
![Data Extraction from Invoices [under development] • Cloud – Continuous retraining of the ML Data Extraction from Invoices [under development] • Cloud – Continuous retraining of the ML](https://slidetodoc.com/presentation_image/26f4aecf530440f973639796982c608b/image-23.jpg)



- Slides: 26
A Standard Communication Format
One Format? • There is a large number of formats to communicate data between systems: – Different formats per PTO – Different formats per operation – Different formats per type of data
What is SGML/XML? • SGML (Standard Generalized Markup Language) – a standard for expressing data in textprocessing applications • XML (e. Xtensible Markup Language) – subset of SGML – invented to deal with the barriers to deliver SGML over the web
XML Example <? xml version="1. 0" encoding="UTF-8"? > <note> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note>
What is DTD/XSD? • A DTD is a Document Type Definition. • A DTD defines the structure, elements and attributes of an XML document. • XSD stands for XML Schema Definition • Can be used by programmers to verify an XML document.
International Standards from WIPO • XML Standards – ST. 36 • Recommendation for the processing of patent information using XML – ST. 66 • Recommendation for the processing of trademark information using XML – ST. 86 • Recommendation for the processing of industrial design information using XML – ST. 96 • Recommendation for the processing of industrial property information using XML
Afnor NF X 50 -276 -2 • XML standard for all IP rights • Already used in France • Patrix is a member of the standardization committee
Financial Standards • Electronic data interchange (EDI) standards – X 12, EDIFACT, ODETTE • Legal Electronic Data Exchange Standard (LEDES) – Set of file format specifications intended to facilitate electronic data transmission in the legal industry • Ty. Metrix® 360° – Saa. S-based e-Billing and Legal Matter Management software solution
Patricia Standard • Case/Name/Documents: XML-based • Financial data – Table-based or file-based • Invoices [under development]: – XML-based – Import from scanned PDFs
Communication Services • e-Filing • EPO • USPTO • Norway (altinn) • Data Exchange • External source Patricia • • • • Data Comparison WIPO TM_view OPS Official PTO Communication Private PAIR EPO Mailbox
e-Filing (EPO) List of Forms • EP (1001 E 2 k) – Request for grant of a European patent • • (EPC 2000) Required EP(1200 E 2 k) – Entry into • Patricia C/S European phase (EPC 2000) • Web Server (Jboss) PCT/RO/101 – PCT/RO/101 • EPOLine software (available on request EPO web site)
e-Filing (USPTO) List of Froms • Application Data Sheet (37 CFR 1. 76) • Information Disclosure Statement by Applicant • Request for Continued Examination (RCE) Transmittal Required • Petition 37 CFR 1. 378(c) • • Patricia C/S Provisional Application for Patent Cover • Web Server (Jboss) • Adobe PDF reader installed / Sheet plugin on Browser
e-Filing (altinn) List of Froms • PS 101 – Patent • PS 201 – Trademark • PS 301 – Design Required • Patricia C/S • Web Server (Jboss)
Data Exchange External source Patricia • Prepare portfolio in Excel Standard Patricia Excel tempalte • Transform Excel to XML Data Transformation • Import XML into Patricia Data Import • Case Diary Parties Case References Notes Required • Patricia C/S • Web Server (Jboss) Classes Desingated Coutnires Other Basic Information • Name Basic Names Information only. (Name, Address)
Data Exchange Patricia • Data Export Configuration available in Maintenance Data in Patricia XML format • Import XML into Patricia Data Import • Required Import Mapping in • Patricia C/S Maintenance • Web Server (Jboss)
Data Comparison Trademarks - WIPO • Compare your Trademark Bibliographic data against the international trademark database from WIPO • Web Services • Free of Charge • Single-case only, no batches • https: //www. epo. org/servicesupport/ordering/ops-terms-andconditions. html Required • Patricia C/S • Web Server (Jboss) • Comparison Mapping in Maintenance
Data Comparison Trademarks - TMView • Compare your Trademark Bibliographic data against TMView • Web Services or Scraping (depending on country) • Free of Charge Required • Patricia C/S • Web Server (Jboss) • Comparison Mapping in Maintenance • Single-case only, no batches
Data Comparison Patents - EPO • Compare your Patent Bibliogrpahic data against Open Patent Services (OPS) from EPO • • • Web Service Free of Charge https: //www. epo. org/servicesupport/ordering/ops-terms-andconditions. html Required • Patricia C/S • Web Server (Jboss) • Comparison Mapping in Maintenance
Data Comparison Batch • Batch comparison not currently available due to the terms of use. • The possibility to reintroduce it at a later stage will be considered.
Official PTO Communication Patents - USPTO • Get official communication from USPTO’s Patent Application Information Retrieval (PAIR) • Web Service and Scraping (depending on sections) • Free of Charge Required • Patricia C/S • Web Server (Jboss) • Comparison Mapping in Maintenance • PKI (based on customer number)
Official PTO Communication Patents – EPO Mailbox • Get official communication from Required EPO’s mailbox • Patricia C/S • Web Server (Jboss) • Comparison Mapping in • Scraping • Free of Charge Maintenance • Smart card or PKI (per customer)
Data Extraction from Invoices [under development] • A highly-scalable cloud service to be used by Document Docketing Automation – A scanned PDF is submitted, extracted data are returned (e. g. registration number, amounts, dates) – Uses OCR to produce the text and its position – Uses Machine Learning and approximate string matching to extract data – Uses a microservices architecture
Data Extraction from Invoices [under development] • Cloud – Continuous retraining of the ML model – Stay up-to-date with the templates used by PTOs – No additional hardware requirements – Automatic Scaling (sub-linear) • Microservices – Easier to upgrade individual components – High flexibility to use the best tool for each task
Document Docketing Future Improvements • Extracting data from invoices is just the start • Looking into other use cases to increase automation of document docketing via machine learning
Thank you