SlideShare a Scribd company logo
PREPARING
LEGAL STATUS DATA
  FOR EXCHANGE




                                    LATIPAT
                               November 2012




    Wistre Rodriguez Del Amo
PREPARING LEGAL STATUS DATA
FOR EXCHANGE

 The data flow at the EPO

 The data flow at your place of work

 Examples of "good practice"

 What we would wish for ...


            W Fenny Versloot-Spoelstra Amo
             istre Rodriguez Del
DATA FLOW AT THE EPO
Legal Status - Back Stage


 Getting the data from A to B

 Maintaining the master database

 Delivering legal status to the world




             W Fenny Versloot-Spoelstra Amo
              istre Rodriguez Del
Getting the data from A to B ...

   Sources
        internet sites
        FTP servers
        E-mail attachments
        EPO front office


   Formats
        gazettes and bulletins in PDF format
        data in TXT or CSV format
        data in SGML or XML format


                       W Fenny Versloot-Spoelstra Amo
                        istre Rodriguez Del
Internet Sites                 EPO Front Office



  FTP Servers                       E-mail
                                                                             over 40 offices
      raw data
                                                                          80.6 Mio events
                               "cooked"
                                 data                        valid data       PRS
                                                                             MASTER
                                                                            DATABASE



new data                                                                           services
new provider                                                                           &
change of format                                                                   products

                                                quality
                                                issues



                                W Fenny Versloot-Spoelstra Amo
                                 istre Rodriguez Del
Challenges ...

   Variety in delivery methods
        data sources, data formats


   Ever-changing environments
        change of patent law
        change of data format
        change of delivery policy


   Human resources
        manual intervention
        intellectual effort
                       W Fenny Versloot-Spoelstra Amo
                        istre Rodriguez Del
manage delivery methods
                                                      manage changing environments
                                                      reduce manual effort




                         polling websites
                         and servers
                         pulling data
                                                      maintenance

dedicated
    processes
"cooking" the data
                                                      monitoring




   powerful engine                 triggering             intellectual   customer
   validating the data             database update        intervention   support

                       managing
             changing parameters
                                                  Master
                                                 Database
                     W Fenny Versloot-Spoelstra Amo
                      istre Rodriguez Del
Maintaining the master database

   Office-specific nature of the data
         language issues
         event codes used
         meta-data provided


   Availability of the bibliographic data
         pre-requisite for exchange of legal status
         contains data elements with legal implications




                       W Fenny Versloot-Spoelstra Amo
                        istre Rodriguez Del
Challenges ...

   Identifying the nature of the event
        events of the same nature identified by different codes
        code descriptions in "exotic" languages

   Identifying data items in the input
        tidiness of the data
        quality of the documentation

   Linking to the bibliographic data
        publication kind-code not provided
        ambiguous number series across IPR-types

                      W Fenny Versloot-Spoelstra Amo
                       istre Rodriguez Del
Define rules to
                        identify legal events by country-specific codes
                       Still need careful analysis of the content

                       Still be relying on
                        the tidiness of the data
                        the quality of the documentation
                       Still be confronted with language issues


                                                    Business
                                                    Rules
                                                    Engine

          PRS
         Master

                       Define rules to :
                        support access without kind-code
DOCDB                   resolve ambiguous number series
Master                 Still be a certain degree of "second guessing"

                  W Fenny Versloot-Spoelstra Amo
                   istre Rodriguez Del
One particular challenge ...

   Trend to exchange complete "life of a file"
        all legal events in the life of a file every time
        the most recent as well as all previous events

   Challenge ? Identifying the new events !!
        no indication which event is the new event
        no date of capture, no reliable date of capture

   Why not take the new life and dump the old ?
        invested time and effort in improving the quality
        improved and corrected data would be overwritten

                       W Fenny Versloot-Spoelstra Amo
                        istre Rodriguez Del
Delivering legal status to the world

   On-line services
        OPS, ESPACEnet, EPO Patent Register
        free of charge
        available 24 x 7


   Raw data product
        INPADOC Worldwide Legal Status
        by subscription only
        updates once a week



                      W Fenny Versloot-Spoelstra Amo
                       istre Rodriguez Del
EPO                       INPADOC
   PATENT INFORMATION               WORLD WIDE
       RESOURCE                    LEGAL STATUS




             EPODOC

                                         EPO                            INPADOC
EXTENDED                               REGISTER
 FAMILIES
                                                                        Worldwide
                                                                        Legal Status



  Open
  Patent
  Services



                                      End Users


 ESPACEne                                                Commercial Hosts
                        W Fenny Versloot-Spoelstra Amo
                         istre Rodriguez Del
Products & Services

   Open Patent Services
        Raw data provided on-line through web-services
        Designed for automated queries returning fair amounts of data


   ESPACEnet - EPO Patent Register
        Patent information provided on-line in end-user format
        Designed for use by the general public


   INPADOC Worldwide Legal Status
        Raw data provided weekly through the down-load area
        Designed for use by commercial hosts and patent professionals
                      W Fenny Versloot-Spoelstra Amo
                       istre Rodriguez Del
