RE: Complexity and Core Considerations

> 1) Is the current form of the specification too complex?  Yes/No/Maybe.
> Why?

No.  Complexity is in the eye of the beholder -- this specification seems as
complex as needed to specify the included functionality.  This specification
is actually smaller than the *user's* manual for most CM systems.

> 2) Does there remain sufficient discussion going on surrounding
> the OPTIONS that the draft should be split into two documents, CORE and
> OPTIONS, so that we can move CORE forward?  Yes/No/Maybe.  Why?

I'm in favor of splitting the document, since I think that will make it
crystal clear exactly what constitutes core versioning.  Thus, I'm in favor
of splitting, even if all the parts are submitted at once.  Document
splitting doesn't imply lack of adoption -- we've seen messages on this list
in the past few days from major vendors indicating they will implement broad
swathes of the specification.

- Jim

Received on Saturday, 3 February 2001 14:01:37 UTC