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

Data Property instances #25

Closed
valeriosantarelli opened this issue May 19, 2019 · 1 comment
Closed

Data Property instances #25

valeriosantarelli opened this issue May 19, 2019 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@valeriosantarelli
Copy link
Contributor

Disallow incorrect ordering of input edges when the pair of individual nodes are an instance of an attribute.

For a pair of individual nodes, if they are an instance of an attribute, the first input edge connecting the respective node to the Property assertion node should be of type (individual) and the second one should be (Value).

The above property should hold even when the type is switched i.e. under all scenarios.

@valeriosantarelli valeriosantarelli added the bug Something isn't working label May 19, 2019
@valeriosantarelli valeriosantarelli added this to the Eddy v1.2.0 milestone May 19, 2019
mnamici added a commit that referenced this issue Jan 15, 2020
@mnamici
Copy link
Collaborator

mnamici commented Jan 15, 2020

Currently this has been fixed by disabling the switch to value toggle on individuals connected as subjects to a DataPropertyAssertion and only allowing to connect value nodes after having connected the DataPropertyAssertion subject. Existing diagrams containing literals as subjects will have to be fixed manually though.

@mnamici mnamici closed this as completed Jan 15, 2020
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

2 participants