-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIPO patent headers = "WOWO" #52
Comments
As of this point my prototypes have not done much with foreign citations. But this does seem to occur quite often, in the data. As of right now foreign patent numbers are the way they appear in the data, with the addition to the country code. So this problems seems to occur when the patent number already has the country code, thus its repeated when the country code is added. Different countries use different numbering schemes, and I just haven't got around to researching the best way to represent them. In this case Google patents translates the number to "WO1994003095A1" |
Thanks, that's helpful. I'll decide how I want to deal with the issue for now. |
WIPO Standard ST.6 Publication Number Formatting; published December 2002 WIPO Standard ST.13, Numbering of applications for IPRs; published Febuary 2008 http://www.wipo.int/export/sites/www/standards/en/pdf/03-14-01.pdf |
Patent Document Id Variations (after quick review, likely more) 8135591 => 8135591 1 277 865 => 1277865 (EP1277865A1) WO2011049527 =>2011049527 1/75580 => 200175580 (WO 1/75580) WO 000033871.009 |
Question:
After processing by TransformerCli, in the citations section WIPO patents seem to come through with a "text"="WOWO xxxxxxx". According to USPTO documentation, the correct header appears to be "WO" (see https://www.uspto.gov/patents-application-process/applying-online/country-codes-wipo-st3-table).
Is this "WOWO" header correct, or an error? Also, given that most other country codes are adjacent to the numbers, is the space correct?
Example:
US Patent: US9234358B2
The text was updated successfully, but these errors were encountered: