You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
ADJ
,NEAR
,WITH
,SAME
) that are not in USPTO.@
before field names, wheras USPTO uses a/
syntax (e.g.@RLAD
vsRLAD/
CPC/
field, PrArAr seems to support a.cpc
format|
and~
BOOST
(and a shortcut of^
)$n
which is like$
but with a set number of characters.The text was updated successfully, but these errors were encountered: