|Hosting Institute||Data Center||Naming Authority ivoid|
|Observatoire de Paris-Meudon (OBSPM)||Paris Astronomical Data Center (PADC)||ivo://vopdc.obspm|
|National Aeronautics and Space Administration (NASA)||High Energy Astrophysics Science Archive Research Center (HEASARC)||ivo://nasa.heasarc|
|Instituto Nazionale di Astrofisica (INAF)||Italian Center for Astronomical Archive (IA2)||ivo://ia2.inaf|
|(several)||Centre de Données de la Physique des Plasmas (CDPP)||ivo://cdpp|
This naming authority ivo-id will appear on all data service provided in the VO. This construction will also simplify the search of resource coming from a specific institution or project, so take some time to construct it.
The construction of an ivo-id rely upon the naming authority it depends on. We suggest here a construction rule that is aiming at facilitating the addition of new data services, as well as facilitating there discovery. We propose to follow a hierarchical (path-like) structure, starting from the naming authority, and cascading down to the service itself. For instance, if you want to declare an EPN-TAP service sharing data from a database called "my_database" in a "my_group" team from a "my_lab" laboratory, you would have: