I noticed a few deviations from the specification which should be easy to correct:

 1. The root of the JSON must be an object with only one key: ‘storageservice’. Its value must be an object where everything else is put.
 2. The ‘endpoints’ key must be renamed to ‘storageendpoints’.
 3. The ‘shares’ key must be renamed to ‘storageshares’.
 4. When multiple VOs have access to a share, their names must be distinct elements of an array, unlike one string in ‘INFO-FS’.

There is one thing to note that is not part of the specification but is necessary to allow clients to combine information from this file with other data
sources:

 5. The name of the shares must match the corresponding space tokens. For example, ‘ATLASDATA-FS’ must be renamed to ‘ATLASDATADISK’.