FACTS of LIFE

   We can only give as much as we get ...
        depend on the accuracy and timeliness of data providers
        cannot guarantee that ALL legal events are covered

   It is not uncommon ...
        NOT to receive a notification of reinstatement after a lapse
        to receive a LATE     notification of reinstatement after a
         lapse




                     W Fenny Versloot-Spoelstra Amo
                      istre Rodriguez Del
FACTS of LIFE

   What we give is as good as we get ...
        do not insert     legal events unless received from the provider
        do not remove legal events once            received from the provider
        do not correct legal events unless requested by the provider

   That means that ...
        "lapse due to non-payment of fees" will not be removed from
         the database when followed by a late "payment of fees"
        "notification of reinstatement" will not be added to the
         database on evidence provided by 3rd parties



                         W Fenny Versloot-Spoelstra Amo
                          istre Rodriguez Del
DISCLAIMER




 EPO does not accept any responsibility
  for the accuracy of data and information
  originating from other authorities
 EPO does not guarantee that they are
  complete, up-to-date or fit for specific purposes

W Fenny Versloot-Spoelstra Amo
 istre Rodriguez Del
Why this "Disclaimer" ... ?

   Worldwide Legal Status is as good as the data it gets
        notification of a lapse may not have been given
        notification of reinstatement may be late
        notification of reinstatement may not have arrived

   Worldwide Legal Status cannot guarantee legal certainty
        inside worldwide legal status the patent might be "dead"
        out there the patent may be "alive and kicking"




                      W Fenny Versloot-Spoelstra Amo
                       istre Rodriguez Del
Business decision to make ... ??

   Use Worldwide Legal Status to get a general idea
   Double-check against the national register at all times




                    W Fenny Versloot-Spoelstra Amo
                     istre Rodriguez Del
So .... this is how the data flows at the EPO




 How does the data flow at your office ?
              W Fenny Versloot-Spoelstra Amo
               istre Rodriguez Del
Couple of questions for you :

   How have you organised your data flow ?

   How do you make your data available ?
        data-format : PDF, XML, SGML, ... , other?
        medium : internet, E-mail, electronic file transfer?

   If in PDF - what format was it in before it became PDF ?
        mark-up language: XML, SGML or even INID-
         code?
        any other format that allows electronic transfer?

                    W Fenny Versloot-Spoelstra Amo
                     istre Rodriguez Del
We will give the floor to the participants




              W Fenny Versloot-Spoelstra Amo
               istre Rodriguez Del
EXAMPLES
     OF
GOOD PRACTICE




                                   LATIPAT
                              November 2012




   Wistre Rodriguez Del Amo
We will take the participants through
some examples ...




               Wistre Rodriguez Del Amo
                 Fenny Versloot-Spoelstra
OUR "WISH LIST" ...
   Delivery Method
        Internet site with stable URL
        FTP server

   Data Format
        generally any mark-up language will do
        preferably data in XML
        not desirable are formats like TXT or PDF

   Content ....
                      Wistre Rodriguez Del Amo
                        Fenny Versloot-Spoelstra
Wistre Rodriguez Del Amo
  Fenny Versloot-Spoelstra
if you provide us with more than just the new event
tell us which of the events is the new event


   clearly indicate when the event was made public



          identify nature of the event by unique code




                         description in your own language




                         if possible translation in English

 Wistre Rodriguez Del Amo
   Fenny Versloot-Spoelstra
clearly indicate when the event has become effective

             clearly indicate the application / publication
             that this event is relating to

             change of ownership, assignments, ...
             clearly indicate previous and new owner
             when in "exotic" original character set
             provide names and addresses transliterated

             supplementary protection certificates
             clearly indicate the vital components




 Wistre Rodriguez Del Amo
   Fenny Versloot-Spoelstra
THUMBS UP for :

   Posting your data on the internet or on FTP
   Providing your data in structured mark-up language
   Clearly identifying the nature of the legal event
   Supporting consistent and unambiguous number series
   Making sure that we understand what we get :
        documentation is vital
        English language translations are helpful


                       Wistre Rodriguez Del Amo
                         Fenny Versloot-Spoelstra
What is a legal event?




   Can you give me
    some examples
           of
     legal events?
                   Wistre Rodriguez Del Amo
                     Fenny Versloot-Spoelstra
A legal event can be

• Any kind of invalidation, e.g.
  lapses, expiries, withdrawals,
  revocations, etc.
• Limitations
• Reinstatements
• Fee payments
• Grant
• Change of ownerships
• Change of representatives
• Licensing information , e.g. willing
                Wistre Rodriguez Del Amo
                  Fenny Versloot-Spoelstra
