This may be a use case:
In 360 DEI, we have one schema block repeated 3 times. So it's a ref because that's sensible. But in this block there is a codelist.
Do we want to be able to produce a file with the codelist options included as a ENUM, but with the block still in one definition and with ref's to it? Such a file would be more human readable
Currently we can only produce a file with the same schema repeated 3 times which isn't very clear to humans
This may be a use case:
In 360 DEI, we have one schema block repeated 3 times. So it's a ref because that's sensible. But in this block there is a codelist.
Do we want to be able to produce a file with the codelist options included as a ENUM, but with the block still in one definition and with ref's to it? Such a file would be more human readable
Currently we can only produce a file with the same schema repeated 3 times which isn't very clear to humans