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

[Technical Report] First-order Variable Terms should not be concepts #65

Open
ccrock4t opened this issue Nov 16, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@ccrock4t
Copy link
Collaborator

ccrock4t commented Nov 16, 2023

Technical Report

Variable terms, or certain compound terms containing variables, do not correspond to concepts.

More Info

It is not creating atomic variable terms, which is correct, but it is incorrectly creating first-order statements with variables.

e.g., For inputting a statement <<#x-->A>==><#x-->B>>, the concepts <#x-->A> and <#x-->B> appear in the Memory

Note that the higher-order statement (<<#x-->A>==><#x-->B>>) should remain the memory, despite that it contains variables.

@ccrock4t ccrock4t added the bug Something isn't working label Nov 16, 2023
@ccrock4t ccrock4t changed the title [Technical Report] Variable Terms should not be concepts [Technical Report] First-order Variable Terms should not be concepts Nov 16, 2023
@ccrock4t ccrock4t changed the title [Technical Report] First-order Variable Terms should not be concepts [Technical Report] [Bug] First-order Variable Terms should not be concepts Jan 16, 2024
@ccrock4t ccrock4t changed the title [Technical Report] [Bug] First-order Variable Terms should not be concepts [Technical Report] First-order Variable Terms should not be concepts Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant