Is "description" supported by this client?
I did not find "description" or "claims" under the table "Currently the Client knows how to issue request for the following services:". Is it supported by this client yet? (I am not familiar with python...) thanks a lot. what I have tried:
response = client.published_data(
reference_type = 'publication', # publication, application, priority
input = epo_ops.models.Epodoc('EP1000000'), # original, docdb, epodoc
endpoint = 'description', # optional, defaults to biblio in case of published_data
constituents = [] # optional, list of constituents
)
I would also like to know this. Is this python package still supported?
I'm not actively working on this project anymore, so welcome anyone to take it over.
As for supported features, only the documented ones are supported. If it's not supported, you can probably easily add it.
I believe OPS now supports JSON? So if I were to start the project today, I would choose JSON instead of the legacy XML.
Dear @ohofherr and @gsong,
at GH-60, I made a start to discuss future maintenance. Anyone who would be up for co-maintenance, please raise your voice.
With kind regards, Andreas.
Dear @baskgithub,
thank you for writing in.
According to this code in PatZilla, epo-ops-client can successfully be used to retrieve descriptions and claims from the EPO OPS HTTP API.
Relating to your report, do you suggest to just update the documentation correspondingly, in order to better educate users, or did you actually miss the feature, or experienced problems using it?
With kind regards, Andreas.
This discussion thread also outlines that retrieving descriptions is supported, and mentions some guidelines how to make it work.
- https://github.com/ip-tools/python-epo-ops-client/discussions/56
Maybe it is really just the documentation which needs a corresponding improvement?
I'm not actively working on this project anymore, so welcome anyone to take it over.
As for supported features, only the documented ones are supported. If it's not supported, you can probably easily add it.
I believe OPS now supports JSON? So if I were to start the project today, I would choose JSON instead of the legacy XML.
Is the XML really 'legacy'? I've been using it via pydantic-xml, which is quite convenient. However, I agree that JSON probably works a lot better... Do they provide JSONSchema?
Cheers,