8 Oct
2015
8 Oct
'15
8:21 p.m.
So, yes, I can see the case for an attribute @format with closed valuelist of "XML", "Other" ... but beyond that I think we're straying too far out of our zone of expertise. How do I know whether "wibble" means "Wibble 1.0" or "Wibble with the doohickey extensions?"
The possibility to state in an attribute what format of metadata is in inside <xenoData> is something I was advocating in since our first mail exchange in July. I agree you cannot go far with this, but maybe distinguishing between Wibble 1 and Wibble 2 could still be possible adopting controlled vocabulary in the ODD at project level (we could also imagine to maintain a registry of endorsed metadata formats but I see this could bring about a lot of problems). f