My first candidate for an annoying and pointless defaultVal is @part.
This has the defaultVal "n", which means:
(no) either the element is not fragmented, or no claim is made as to its
completeness. [Default]
If it means "No claim is made as to its completeness", then there's no
point whatsoever -- and actually the fact that this means _both_ "not
fragmented" _and_ "I'm not saying whether this is fragmented or not" is
just silly.
Unless anyone gives me a good reason within the next 24 hours, I'm going
to delete the defaultness and remove the latter part of the definition.
I don't believe anyone has ever explicitly applied this attribute with
the value "no" to mean the second part of its definition, so I don't see
that any difference could be made to anyone's existing projects.
Shout if you think I'm missing something.
Cheers,
Martin
