A soundxyz doesn't implement a valid uri as audio_url and we still include it in our data set

https://metadata.sound.xyz/v1/0xaa0647818717230b74aea9ba711566132f224847/1361129467683753853853498429727072845825

see audio_url

{"name":" Before I Go  #1","artist_name":"Sophia Alexa","description":"Hi guys :) I’m sophia alexa, I’m an artist and songwriter born in california and raised in amsterdam, now living in london. i’ve had a love of songwriting since the day my obsession with Joni Mitchell started. i wrote 'before i go' about wanting to see and do everything essentially before i go. it came from the idea of being stuck in a longterm relationship that wasn't working out, and how it would feel to waste all that time. i hope you enjoy it! ","external_url":"https://www.sound.xyz/sophiaalexa/before-i-go","image":"missing","audio_url":"missing","animation_url":"missing","comment_wall_url":"missing","attributes":[{"trait_type":" Before I Go ","value":"Song Edition"}]}

first: We may include this in the final data set: but it'd also not be legitimate according to the formatting rules of our JSON schema: https://github.com/neume-network/schema/blob/39a4bdb680062599bcd741679515093870798e5d/src/schema.mjs#L294
But I think we may need to address this already earlier and hence here would be a good problem to introduce what @sirnicolaz had proposed, namely mandating a JSON schema structure for all data sources, see issue below:
231

neume-network / strategies

A soundxyz doesn't implement a valid uri as audio_url and we still include it in our data set #273

231