Service naming criteria

From GEANT2-JRA1 Wiki

On the Cambridge meeting last January, we agreed on the following naming criteria:

  • Should be uniquely identifable
  • Must include unique project name
  • Could include category e.g. rrdma or ls

Use the following naming scheme for projects:

  • $name = $string1_$string2
  • $release_name= $name_$version

Where $string1 has to be Organisation specific name (has to be unique across all organisations) $string2 has to be Project/Software specific name (example: -JAVA-RRD-MA, HADES-MA, BWCTL-MP, etc) $version (we are talking about 'per service' version here) has to be managed by the team doing the development and the release of the service/software.

Underscore required between project name and the latter part Version number could be added to tar file or release tag Examples of names:

  • GEANT2_JAVA-RRD-MA
  • GEANT2_PERL-HADES-MA

Exampes of releases

  • GEANT2_JAVA-RRDMA_1.0
  • GEANT2_PERL-HADES-MA_0.2

This is taken from the minutes of the ISS session: http://wiki.perfsonar.net/jra1-wiki/index.php/ISS-Session-10-Jan-07

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/Service_naming_criteria"
Personal tools