We should only have *one* way of specifying these, not both ```requireType``` property and the ```requireType:id:value``` thing below. Having just one way makes the code cleaner, and reduces confusion for the content creators.
I think the ```requireType:id:value``` way looks better now, compared to the abbreviations earlier, but this ```requireType``` property-method is more explicit. I like being explicit in the resources :)

Don't worry about backwards-compatibility, we can do some clever scripting later on existing resources, once we decide a good way to represent the data.