Which legal events are in the worldwide legal event database?




In the worldwide legal event database are no
legal events that are in DOCdb
(i.e. bibliographic data)

              Which legal events
    can be coupled with bibliographic data?




                     Wistre Rodriguez Del Amo
                       Fenny Versloot-Spoelstra
Events received by bibliographic data
•   Priorities
•   Filing an application
•   Each publication step (i.e. normally also grant)
•   For EP documents also
     – previously files application
     – preceding publication date
     – coming into force

 We produce Extended legal event data to
  cover these events as raw data



                    Wistre Rodriguez Del Amo
                      Fenny Versloot-Spoelstra
Which legal events are in the worldwide legal event database?




                 Why are different
               legal events collected
                  for each country?

  (i.e. not always the same kind of events for
                   each country)




                     Wistre Rodriguez Del Amo
                       Fenny Versloot-Spoelstra
The reasons for different kind of data are

• Each country has a different patent law
• Each patent office sent us different data
• The collection of each country started at the different
  moment


Side effect
 We receive data from very different sources and
 none of them can guarantee completeness and
 correctness of their data

             We cannot guarantee the completeness
              and correctness of our data

                     Wistre Rodriguez Del Amo
                       Fenny Versloot-Spoelstra
Which legal events are in the worldwide legal event database?




 How many patent authorities are covered by
             legal event data?

    How many records are in the legal event
                  database?




                     Wistre Rodriguez Del Amo
                       Fenny Versloot-Spoelstra
Statistical data of the legal event database
•   Number of records March 2012:
     – 100 000 000
•   Expected number of records end of 2012:
     – 120 000 000
•   Number of patent authorities we have received data from 2012:
     – 42
•   Overall number of patent authorities we have data from:
     – 62
        • PCT entry data from WIPO (not sent directly to us)
        • not existing countries (like GDR)
        • patent office stopped sending us data




                       Wistre Rodriguez Del Amo
                         Fenny Versloot-Spoelstra
Which information is in a legal event record?



               Here is a legal event from
                espacenet:          Application Number
                                                        Publication Date
Country Code




                                                   Legal Event (what happened)




                                     Wistre Rodriguez Del Amo
                                       Fenny Versloot-Spoelstra
Which information is in a legal event record?



Here is the same legal event
 from espacenet:




                      Wistre Rodriguez Del Amo
                        Fenny Versloot-Spoelstra
Where can you find worldwide legal event data?




       Where can you
       search for legal
         event data?
                     Wistre Rodriguez Del Amo
                       Fenny Versloot-Spoelstra
Legal events can be received via

EPO tools
   –espacenet
   –OPS
   –PATSTAT (add on)
   –European Register (only EP patents)
   –as raw data, sent to subscribers


Commercial partners
   −STN
   −Thomson Scientific
   −Questel/Orbit
   −Dialog     Wistre Rodriguez Del Amo
                 Fenny Versloot-Spoelstra
What is a legal event with PRS code "REG "?

 In espacenet one can see this information




                            ....               IE = Ireland




Which patent office has provided this
           information?

  Why has this information a code
   "REG " before the real code?
                      Wistre Rodriguez Del Amo
                        Fenny Versloot-Spoelstra
Why there are "REG " codes?
In the PRS database only the country code of the patent
is included.

The PRS code consists also of these 2 parts:
    Country Code
    4 digit event code

The country code of the PRS code is not included in
PRS and most of the tools you can search for legal
event data

=> Country code is taken from patent identification

Therefore an original European patent has to have an
EP Code
(= "REG ") and the real national code is hidden in an
attribute.

=> in our example: EP REG Rodriguez Del Amo
                             IE FG4A
                      Wistre Versloot-Spoelstra
                        Fenny
How should "REG " codes be
interpreted?




Something happens with a patent filed in a regional office or of a
country with a number (here EPO patent 1456342) of another patent
authority

The patent office the event happened or has been announced by is the
country (in espacenet) behind "REG " (here Ireland)

What happened says the code behind the country (here entry of EP
patent into the Irish national phase)

All attributes rely on the "real code" (here original document was
published in French)
                         Wistre Rodriguez Del Amo
                           Fenny Versloot-Spoelstra
My further question?



    For what are legal event data useful?

   (also in combination with another patent
                  information)




                Wistre Rodriguez Del Amo
                  Fenny Versloot-Spoelstra
My further question - use for legal status
data?
• Where (in which countries) is an invention
  still protected?
• Where is the present owner of an invention
  and where?
• How long is a patent protected?
   – in a technical field
   – by an applicant
   – etc.
• What happened with an invention in different
  countries?
• etc.

                 Wistre Rodriguez Del Amo
                   Fenny Versloot-Spoelstra
Résumé

  Worldwide legal event data is a valuable
  source to answer interesting questions
         (especially for the industry)
   for the protection of inventions and for
                    patents.




                Wistre Rodriguez Del Amo
                  Fenny Versloot-Spoelstra
