Page 1 of 1

Ambiguous response when querying published data for Japan with a wild card kind code

Posted: Tue Jan 16, 2024 11:45 am
by ofipify
Hi,

We are using a request like the one below to grab all published documents for a publication number, using a wild card in lieu of the kind code.

Code: Select all

http://ops.epo.org/3.2/rest-services/published-data/publication/docdb/EP.1234567.%/biblio
This does not seem to work for Japanese patents. A request to:

Code: Select all

http://ops.epo.org/3.2/rest-services/published-data/publication/docdb/JP.3232777.%/biblio
results in 413 Request Entity Too Large:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault xmlns="http://ops.epo.org">
    <code>CLIENT.AmbiguousRequest</code>
    <message>The request was ambiguous</message>
    <details>
        <cause>Ambiguous input: publication/docdb/JP.3232777.*</cause>
        <resolution>publication/docdb/JP.3232777.B2</resolution>
        <resolution>publication/docdb/JP.3232777.U</resolution>
    </details>
</fault>
The difference in behaviour is a bit confusing. I would also suggest that 300 Multiple Choices would be a better HTTP status code in this instance.

Thank you.

Re: Ambiguous response when querying published data for Japan with a wild card kind code

Posted: Thu Jan 18, 2024 10:44 am
by EPO / OPS Support
Hi,

In fact, that is a feature of OPS and not a mistake in response. The ambiguous seed informs you that your query has to be amended because there are two (or more) documents found that correspond to your number query. You have to choose one of the proposed options in order to display it.

Regards
Vesna
OPS support

Re: Ambiguous response when querying published data for Japan with a wild card kind code

Posted: Fri Jan 26, 2024 2:42 am
by consentmainmast
I think this is a characteristic of OPS