-
Notifications
You must be signed in to change notification settings - Fork 0
Requesting & Curating New Specification Elements
As projects and technologies evolve, so must the data specifications that support them. New tools, practices, and techniques often emerge, necessitating updates to the specification to accommodate these advancements. This ensures that our specification remains relevant and comprehensive.
New terms and fields are requested through our GitHub issues repository. To expedite the process, we encourage requests to be well curated. Well-curated terms facilitate quicker review and integration into the ontology and subsequently the specification.
- Avoid Composite Terms: Terms should represent single, clear concepts rather than composite ideas.
- Generic Terms: Terms should be as generic as possible to maximize their applicability across different contexts.
- Check Existing Ontologies: Ensure that the term does not already exist in other ontologies. This avoids redundancy and promotes consistency.
- Supply an Appropriate Parent Class: Identify and supply an appropriate parent class for the new term. An easy way to find suitable parent classes is by checking existing terms in a picklist and seeing if they have similar parents. Additionally, you can use the EBI Ontology Lookup Service (OLS) to look up potential parent classes.
- Provide a Definition: A clear and precise definition should be supplied for the term. This helps in understanding the term's intended use and scope.
New terms and fields should be requested through the issue request form. For individual requests, you will need to fill out the appropriate informatiom in the relevant form. For bulk requests however, it is recommended to use the template. Make a copy of the template and fill out the requested information. Ensure that you have enabled sharing access to this, before providing the link in the bulk issue request form.