TASK 3. Contribute to ONS

We encourage users to contribute to the ONS on every aspects of the ontology.

Contributing with issue tracker

The Github repository issue tracker is the preferred way of contribution to ONS. In fact, the Github issue tracker system makes all edit proposals traceable, and allows for open discussion among users and developers/maintainers on the proposed edit.

To contribute, the user firstly need to possess a Github account (which can be created here) and log in.

Requirement for a edit/improvement request:

1. Use tags in the title indicating the type of issue you are posting. Allowed tags (subjected to change) are:

   • [Existing term modification] to propose modification in an existing term/class. Every part of the term can be modified: definition, label, super-classes, relations
   • [New term request] to propose addition of a missing term/class.

2. Detail the requests following these templates, containing the minimum information necessary for a change:

   • [Existing term modification]

     • Class label (i.e. Food)
     • Class prefixed name (i.e. ONS_0000079)
     • Item to edit (i.e. Textual definition, Relation with other classes, Annotation, other)
     • Edit (indicate the proposed editing)

   • [New term request]

     • Proposed label
     • Proposed Super-class (to be identified among classes already inserted in ONS)
     • Proposed Sub-class
     • Proposed textual definition (i.e. the formal and technical english description that should be associated to the term).
     • Proposed relations with other classes (propose in the form of triplet, preferably using properties already inserted in ONS)

After posting an issue, the developer will be notified and will process the request. Occasionally, both from the developers and from other users, a discussion about the proposed changes or additions can develop. This process eventually could lead to refine and improve the proposal, or other classes in ONS connected to it.