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

oekg-specific annotations are needed #1529

Open
5 tasks
l-emele opened this issue May 3, 2023 · 3 comments
Open
5 tasks

oekg-specific annotations are needed #1529

l-emele opened this issue May 3, 2023 · 3 comments
Assignees
Labels
[B] restructure Restructuring existing parts of the ontology enhancement New feature or request OEKG important for knowledge graph generation ontology infrastructure

Comments

@l-emele
Copy link
Contributor

l-emele commented May 3, 2023

Description of the issue

ideas from OEKG:

Ideas of solution

If you already have ideas for the solution describe them here

Workflow checklist

  • I discussed the issue with someone else than me before working on a solution
  • I already read the latest version of the workflow for this repository
  • The goal of this ontology is clear to me

I am aware that

  • every entry in the ontology should have a definition
  • classes should arise from concepts rather than from words
@l-emele l-emele added [B] restructure Restructuring existing parts of the ontology To do Issues that haven't got discussed yet OEKG important for knowledge graph generation labels May 3, 2023
@l-emele l-emele added this to the oeo-release-1.15.0 milestone May 3, 2023
@stap-m stap-m added enhancement New feature or request ontology infrastructure labels May 3, 2023
@l-emele
Copy link
Contributor Author

l-emele commented May 12, 2023

annotation for classes that oekg should neglect: oekg ignore = true

Probably not the oekg should ignore these classes but the scenario factsheet, right?

@stap-m stap-m moved this to OEO to requirements in factsheets + scenario bundles Jun 23, 2023
nelekoehler added a commit that referenced this issue Sep 12, 2023
@l-emele l-emele changed the title annotation for classes that oekg should neglect annotation for classes that the scenario factsheet should neglect Jan 22, 2024
@l-emele
Copy link
Contributor Author

l-emele commented Jun 13, 2024

Issue OpenEnergyPlatform/oekg#19 in the OEKG has shown a potential second use case: to mark classes that could be used as a descriptor in a bundle.

So what about: An annotation that specifies how an entity should be used by the OEKG or the scenario bundles.
Allowed values:

  • ignore: Entity will not by shown in hierarchical structures (e.g. of sectors or energy carriers)
  • descriptor: Entity will be used in the scenario bundles as option to be selected as descriptor.

@stap-m stap-m changed the title annotation for classes that the scenario factsheet should neglect oekg-specific annotations are needed Aug 16, 2024
@stap-m
Copy link
Contributor

stap-m commented Aug 16, 2024

Since the descriptor annotation is requested for in OpenEnergyPlatform/oeplatform#1718 again, and there is an agreement on that in OpenEnergyPlatform/oekg#19, I will add this annotation now, so that it can be used for the bundles.

@github-actions github-actions bot removed the To do Issues that haven't got discussed yet label Aug 16, 2024
stap-m added a commit that referenced this issue Aug 16, 2024
stap-m added a commit that referenced this issue Aug 19, 2024
…tor-annotation

add oekg specific annotation #1529
@github-project-automation github-project-automation bot moved this to In discussion in Issues Aug 29, 2024
@l-emele l-emele removed their assignment Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[B] restructure Restructuring existing parts of the ontology enhancement New feature or request OEKG important for knowledge graph generation ontology infrastructure
Projects
Status: In discussion
Status: Requirements to OEO
Development

No branches or pull requests

6 participants