When I do the following request with my browser: http://ops.epo.org/3.1/rest-services/legal/publication/docdb/JP.S5582191.* I get the following fault, which is perfectly OK, as I know how to deal with this. <fault> <code>CLIENT.AmbiguousRequest</code> <message>The request was ambiguous</message> <de...

Thank you for your reply.

We have changed our tests to use the request
http://ops.epo.org/3.1/rest-services/legal/publication/docdb/JP.S5582191.*

This provokes the error we want to test.

Thank you for your reply.

We are using this request to provoke an error, to see if we handle errors correct. So you are right, we are in a truncated family situation, on purpose

Thank you for checking with technicians.

Thank you for the reply.

As an example, when fetching the family for http://ops.epo.org/3.1/rest-services/family/publication/docdb/US.2003082717.* You can see right at the top that a priority-claim with an invalid document-id is returned. It is invalid as the doc-number is missing: "priority-claim": { "@kind&...

Hi there, similar to my previous question, we have another test that fails, now. We do request bibliographic and legal data of a large family by http://ops.epo.org/3.1/rest-services/family/publication/docdb/US.2003082717/legal,biblio We were used to get an error as follows code 503 message SERVER.Li...

Hi there, we have noticed that the web service behaves differently than used to do. The test we wrote worked with version 3.0 in June 2012. We do the following request http://ops.epo.org/3.1/rest-services/family/publication/docdb/WO.9944063.*/legal In the past we received an error when performing th...

I have not found it in the documentation, so I ask here. In order to reduce the bandwidth used on our side and on your side, we could employ gzip compression. In order to use it as a client I would indicate that I support compression by setting the appropriate header value: Accept-Encoding: gzip Is ...

We develop test driven, as such we make heavy usage of unit and integration tests. In conjunction with our Jenkins server this may produce load on your side and it consumes our quota. For our unit tests we use moquito * so that theses tests do not contact your server. But to test if we are using OAu...

For googlers, this has been answered here.