Tag values

authors : Tony CHEMIT
contact : chemit@codelutin.com


You can add some tag values on each element of an model.

This can be done in two ways:

  • inside the zargo model
  • in the optinal model properties file related to your model


There is two main scopes for a tag value:

  • on the the model, the tag value can be used for any element of your model (if the tag value accept it)
  • on a specific element of the model (classifier, class, interface, enumeration, attribute, paramter, operation, ...) to restrict the usage of the tag value.

Note that a tag value can be override (for example put in on the global model, and for a specific class override it, and so even on a attribute, ...).


We describe here the format of a tag value when written in the model properties file.

  • On a model
  • On a specific element of the model


Tag values availables from modules can be validated to make their experience safer and nearly compile safe.

Each module which offers some tagValues can describe a report of them which describe.

Have a look for example to the report for the EUGene core api or java templates.

How to write tag values

This section describe how to write safe tag values using the EUGene tag values API.

You need to define a provider of tag values in a new class:

System Message: WARNING/2 (line 70)

Literal block expected; none found.

See JavaDocs API or API Sources for more details.

Once this is done, use the EUGene tag-values-report to expose them in your site:



          <!-- To make your stereotypes and tag values available in the report plugin -->