Skip to content

Glossary Management

mfontsan edited this page Feb 27, 2018 · 8 revisions

The ePO Glossary is fundamental for the Ontology to represent the exact knowledge about the eProcurement as understood and used in Europe.

Hence the contribution of the experts in the e-Procurement business domain is crucial. Anyone interested in contributing to the improvement of the ePO Glossary is welcome to propose new concepts and definitions or to suggest modifications to the existing ones.

How to contribute

If you want to contribute to the improvement or extension of the ePO Glossary:

If you are not yet a member of the Working Group, you must first register as such. Contact an EPO Administrator to register;

How to improve a concept

  1. Open the Glossary spread-sheet;
  2. Search for the concept you want to improve in the spread-sheet;
  3. Copy the text of the concept, in column "B". Now you have it in the clipboard;
  4. Go the GitHub "Issues" space (tab "Issues") and create a new Issue;
  5. In the title of the new Issue introduce GLOSSARY-; and
  6. Paste the concept you copied in the clipboard; e.g. Abnormally low tenders; and
  7. Add a very short text related to the issue, e.g. : definition improvement;
  8. Provide a sufficient description of what is the issue in the current definition and how you to propose to improve it. At the end of your proposal provide always the new definition that includes your proposal;
  9. Assign the label "Glossary" to the Issue (see example below);
  10. Submit the issue.

Example:

Glossary Issue

How to create a new entry in the Glossary for a new concept

  1. Go the Github "Issues" space (tab "Issues") and create a new Issue;
  2. In the title of the new Issue introduce GLOSSARY-; and
  3. Introduce a text representing the concept; e.g. **Economic Operator"; and
  4. Add the text : New concept; and
  5. Provide the definition of the new new concept; and
  6. Assign the label "Glossary";
  7. Submit the issue.

Example:

New Glossary Concept

How to search for issues related to the Glossary

You can either:

  1. Search for issues labelled with "glossary"
  • Click on "Labels":

![Searching labels]https://github.com/eprocurementontology/eprocurementontology.github.io/blob/master/images/GlossarySearchingByLabel_1.png)

  • And click on "glossary", this will return the list of issues related to the glossary:

List of labels

  1. Or you can search for issues the title of which contain the word "GLOSSARY", optionally followed by the text representing the concept. This will filter the list of issues containing the text introduced in the search field:

Filtered search

Discussions and decisions about the Glossary

Creating issues requesting changes about the entries of the glossary or asking for the creation of new entries is intended to start collaborative discussions that MUST end in a final decision agreed by the majority of the members of the Working Group.

To discuss about definition changes or new entries requests search for the issue and add your own comment. At some point, the Working Group will agree on the issue and will close it:

Glossary discussion thread

Maintenance of the ePO Glossary spread-sheet

The final decisions MUST be gathered in the ePO Glossary spread-sheet (tab "ePO Dictionary" of the spread-sheet).

The Technical Team (TT) in charge of the development and maintenance of the ePO, and only them, SHALL regularly peruse all the closed issues related to the ePO Glossary and WILL ensure that the entries in the ePO Glossary spread-sheet are correct and up to the date.

Glossary

Conceptual Model (CM)

OWL Files

Mappings between TED form v2.0.9 and ePO v2.0.1

ePO Reg2015 - Application Profile

Conceptual Model

OWL Files

ePO BDTI - Application Profile

Conceptual Model

OWL Files


Conceptual Model (CM)


Working documents

see more

Use Cases

see more


see more

Glossary

Development

Online documentation

Information requirements

Conceptual Model (CM)

OWL

Proof of Concept


see more

Information requirements

Conceptual model

Mapping of the conceptual data entities to OWL

Clone this wiki locally