Hi Stephen, On Friday 27 March 2009 12:30:15 Burke, S (Stephen) wrote:
Paul Millar [mailto:paul.millar@desy.de] said:
How about "finding out which CE job managers are in use at UK sites".
I think that would be an abuse of the attribute; people should use the AdminDomain structure for that kind of thing.
But the Location object is tied to the AdminDomain (amongst other classes), so I don't see this as an abuse: the Location objects describe where things are. If one wishes to group objects by country then (to me) it seems natural that Location objects be used and Location.country attribute be processed. Moreover, I don't see how else one can answer the question without making potentially fragile assumptions. For example, one cannot assume that a country forms a single AdminDomain, or that the some other attribute (with a DNS component) ends with the country-specific TLD. So, I'm curious how one answers the above question with GLUE 2.0 without processing the published Location.country attributes.
Anyway I don't think we should change the schema any more, we've discussed this for two years and anything non-critical should wait for glue 2.1 ...
The issue is when will GLUE 2.1 come out? If we go for a time-based release process (say every six months, if a new release is meritted) then I'm perfectly happy to delay this for GLUE v2.1. Cheers, Paul.