Potential Issue: critdates requires created

I just noticed, in the context of implementing a client-specific
specialization, that critdates requires <created> before you can have any
number of <revised>.

I can understand requiring that <created> occurs at most once and before any
<revised> but it seems unnecessarily constraining to require <created> in
all cases.

In particular, you might not care when something was created (or necessarily
even know when it was created) but care about when it was revised (for
example, because you're revising it but didn't create it).

It is a fully backward-compatible change to made <created> option rather
than required in <critdates>.

Does anyone else agree that requiring <created> is imposing an unnecessary
and inappropriate policy?

Cheers,

Eliot

----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email:   <mailto:>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>