-
Notifications
You must be signed in to change notification settings - Fork 18
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
Does the distinction between hasProperties and hasStandoffProperties make sense? #760
Comments
And actually, do we need |
I guess that would make sense. Actually, we also flagged value classes in a way so they can be distinguished from resource classes. So we could also flag standoff classes. |
OK, so I will make it like this:
And I will add flags to distinguish resource classes from standoff classes, and resource properties from standoff properties. |
Just keep in mind that the ontology service in the SALSAH GUI might have to be adapted accordingly. |
Actually, sorry, what I just said makes no sense, because is Do we actually need to flag standoff properties? Isn't it enough that we have the cardinalities in standoff classes, to find out which properties they need? |
If they show up like other properties, the GUI will display them in the extended search form if they cannot be distinguished from other props. |
Doesn't that just mean that the GUI needs to know which properties are resource properties (which it should use in the extended search form)? Why would it need to distinguish between, say, |
In the JSON-LD returned by the ontology routes, some properties go in
hasProperties
(if they’re used on resources or values), and others go inhasStandoffProperties
(if they’re used on standoff tags). But what if a property is used both on values and on standoff tags (likevalueHasUri
)? Where should it go? Should we even have this distinction, or could we get rid of it?The text was updated successfully, but these errors were encountered: