3 spaces as a tab-stop for XML blobs?

[hellt]

Hi @pdellaert
I spotted an interesting thing. When you create some object which accepts XML Blobs (for instance VNF Metadata) you receive the blob back with 3 spaces used as a tab stop:

In CATS, after creation of any object we perform double-check operation which compares params pushed to VSD and ones we received back. This check failed for XML blob because of 4spaces vs 3 spaces
While comparing blobs might not be a good idea, still 3 spaces used as a tab stop seems a bit questionable =)