shall we name the new attribute "AdditionalPaths"?

so by default it will be used the attribute "Path" and the other paths can be published in "AdditionalPaths"

On 7 June 2018 at 12:01, Stephen Burke - UKRI STFC <stephen.burke@stfc.ac.uk> wrote:
glue-wg <glue-wg-bounces@ogf.org> On Behalf Of Paul Millar said:
> I have a slight preference for "Paths" over "OtherPaths", since
> OtherPaths suggests the value of Path is somehow canonical or preferred,
> which (I believe) isn't the intention.

It's preferred in the sense of being a default, use that path if you don't have a reason to do something else. That's how lcg-utils always worked, if you just specified a file name rather than a full path the code would write it to the default path. If there's only one default that's unambiguous, if you have several it's not clear what the semantics should be and anyway it's a change. Lcg-utils is now deprecated in favour of gfal and that doesn't use the information system, it just leaves it to the user, but that still gives the user the same question of how they construct a path if they don't have other knowledge.

Stephen




--
Dr. Alessandro Paolini
Operations Officer - EGI Foundation
Science Park 140
1098 XG Amsterdam
The Netherlands
skype: alessandro.paolini.egi
*********************************
"I believe in the power of laughter and tears"
    "as an antidote to hatred and terror"
          "A day without laughter"
             "is a wasted day" >>> Charlie Chaplin