Comment by omoikane

The person designing the database schema might have made a conscious decision not to support arbitrary track names and layout, since the added restrictions will make the client side software easier to implement.

But I guess it is also possible to design a schema that includes a lot of optional metadata, and clients only need to support up to certain core set of features if they choose.