Hi lucb1e, thanks for finding this issues. It actually gets validated correctly by our parser (which will soon be open source) but hits a bug in our API. We are working on a fix right now.