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

Term proximity matching with exclusive list of allowable terms #96

Open
bramiozo opened this issue Jun 3, 2024 · 2 comments
Open

Term proximity matching with exclusive list of allowable terms #96

bramiozo opened this issue Jun 3, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@bramiozo
Copy link
Collaborator

bramiozo commented Jun 3, 2024

The proximity matching is very useful in case the expression between START and END tokens are specific in scope.
It might occur in practice that there are multiple types of expression between START and END tokens. To facilitate a specific scope it is useful to have an exclusive list of allowable terms for the proximity list.

@vmenger
Copy link
Collaborator

vmenger commented Jun 3, 2024

Not totally sure if I get this one, have an example?

@bramiozo
Copy link
Collaborator Author

bramiozo commented Jun 4, 2024

Suppose, I am interested in:

No, red, green or blue sheep and similar statements, indicating, the absence of any type of sheep.

So, I use

sheep_term = Term("No sheep", proximity=K, fuzzy=L..)

But now
No, there are plenty of sheep is also flagged by the matcher.

In practice this might be limited to e.g .specific descriptors, plus some connecting words.

@vmenger vmenger added the enhancement New feature or request label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Later
Development

No branches or pull requests

2 participants