Questions ?




                           Comments ?


              W Fenny Versloot-Spoelstra Amo
               istre Rodriguez Del             21/11/12

More Related Content

Similar to Legal status at the epo latipat

10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
Stichting ePortfolio Support
 
Info.processing
Info.processingInfo.processing
Info.processing
jeancly
 
January 2006 Document Scanning Considerations Presentation
January 2006 Document Scanning Considerations PresentationJanuary 2006 Document Scanning Considerations Presentation
January 2006 Document Scanning Considerations Presentation
John Wang
 
01 data quality-international challenge
01 data quality-international challenge01 data quality-international challenge
01 data quality-international challenge
PiLog
 

Similar to Legal status at the epo latipat (20)

10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
10052012 luc vervenne synergetics van syntax portfolio naar semantische uitwi...
 
Spreadmart To Data Mart BISIG Presentation
Spreadmart To Data Mart BISIG PresentationSpreadmart To Data Mart BISIG Presentation
Spreadmart To Data Mart BISIG Presentation
 
Fujitsu & Readsoft Forms Classification and Document Automation Webinar
Fujitsu & Readsoft Forms Classification and Document Automation WebinarFujitsu & Readsoft Forms Classification and Document Automation Webinar
Fujitsu & Readsoft Forms Classification and Document Automation Webinar
 
Rapid and flexible clinical data extraction and processing using Apache OODT
Rapid and flexible clinical data extraction and processing using Apache OODTRapid and flexible clinical data extraction and processing using Apache OODT
Rapid and flexible clinical data extraction and processing using Apache OODT
 
Edi2
Edi2Edi2
Edi2
 
Anzo Smart Data Lake 4.0 - a Data Lake Platform for the Enterprise Informatio...
Anzo Smart Data Lake 4.0 - a Data Lake Platform for the Enterprise Informatio...Anzo Smart Data Lake 4.0 - a Data Lake Platform for the Enterprise Informatio...
Anzo Smart Data Lake 4.0 - a Data Lake Platform for the Enterprise Informatio...
 
Info.processing
Info.processingInfo.processing
Info.processing
 
Info.processing
Info.processingInfo.processing
Info.processing
 
Data Ninja Webinar Series: Accelerating Business Value with Data Virtualizati...
Data Ninja Webinar Series: Accelerating Business Value with Data Virtualizati...Data Ninja Webinar Series: Accelerating Business Value with Data Virtualizati...
Data Ninja Webinar Series: Accelerating Business Value with Data Virtualizati...
 
Os Pittaro
Os PittaroOs Pittaro
Os Pittaro
 
January 2006 Document Scanning Considerations Presentation
January 2006 Document Scanning Considerations PresentationJanuary 2006 Document Scanning Considerations Presentation
January 2006 Document Scanning Considerations Presentation
 
Starting the Small Case: Technical Considerations
Starting the Small Case: Technical ConsiderationsStarting the Small Case: Technical Considerations
Starting the Small Case: Technical Considerations
 
Innovations in Intake - Ohio 11 21 2008
Innovations in Intake - Ohio 11 21 2008Innovations in Intake - Ohio 11 21 2008
Innovations in Intake - Ohio 11 21 2008
 
01 data quality-international challenge
01 data quality-international challenge01 data quality-international challenge
01 data quality-international challenge
 
Ecm sales training sample day 1
Ecm sales training sample  day 1Ecm sales training sample  day 1
Ecm sales training sample day 1
 
E-Discovery explained, so you don't need to be a Lawyer, to get it.
E-Discovery explained, so you don't need to be a Lawyer, to get it.E-Discovery explained, so you don't need to be a Lawyer, to get it.
E-Discovery explained, so you don't need to be a Lawyer, to get it.
 
Corporate Awareness Litigation
Corporate Awareness  LitigationCorporate Awareness  Litigation
Corporate Awareness Litigation
 
eDiscovery Perspective
eDiscovery PerspectiveeDiscovery Perspective
eDiscovery Perspective
 
Gilbane 2009 -- How Can Content Management Software Keep Pace?
Gilbane 2009 -- How Can Content Management Software Keep Pace?Gilbane 2009 -- How Can Content Management Software Keep Pace?
Gilbane 2009 -- How Can Content Management Software Keep Pace?
 
Best practices and trends in people soft
Best practices and trends in people softBest practices and trends in people soft
Best practices and trends in people soft
 

More from LATIPAT

Publication servers
Publication serversPublication servers
Publication servers
LATIPAT
 
Ftp data exchange-mechanism
Ftp data exchange-mechanismFtp data exchange-mechanism
Ftp data exchange-mechanism
LATIPAT
 
Citation data flow 2012 nat latipat
Citation data flow 2012 nat latipatCitation data flow 2012 nat latipat
Citation data flow 2012 nat latipat
LATIPAT
 
2012 11 latipat-cpc_epo
2012 11 latipat-cpc_epo2012 11 latipat-cpc_epo
2012 11 latipat-cpc_epo
LATIPAT
 
2012 11 latipat-ccd_epo
2012 11 latipat-ccd_epo2012 11 latipat-ccd_epo
2012 11 latipat-ccd_epo
LATIPAT
 
03 patent families latipat the powerpoint
03 patent families latipat   the powerpoint03 patent families latipat   the powerpoint
03 patent families latipat the powerpoint
LATIPAT
 
E pec colombia todorov
E pec colombia todorovE pec colombia todorov
E pec colombia todorov
LATIPAT
 
Presentación latipat rio
Presentación latipat rioPresentación latipat rio
Presentación latipat rio
LATIPAT
 
Gb wipoq@s
Gb wipoq@sGb wipoq@s
Gb wipoq@s
LATIPAT
 
Gb indexacion automatica
Gb indexacion automaticaGb indexacion automatica
Gb indexacion automatica
LATIPAT
 
Intercambio electrónico 2011
Intercambio electrónico 2011Intercambio electrónico 2011
Intercambio electrónico 2011
LATIPAT
 
Estadistica acceso latipat
Estadistica acceso latipatEstadistica acceso latipat
Estadistica acceso latipat
LATIPAT
 
Co complemento situacion-actual
Co   complemento situacion-actualCo   complemento situacion-actual
Co complemento situacion-actual
LATIPAT
 
Presentación latipat rio
Presentación latipat rioPresentación latipat rio
Presentación latipat rio
LATIPAT
 
Papel de la ompi promocion innov arc_ar
Papel de la ompi promocion innov arc_arPapel de la ompi promocion innov arc_ar
Papel de la ompi promocion innov arc_ar
LATIPAT
 

More from LATIPAT (20)

Publication servers
Publication serversPublication servers
Publication servers
 
Ftp data exchange-mechanism
Ftp data exchange-mechanismFtp data exchange-mechanism
Ftp data exchange-mechanism
 
Citation data flow 2012 nat latipat
Citation data flow 2012 nat latipatCitation data flow 2012 nat latipat
Citation data flow 2012 nat latipat
 
2012 11 latipat-cpc_epo
2012 11 latipat-cpc_epo2012 11 latipat-cpc_epo
2012 11 latipat-cpc_epo
 
2012 11 latipat-ccd_epo
2012 11 latipat-ccd_epo2012 11 latipat-ccd_epo
2012 11 latipat-ccd_epo
 
03 patent families latipat the powerpoint
03 patent families latipat   the powerpoint03 patent families latipat   the powerpoint
03 patent families latipat the powerpoint
 
E pec colombia todorov
E pec colombia todorovE pec colombia todorov
E pec colombia todorov
 
Servicios de información y fuentes latest developments sept_2011
Servicios de información y fuentes latest developments sept_2011Servicios de información y fuentes latest developments sept_2011
Servicios de información y fuentes latest developments sept_2011
 
Presentación latipat rio
Presentación latipat rioPresentación latipat rio
Presentación latipat rio
 
Gb wipoq@s
Gb wipoq@sGb wipoq@s
Gb wipoq@s
 
Gb indexacion automatica
Gb indexacion automaticaGb indexacion automatica
Gb indexacion automatica
 
Logo
LogoLogo
Logo
 
Intercambio electrónico 2011
Intercambio electrónico 2011Intercambio electrónico 2011
Intercambio electrónico 2011
 
Estadistica acceso latipat
Estadistica acceso latipatEstadistica acceso latipat
Estadistica acceso latipat
 
Co complemento situacion-actual
Co   complemento situacion-actualCo   complemento situacion-actual
Co complemento situacion-actual
 
Presentación latipat rio
Presentación latipat rioPresentación latipat rio
Presentación latipat rio
 
Epo info resources & espacenet & search techniques
Epo info resources & espacenet & search techniquesEpo info resources & espacenet & search techniques
Epo info resources & espacenet & search techniques
 
Presentacion 20111019 latipat
Presentacion 20111019 latipatPresentacion 20111019 latipat
Presentacion 20111019 latipat
 
Presentation vm latipat2011 ver 3
Presentation vm latipat2011 ver 3Presentation vm latipat2011 ver 3
Presentation vm latipat2011 ver 3
 
Papel de la ompi promocion innov arc_ar
Papel de la ompi promocion innov arc_arPapel de la ompi promocion innov arc_ar
Papel de la ompi promocion innov arc_ar
 

Legal status at the epo latipat

  • 1. PREPARING LEGAL STATUS DATA FOR EXCHANGE LATIPAT November 2012 Wistre Rodriguez Del Amo
  • 2. PREPARING LEGAL STATUS DATA FOR EXCHANGE  The data flow at the EPO  The data flow at your place of work  Examples of "good practice"  What we would wish for ... W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 3. DATA FLOW AT THE EPO Legal Status - Back Stage  Getting the data from A to B  Maintaining the master database  Delivering legal status to the world W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 4. Getting the data from A to B ...  Sources  internet sites  FTP servers  E-mail attachments  EPO front office  Formats  gazettes and bulletins in PDF format  data in TXT or CSV format  data in SGML or XML format W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 5. Internet Sites EPO Front Office FTP Servers E-mail over 40 offices raw data 80.6 Mio events "cooked" data valid data PRS MASTER DATABASE new data services new provider & change of format products quality issues W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 6. Challenges ...  Variety in delivery methods  data sources, data formats  Ever-changing environments  change of patent law  change of data format  change of delivery policy  Human resources  manual intervention  intellectual effort W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 7. manage delivery methods manage changing environments reduce manual effort polling websites and servers pulling data maintenance dedicated processes "cooking" the data monitoring powerful engine triggering intellectual customer validating the data database update intervention support managing changing parameters Master Database W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 8. Maintaining the master database  Office-specific nature of the data  language issues  event codes used  meta-data provided  Availability of the bibliographic data  pre-requisite for exchange of legal status  contains data elements with legal implications W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 9. Challenges ...  Identifying the nature of the event  events of the same nature identified by different codes  code descriptions in "exotic" languages  Identifying data items in the input  tidiness of the data  quality of the documentation  Linking to the bibliographic data  publication kind-code not provided  ambiguous number series across IPR-types W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 10. Define rules to  identify legal events by country-specific codes Still need careful analysis of the content Still be relying on  the tidiness of the data  the quality of the documentation Still be confronted with language issues Business Rules Engine PRS Master Define rules to :  support access without kind-code DOCDB  resolve ambiguous number series Master Still be a certain degree of "second guessing" W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 11. One particular challenge ...  Trend to exchange complete "life of a file"  all legal events in the life of a file every time  the most recent as well as all previous events  Challenge ? Identifying the new events !!  no indication which event is the new event  no date of capture, no reliable date of capture  Why not take the new life and dump the old ?  invested time and effort in improving the quality  improved and corrected data would be overwritten W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 12. Delivering legal status to the world  On-line services  OPS, ESPACEnet, EPO Patent Register  free of charge  available 24 x 7  Raw data product  INPADOC Worldwide Legal Status  by subscription only  updates once a week W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 13. EPO INPADOC PATENT INFORMATION WORLD WIDE RESOURCE LEGAL STATUS EPODOC EPO INPADOC EXTENDED REGISTER FAMILIES Worldwide Legal Status Open Patent Services End Users ESPACEne Commercial Hosts W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 14. Products & Services  Open Patent Services  Raw data provided on-line through web-services  Designed for automated queries returning fair amounts of data  ESPACEnet - EPO Patent Register  Patent information provided on-line in end-user format  Designed for use by the general public  INPADOC Worldwide Legal Status  Raw data provided weekly through the down-load area  Designed for use by commercial hosts and patent professionals W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 15. FACTS of LIFE  We can only give as much as we get ...  depend on the accuracy and timeliness of data providers  cannot guarantee that ALL legal events are covered  It is not uncommon ...  NOT to receive a notification of reinstatement after a lapse  to receive a LATE notification of reinstatement after a lapse W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 16. FACTS of LIFE  What we give is as good as we get ...  do not insert legal events unless received from the provider  do not remove legal events once received from the provider  do not correct legal events unless requested by the provider  That means that ...  "lapse due to non-payment of fees" will not be removed from the database when followed by a late "payment of fees"  "notification of reinstatement" will not be added to the database on evidence provided by 3rd parties W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 17. DISCLAIMER  EPO does not accept any responsibility for the accuracy of data and information originating from other authorities  EPO does not guarantee that they are complete, up-to-date or fit for specific purposes W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 18. Why this "Disclaimer" ... ?  Worldwide Legal Status is as good as the data it gets  notification of a lapse may not have been given  notification of reinstatement may be late  notification of reinstatement may not have arrived  Worldwide Legal Status cannot guarantee legal certainty  inside worldwide legal status the patent might be "dead"  out there the patent may be "alive and kicking" W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 19. Business decision to make ... ??  Use Worldwide Legal Status to get a general idea  Double-check against the national register at all times W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 20. So .... this is how the data flows at the EPO How does the data flow at your office ? W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 21. Couple of questions for you :  How have you organised your data flow ?  How do you make your data available ?  data-format : PDF, XML, SGML, ... , other?  medium : internet, E-mail, electronic file transfer?  If in PDF - what format was it in before it became PDF ?  mark-up language: XML, SGML or even INID- code?  any other format that allows electronic transfer? W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 22. We will give the floor to the participants W Fenny Versloot-Spoelstra Amo istre Rodriguez Del
  • 23. EXAMPLES OF GOOD PRACTICE LATIPAT November 2012 Wistre Rodriguez Del Amo
  • 24. We will take the participants through some examples ... Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 25. OUR "WISH LIST" ...  Delivery Method  Internet site with stable URL  FTP server  Data Format  generally any mark-up language will do  preferably data in XML  not desirable are formats like TXT or PDF  Content .... Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 26. Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 27. if you provide us with more than just the new event tell us which of the events is the new event clearly indicate when the event was made public identify nature of the event by unique code description in your own language if possible translation in English Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 28. clearly indicate when the event has become effective clearly indicate the application / publication that this event is relating to change of ownership, assignments, ... clearly indicate previous and new owner when in "exotic" original character set provide names and addresses transliterated supplementary protection certificates clearly indicate the vital components Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 29. THUMBS UP for :  Posting your data on the internet or on FTP  Providing your data in structured mark-up language  Clearly identifying the nature of the legal event  Supporting consistent and unambiguous number series  Making sure that we understand what we get :  documentation is vital  English language translations are helpful Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 30. What is a legal event? Can you give me some examples of legal events? Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 31. A legal event can be • Any kind of invalidation, e.g. lapses, expiries, withdrawals, revocations, etc. • Limitations • Reinstatements • Fee payments • Grant • Change of ownerships • Change of representatives • Licensing information , e.g. willing Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 32. Which legal events are in the worldwide legal event database? In the worldwide legal event database are no legal events that are in DOCdb (i.e. bibliographic data) Which legal events can be coupled with bibliographic data? Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 33. Events received by bibliographic data • Priorities • Filing an application • Each publication step (i.e. normally also grant) • For EP documents also – previously files application – preceding publication date – coming into force  We produce Extended legal event data to cover these events as raw data Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 34. Which legal events are in the worldwide legal event database? Why are different legal events collected for each country? (i.e. not always the same kind of events for each country) Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 35. The reasons for different kind of data are • Each country has a different patent law • Each patent office sent us different data • The collection of each country started at the different moment Side effect We receive data from very different sources and none of them can guarantee completeness and correctness of their data  We cannot guarantee the completeness and correctness of our data Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 36. Which legal events are in the worldwide legal event database? How many patent authorities are covered by legal event data? How many records are in the legal event database? Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 37. Statistical data of the legal event database • Number of records March 2012: – 100 000 000 • Expected number of records end of 2012: – 120 000 000 • Number of patent authorities we have received data from 2012: – 42 • Overall number of patent authorities we have data from: – 62 • PCT entry data from WIPO (not sent directly to us) • not existing countries (like GDR) • patent office stopped sending us data Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 38. Which information is in a legal event record? Here is a legal event from espacenet: Application Number Publication Date Country Code Legal Event (what happened) Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 39. Which information is in a legal event record? Here is the same legal event from espacenet: Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 40. Where can you find worldwide legal event data? Where can you search for legal event data? Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 41. Legal events can be received via EPO tools –espacenet –OPS –PATSTAT (add on) –European Register (only EP patents) –as raw data, sent to subscribers Commercial partners −STN −Thomson Scientific −Questel/Orbit −Dialog Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 42. What is a legal event with PRS code "REG "? In espacenet one can see this information .... IE = Ireland Which patent office has provided this information? Why has this information a code "REG " before the real code? Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 43. Why there are "REG " codes? In the PRS database only the country code of the patent is included. The PRS code consists also of these 2 parts: Country Code 4 digit event code The country code of the PRS code is not included in PRS and most of the tools you can search for legal event data => Country code is taken from patent identification Therefore an original European patent has to have an EP Code (= "REG ") and the real national code is hidden in an attribute. => in our example: EP REG Rodriguez Del Amo IE FG4A Wistre Versloot-Spoelstra Fenny
  • 44. How should "REG " codes be interpreted? Something happens with a patent filed in a regional office or of a country with a number (here EPO patent 1456342) of another patent authority The patent office the event happened or has been announced by is the country (in espacenet) behind "REG " (here Ireland) What happened says the code behind the country (here entry of EP patent into the Irish national phase) All attributes rely on the "real code" (here original document was published in French) Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 45. My further question? For what are legal event data useful? (also in combination with another patent information) Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 46. My further question - use for legal status data? • Where (in which countries) is an invention still protected? • Where is the present owner of an invention and where? • How long is a patent protected? – in a technical field – by an applicant – etc. • What happened with an invention in different countries? • etc. Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 47. Résumé Worldwide legal event data is a valuable source to answer interesting questions (especially for the industry) for the protection of inventions and for patents. Wistre Rodriguez Del Amo Fenny Versloot-Spoelstra
  • 48. Questions ? Comments ? W Fenny Versloot-Spoelstra Amo istre Rodriguez Del 21/11/12

