New annotations proposed: "user interface label", ...

[zhengj2007]

From @Public-Health-Bioinformatics on July 6, 2018 7:33

In GenEpiO I have "user interface label" and "user interface definition" and "user interface help" annotations that one can include in a term, and they are geared for selection lists and user help display etc. in software. They usually end up being shorter, abbreviated and lay-oriented text rather than ontology labels and definitions that are designed to satisfy an ontology search engine or convey aristotelian logic. The original label and definition remain available for source attribution and reference and "deeper" help info in user interface if desired.

Does this appeal? It seems to me these terms should be in IAO. The main motivation for having these as annotations situated in an ontology rather than in an external term mapping system is that then all community users can get the benefit of centrally managed and recommended user-interface-oriented terms for their apps in a simple way. A further step to software standardization. (However a user would still have the ability to override such terms with their own customizations).

p.s. ui label is different from "editor preferred term" in that it addresses the tuning one does for user interfaces.

Copied from original issue: information-artifact-ontology/IAO#205

[zhengj2007]

@Public-Health-Bioinformatics There is separate repository "ontology-metadata" that discuss about the annotation properties used for an ontology term. So, will move the issue to that repository.

[Public-Health-Bioinformatics]

ok, thanks Jie, I didn't quite realize that was the annotation hangout.

[zhengj2007]

We are planning to separate ontology-metadata.owl development, aiming to be used by all OBO Foundry ontologies, from IAO. That's why this new repository created.

[alanruttenberg]

@Public-Health-Bioinformatics suggests adding software specific labels and definitions, which could be of benefit to others and I support the idea. However let's not make the assumption that there's just one software so that we don't land up having two pieces of software conflict. Instead have class like SoftwareMeta, which could have a link or label for the software and then whichever differing properties they want, and which would be linked by an annotation property (hasAppMeta) to the term. So suppose we have a class C. Then

mywebapp a SoftwareMeta. mywebapp forSoftware "..."

C hasAppMeta mywebapp mywebapp 'user interface label' 'blammo' mywebapp 'user interface definition' 'a shooter' ...