[InC-Admin] bug in Incommon-metadata.xml

[Rod Widdowson]

> I am able to determine that the offending character is a non-breaking
> space (HEX A0). We will of course remove the character from InCommon
> metadata ASAP.

I'd bet that that meant that the JSON had a nbs in it and some browsers implementation barfed it assuming that this was a line break.  Good luck debugging this it will be browser specific....  Of course another option is that the SP serving it up has got confused about the encoding  (and is spitting out ISO-LATIN-1 as UTF or some such)
 
> Comments or suggestions are welcome.

Ian will chime in but I'm pretty sure that the UKFed has a rule..

R