Idea: visualization patterns
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- data-visualization, design
Research direction
No implementation files or tests are named. Start by reviewing the lattice example at QuickGO and the multi-axial-ontology-test repository, then clarify the scope and format of visualization guidance for design patterns. Done requires an agreed specification and an implemented, usable approach for showing class-expression graphs and pattern-specific visual guidance.
Written by the indexing model from the issue text.
Description
Each design pattern could come with 'visualisation patterns'. Some kind of analog of style sheets that provide hints on the best way to show term graphs.
As a guiding example consider the lattice:
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0099638#term=ancchart
A generic improvement would be to unfold one or more steps and show graphs for each class expression. See this repo for examples: https://github.com/cmungall/multi-axial-ontology-test
But different DPs could have specific guidance or code. For example, for a transport DP, we can imagine cell maps with an arrow connecting source to target, with the edge labeled with the cargo.
From a discussion with @ValWood and @kltm
- Dominant language
- Python
- Stars
- 49
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from INCATools/dead_simple_owl_design_patterns
-
`test_text_fields` validator ignores `dataProperties` and `annotationProperties`Possibly taken @forest-savage1234 claimed this 55 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Request: new field for synonym permutationsPossibly taken @matentzn claimed this 319 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
INCATools/dead_simple_owl_design_patterns#87 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
schema_ext
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
INCATools/dead_simple_owl_design_patterns#67 · 3 comments ·
All issues in INCATools/dead_simple_owl_design_patterns
Similar issues
-
README.zh-CN/ja/es still hard-code 501 test counts after README.md went count-freePossibly taken @Aaqibhafeezkhan claimed this today. Openbeginner documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BistaDinesh03/critique#164 · 1 comment ·
Maintainers usually reply within 1 day
-
bug IO
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MrNeRF/LichtFeld-Studio#3824 ·
Maintainers usually reply within 1 day
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-webui/open-webui#33200 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days