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

Distinction between use and definition of a Concept should be made explicit. #1498

Closed
hanjoosten opened this issue Sep 1, 2024 · 0 comments
Assignees

Comments

@hanjoosten
Copy link
Member

In the P-structure, we used to use a Text to identify a Concept. With the introduction of the first phase of namespaces, we decided to restrict the names of Concepts. Besides the restrictions, we added an optional LABEL.

This has some funny effects, which do not feel intuitive and/or logical. At all places where a P_Concept is used internally, one can now expect a label. A label should only be in te P_ConceptDef, not in the P_Concept. At the A-structure however, we need the optional label in the A_Concept.

@hanjoosten hanjoosten self-assigned this Sep 1, 2024
hanjoosten added a commit that referenced this issue Sep 1, 2024
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

1 participant