About Open Patent Services (OPS) Version 3.2.

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s raw data subscription products such as 14.7 DOCDB - worldwide bibliographic master database, 14.11 Worldwide legal status (INPADOC), 14.12 EP full text in XML, 14.1 EBD and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

EPO / OPS Support
Posts: 934
Joined: Thu Feb 22, 2007 5:32 pm

About Open Patent Services (OPS) Version 3.2.

Post by EPO / OPS Support » Thu Nov 03, 2016 1:45 pm

The EPO is pleased to announce the release of Open Patent Services (OPS) version 3.2.

New features and changes

 OPS web service (in general):
• "Anonymous" test access option removed (testing v 3.2 possible via the API Console but only with “OAuth 2 Client Credentials“ switched on)

 OPS Published-data service/search:
• CQL query behaviour streamlined with Espacenet query implementation
• Searchable field "classification combination (cpcc)" added to search for CPC combination sets

 OPS Published-data service/biblio:
• CPC combination set retrieval enabled
• Citations now provided in rich format where available
Please note that although rich format is already supported, it is subject to the availability at the back end of citation data in the new format.
Further details can be found under Rich citations in Patent Information News issue 3/2016: http://documents.epo.org/projects/babyl ... 316_en.pdf

 OPS Published-data service/claims, description:
• EP-B full-text documents available in character-coded format (XML), including claims in three languages

 OPS Register service (in general):
• Adapted to accept new European Patent Register features linked to the implementation of the unitary patent (not yet visible to users)

 OPS Register service/search:
• Searchable fields "date of grant (grd)" and "appeal case number (apl)" added

 OPS CPC classification service:
• New CPC classification scheme (01.11.2016) available only in version 3.2 (that is, version 3.1 will continue to provide only the previous version of the CPC classification scheme)


To access OPS version 3.2 documentation visit:
http://www.epo.org/searching-for-patent ... .html#tab3

Planning

As was the case for previous releases, the two versions of OPS will remain in production in parallel for a certain length of time to ensure the users experience a smooth migration to the latest version. The planned schedule is as follows:

• Current: version 3.1 production environment – version 3.2 public beta
• January 2017: version 3.2 in full production – version 3.1 still available
• As from Q2 2017: discontinuation of version 3.1


Encryption protocols

We would like to remind you that, as communicated in July, we have recently added the TLS 1.1 and TLS 1.2 encryption protocols to OPS version 3.1. As TLS 1.2 is now fully supported, you should ensure that your client code establishes a TLS1.2 connection with the server.


Migration steps

• OPS version 3.2 uses the same credentials for accessing the service as OPS version 3.1.

• While migrating to OPS version 3.2 you will be able to test your client code simply by updating the URLs used from https://ops.epo.org/3.1/rest-services to https://ops.epo.org/3.2/rest-services.

• However, as part of this migration, you need to perform some additional steps to ensure that your client code is running in the most robust way possible. For backward-compatibility purposes, our servers support the HTTPS protocols SSL3, TLS 1.0, 1.1 & 1.2.

• Please note that 1.2 is the recommended security protocol for establishing an HTTPS connection.

• When reconnecting your client code to OPS 3.2, please ensure that your client code supports TLS 1.2.

• When starting your application and establishing a connection to OPS 3.2 for the first time, please check your connection logs and ensure that the handshake and connection correctly establish a TLS 1.2 protocol connection.

In the new v 3.2 version you should set your Accept request HTTP header parameter to Accept = "application/xml" as oppose to the 3.1 version where the same parameter could be left empty.

• For best-practice purposes, you should also ensure that your client cannot establish any other kind of HTTPS connection.

• The EPO plans to decommission SSL3, TLS 1.0 and TLS 1.1 in 2017. To avoid losing access to OPS when this happens, we strongly recommend that you take the above steps now.


API Console:https://developers.epo.org/now offers testing of both versions as well as possibility to test POST and GET requests for Ver. 3.2. Please make sure you have “OAuth 2 Client Credentials“ switched on when testing v 3.2 in the API Console.

For all other questions and comment contact us directly at patentdata@epo.org or post your question in this forum.

Regards,

OPS support at Patent Data Team


Post Reply