It seems to me quite clear that we should leave "@value" as meaning
"@isovalue" (we could even rename it),
and that projects should consider introducing their own attribiutes for
contained normalized dates
in other schemes. The killer, as Lou says, is the existence of the
related @notBefore, @notAfter, @from, and @to.
In theory one could declare up front "all my normalized dates are in
Klingon notation" , and leave
the datatype of @value as just character date. But this seems like madness.
rename to @value, @isoNotBefore, @isoNotAfter, @isoFrom @isoTo? and leave
projects to add their own comparable attributes?
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
OSS Watch: JISC Open Source Advisory Service