Skip to content

How to deal with variable naming in Knowledge Gap detection? #555

@Sophietje

Description

@Sophietje

When detecting Knowledge Gaps, different knowledge bases/interactions may use different variable names. However, when combined with reasoning, these variable names may actually refer to the same thing. How should we deal with variable naming when detecting knowledge gaps? Should we replace all occurrences of variables in the consequent by the names used in the antecedent?

I came across this issue when working on #519 (see testKnowledgeGapNoMatchingVars() or make a test where, in a similar setting, the domain knowledge uses a different variable name)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions