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

Add info to association qualifiers describing which part of the statement they apply to #1514

Open
Woozl opened this issue Jun 20, 2024 · 2 comments
Labels
question working-group/ROBOKOP Not really a working group per se

Comments

@Woozl
Copy link

Woozl commented Jun 20, 2024

We're developing a UI to allow the creation of fully-qualified statements using associations and noticed during the process that there doesn't seem to be a way to tell which part of the statement a qualifier applies to. We'd like to be able to know this to co-locate the qualifiers in the UI with the part of the statement they describe. The model already defines the type of the qualifier with the normal is_a hierarchy, so I'm not sure if the best method is another slot like defines or applies_to:

  subject context qualifier:
    is_a: context qualifier
+   applies_to: subject
    in_subset:
      - translator_minimal

Or if it's better to have some abstract qualifiers that can be mixed in:

+ subject qualifier:
+   abstract: true

  subject context qualifier:
    is_a: context qualifier
+   mixins:
+     - subject qualifier
    in_subset:
      - translator_minimal

Or maybe there's another way to do this that's easier. I think we only need to differentiate between "subject", "object", and "statement" qualifiers (I believe predicate qualifiers will always be qualified predicate but I may be wrong).

@nlharris
Copy link
Contributor

Hi @Woozl, thanks for submitting this question/request. Are you associated with Translator?

@Woozl
Copy link
Author

Woozl commented Jun 21, 2024

Hi, yes, we're working on the ROBOKOP UI.

@nlharris nlharris added the working-group/ROBOKOP Not really a working group per se label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question working-group/ROBOKOP Not really a working group per se
Projects
None yet
Development

No branches or pull requests

2 participants