Editor's Notes

  1. We will kick-off taking the participants through our data flow - all the efforts we put in, the challenges we face, give them a bit of context Next the participants will take the floor and tell us about their working practices. Then Wistre will take the participants past a couple of real-life data feed examples. Last we will try and give them an idea of what it is that we are expecting from them.
  2. Over 40 national offices are making legal status data available to us, either by sending their data to our EPO front office or through their websites, over FTP servers, in E-mail attachments Let's have a look at the sunny day scenario first and follow the green line <C> Our support team take and pre-process the raw data - "cook" the data if you like - so that our validation and conversion processes can digest it. At the moment we are maintaining at least one dedicated process per data provider. Valid data is loaded into the master database. Once a week the data is made available to you - the end user - in our on-line services and raw data products. That is the sunny day scenario - but into each life some rain must fall ... <C> Invalid data and quality issues are being intercepted in our validation processes and slotted through to our support team. After consultation with the data analyst and possibly some troubleshooting by our maintenance team, corrected data and resolved issues will be added to the database and find their way to you - the end-user. <C> It is not only invalid data and quality issues that require intervention. Whenever we receive new data for an existing provider or add a provider to the list or experience a change of format, our data analyst and maintenance team will have to analyse the new situation and very likely have to set up a new process and a new procedure.
  3. All of those are challenges that we have to face : <C> Variety in delivery methods .... <C> Ever changing environments .... <C> Human resources
  4. <C> At this very minute our maintenance team are on the verge of deploying a data flow platform that will help us manage delivery methods, manage changing environments, reduce manual intervention. <C> This platform is polling websites and servers and pulling the data in as soon as it becomes available <C> It is triggering the dedicated processes that are "cooking" the data <C> It is running a powerful business rules engine to validate the data <C> It is pushing the data towards the master database Now all of this high-tech stuff does not mean that we do not need any people anymore ... <C> This data flow platform - however sophisticated - will need to be maintained and monitored <C> Intellectual intervention will still be required to clear any anomalies from the database and to keep our customers happy <C> Changing parameters will still need to be assessed and analysed.
  5. Maintaining the database Here there are two things that give us a pain behind the eyes <C> The office specific nature of the data when trying to get the data into the database : language issues, event codes uses, meta-data provided The availability of the bibliographic data when wanting to get data out of the database and off to you. The availability of bibliographic data is a prerequisite for the exchange of legal status data.
  6. Let's have a look at just a selection of the challenges that we have to face : <C> Identifying the nature of the event. Events of the same nature are more often than not identified by different legal status codes from one providing office to the next. Code descriptions in "exotic" language do not make it easy to understand the nature of the event <C> Identifying data items in the input. Here we are depending on the tidiness of the data and the quality of the documentation <C> The link to the bibliographic data. More often than not the publication kind-code is not provided. This may lead to ambiguous number series across IPR-types. Which will make linking legal status data to bibliographic data more difficult.
  7. Our powerful Business Rules Engine can only help us here to a given extent .. <C> You can define rules to identify legal events by country-specific codes .... but you will still need careful analysis of the content <C> Which means you will still be relying on the tidiness of the data and the quality of the documentation <C> And you will still be confronted with language issues <C> With regards to the connecting legal status with bibliographic data ... <C> You can defined rules to support access without kind-code, to resolve ambiguous number series but there will still be a certain degree of "second guessing"
  8. And then there is one particular challenge ... <C> There is an ongoing trend to provide legal status data within the context of the "life of a file" .... <C> So what is the challenge here ... ? Identifying new events, THAT is the challenge ... very often there is no clear indication of what event is the new event .... very often the "date of capture" is not given ... or the date of capture is not reliable <C> So ... why not take the new life and dump the old ... I can hear you think Well, for the simple reason that we have invested time and effort in improving the quality and correcting the data. If we would just exchange the old life for the new, we would be overwriting improved and corrected data and destroy all of our efforts ...
  9. Delivering legal status to the world <C> ....
  10. Let's illustrate that with a picture ... INPADOC worldwide legal status is "on the market" as a raw data product and accessible through on-line services. Services run by the EPO - OPS, ESPACEnet and the EPO Register - and services run by commercial hosts. OPS and ESPACEnet have access to EPODOC the search and reference database that is supporting the EPO examiners in their daily work
  11. Delivery method, data format speak for themselves ... What is on our wish list content-wise, we will illustrate by taking the participants through our draft XML schema
  12. This is our proposed new format - an XML schema - that we intend to use for exporting data out of our database. It will equally well accommodate importing data into our database. What we would need the providing offices to "fill out" is this element, the element <legal-event>
  13. Elements "event-class" and "event-code generic" are not relevant when using the schema for importing the data into the database. Event-class is a "code-independent" identification that will allow for grouping legal events of the same nature across applications without any knowledge of the underlying intricate country dependent coding systems Event-code-generic is a "country independent" code that will allow for identifying a particular legal event across applications irrespective of where - with which authority - the application has been filed. Both entities are only of significance when exporting the data out of the database.