Skip to content
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

Differences between USPTO and PrArAr #5

Open
slifty opened this issue Sep 20, 2019 · 2 comments
Open

Differences between USPTO and PrArAr #5

slifty opened this issue Sep 20, 2019 · 2 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@slifty
Copy link
Collaborator

slifty commented Sep 20, 2019

It looks like the Prior Art Archive search syntax is slightly different than those documented at the USPTO search site (see the resources in #3).

What is the reason for those differences; is there a different USPTO standard than the one listed in the USPTO resources? Do we really want to diverge from that standard?

Specific differences I see so far

  • PrArAr lists several operators (e.g. ADJ, NEAR, WITH, SAME) that are not in USPTO.
  • PrArAr seems to prepend @ before field names, wheras USPTO uses a / syntax (e.g. @RLAD vs RLAD/
  • USPTO lets you look up by cpc code using the CPC/ field, PrArAr seems to support a .cpc format
  • PrArAr supports some shortcuts such as | and ~
  • PrArAr supports something called BOOST (and a shortcut of ^)
  • PrArAr supports $n which is like $ but with a set number of characters.
@slifty slifty added the question Further information is requested label Sep 20, 2019
@metasj metasj added the documentation Improvements or additions to documentation label Sep 20, 2019
@slifty
Copy link
Collaborator Author

slifty commented Oct 2, 2019

I spoke with Shikha about this and got a copy of the documentation that they used to work on the original Prior Art Archive query parser. There are internal documents that are more robust (and slightly different in some ways) than the USPTO patent search instructions. I'll add those to a /docs directory separately and use that to close this issue.

@slifty
Copy link
Collaborator Author

slifty commented Oct 14, 2019

There are still some oddities, which are a bit more explicit when you look at the sample queries provided in #10

For example, none of the documentation talks about the use of @ (e.g. in @ad<"20141215" @rlad<"20041215" which is the first sample query)

It also appears that the expected default in parsing is to treat multiple terms with an OR not an AND which contradicts this documented requirement:

image

Here are some of the documentation files I'm working from:

Filter class & Parboiled Parser.docx
east west operators.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants