Re: [CF-metadata] Invalid alias IDs in CF Standard Name Table v47

2017-11-21 Thread Lowry, Roy K.
Dear Murray, The whole point of these two aliases was to correct the accidental omission of an underscore. I appreciate the issues that this causes for rigorous XML parsing. For a number of reasons, including support of data delivery systems based on Linked Data, we have set up an alternativ

Re: [CF-metadata] Invalid alias IDs in CF Standard Name Table v47

2017-11-21 Thread Lowry, Roy K.
Dear Murray, The duplicate you mention is a case where the original Standard Name was unfit for purpose due to the direction of the flux being implicit (assumed downwards) rather than explicit. We tackled this in our serving by using narrowMatch as the mapping predicate to both possibilities,