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

Repetition among matches #19

Open
yfaria opened this issue Aug 24, 2021 · 1 comment
Open

Repetition among matches #19

yfaria opened this issue Aug 24, 2021 · 1 comment

Comments

@yfaria
Copy link
Contributor

yfaria commented Aug 24, 2021

Sometimes, the matches "collide" with themselves, which is not necessarily a problem but in the interface it may be confusing.
For example, when I run the query

h1:[rstr h2] 
h3:[]

It's possible that h1 matches with the same predication as h3. When it doesn't it, it is displayed as expected:
image

When it collides, one example is like that:
image

Maybe there should be a color change when there is more than one match in a predicate.

@arademaker
Copy link
Member

arademaker commented Aug 24, 2021

We may need to expose the project to DELPH-IN members to have feedbacks. See delph-in/docs#24

In the meantime, I believe we have two questions here:

  1. do we want that h3: [] denote any predication? Because h:[* x] is a predication with hole h with an argument with x as value... so if we omit the pattern inside the brackets we are saying anything? So what is the denotation of the empty string as a query?

  2. different variables may have the same bind or not? If I have h1 and h2, do we adopt the standard FOL semantics where they can both point to the same individual or we adopt a more practical approach were different variables should not have the same bind... what is the SPARQL semantics for that? I need to double-check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants