Hi, I think it may be interesting to know the implementation but I am struggling to see why it is a MUST and also how we would aim for the MUST NOT Clash. If it is used I agree a project should themselves ensure that no clashes occur but only the infrastructure/project using the standard can define their resource types and ensure this. can someone help clear this up for me - I may have missed some of the background discussion? cheers johnk On 06/15/2012 10:03 AM, Andrea Cristofori wrote:
Dear all,
In reference to the discussion during our last phone meeting I found that GLUE seems not to inforce any standar name. But I also found a rather document (from 2009. You can find it attached to this email) that describe the name usage in WLCG. In particular, concerning the storage:
* ImplementationName MUST be published. The format is defined by the implementations, but the names MUST NOT clash. In particular, for WLCG storage services the names to be used are: CASTOR, DPM, StoRM, dCache, BeStMan, xrootd.
* ImplementationVersion MUST be published. The format is defined by the implementations.
For OS names there are others directives here (I don not think we need it but while I was looking around for info I found it):
https://wiki.egi.eu/wiki/Operations/HOWTO05
For site names:
https://wiki.egi.eu/wiki/Operations/HOWTO05
Furthermore my understanding is that, at least in EMI, the decision is just to set the EMI release version. Based on that it should be then possible to identify the version of the specific middleware.
Cheers, Andrea
-- ur-wg mailing list ur-wg@ogf.org https://www.ogf.org/mailman/listinfo/ur-wg
-- +------------------------------------------------------------+ |Dr. John Alan Kennedy Rechenzentrum Garching (RZG) | |Mail: jkennedy@rzg.mpg.de Boltzmannstrasse 2 | |Phone: +49 89 3299 2694 85748 Garching | |Fax: +49 89 3299 1301 | +------------------------------------------------------------+