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 fields: issueTracker and issue #154

Open
nichtich opened this issue Feb 27, 2025 · 1 comment
Open

Add fields: issueTracker and issue #154

nichtich opened this issue Feb 27, 2025 · 1 comment
Labels
Milestone

Comments

@nichtich
Copy link
Member

nichtich commented Feb 27, 2025

Add field issueTracker from https://codemeta.github.io/terms/ and/or https://w3id.org/okn/o/sd#issueTracker from Software Description Ontology to Registry, ConceptScheme, and Concordance.

Not sure about an additional field issue for individual mappings, concepts etc. as subjectOf (or an additional fuzzy field seeAlso) can already be used for the same purpose. On the other hand, linking to specific issues where an item (as conceptual entity) is discussed. The difference is more clear for Concepts:

  • The concept "Apple" is the subjectOf a book about apples.
  • The management of the concept "Apple" is subject of an issue about the concept "Apple".
@nichtich nichtich added this to the 0.7.0 milestone Feb 27, 2025
@nichtich nichtich added the NFDI label Feb 27, 2025
@nichtich nichtich changed the title Add field: issueTracker Add fields: issueTracker and issue Feb 27, 2025
@nichtich
Copy link
Member Author

nichtich commented Mar 3, 2025

Looking for an RDF property for issue I found several unmaintained RDF ontologies. In particular

bom:Issue = http://www.ifi.unizh.ch/ddis/evoont/2008/02/bom#Issuehttp://www.ifi.unizh.ch/ddis/evoont/2008/02/bom#Issue

I'd vote for wf:task just because Issue Tracking Ontology because it has been created by TBL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant