[no subject]

<p><font size=3D"2" color=3D"#800080">Please respond to karl.best@oasis=
-open.org </font>
<p><font size=3D"2" color=3D"#800080">To:	</font><font size=3D"2">Chair=
s OASIS &lt;chairs@lists.oasis-open.org&gt;</font><br>
<font size=3D"2" color=3D"#800080">cc:	</font><font size=3D"2">&quot;lo=
mas &gt;&gt; Jeff Lomas&quot; &lt;Jeff.Lomas@oasis-open.org&gt;</font><=
font size=3D"2" color=3D"#800080"> </font><br>
<font size=3D"2" color=3D"#800080">Subject:	</font><font size=3D"2">Re:=
 [chairs] need your comments on DocMgmt system requirements</font><br>
<br>
<br>
<br>
<tt>Excellent comments, everyone. Keep 'em coming.<br>
</tt><br>
<tt>I see a consensus that we want a sandbox as a phase prior to checki=
n and<br>
version control, and a suggestion to use wiki for the sandbox. We will<=
br>
need to have access control too, to restrict this to the TC members.<br=
>
</tt><br>
<tt>I see a lot of pros-n-cons for using MSWord together with CVS in th=
e<br>
second phase, especially as it relates to change control. We're not<br>=

committed to CVS yet; that's just a popular suggestion. How would you<b=
r>
feel about a requirement to do all of your documents in HTML or XML?<br=
>
i.e. no proprietary or binary formats. (Now there's a big can of worms<=
br>
to open :-) I'm not making any threats; just wondering if that might be=
<br>
a good way to go. Perhaps this would require OASIS providing tools for<=
br>
the TCs to use; we'd have to ask some vendors for contributions.<br>
</tt><br>
<tt>If we did use some text-based format (as above), would CVS provide =
us<br>
with change logs?<br>
</tt><br>
<tt>-Karl<br>
</tt><br>
<br>
</body></html>=

--0__=09BBE4ACDFC4C37F8f9e8a93df938690918c09BBE4ACDFC4C37F--