OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [no subject]

work of the TC.  Frankly, I'd prefer not to force any of the TC's to ma=
this sort of a transition since it will only detract from time spent on=

real technical work in exchange for no valuable benefits from what I ca=

It probably does indeed make sense is to put a standard set of tools in=

place for TC's to use, but mandating that they MUST use them does not s=
like a good expenditure of member resources.

As for change control, I'd vote for CVS as it is simple to use and is
agnostic to the data it holds.  This would definitely be a big value ad=
for OASIS IMO.   Coupling this with version control, author/editor cont=
etc. gets my vote too.

Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
Co-Chair, OASIS UDDI Specification TC
STSM - Emerging Technologies
IBM Corporation

"Karl F. Best" <karl.best@oasis-open.org> on 02/18/2004 04:51:30 PM

Please respond to karl.best@oasis-open.org

To:    Chairs OASIS <chairs@lists.oasis-open.org>
cc:    "lomas >> Jeff Lomas" <Jeff.Lomas@oasis-open.org>
Subject:    Re: [chairs] need your comments on DocMgmt system requireme=

Excellent comments, everyone. Keep 'em coming.

I see a consensus that we want a sandbox as a phase prior to checkin an=
version control, and a suggestion to use wiki for the sandbox. We will
need to have access control too, to restrict this to the TC members.

I see a lot of pros-n-cons for using MSWord together with CVS in the
second phase, especially as it relates to change control. We're not
committed to CVS yet; that's just a popular suggestion. How would you
feel about a requirement to do all of your documents in HTML or XML?
i.e. no proprietary or binary formats. (Now there's a big can of worms
to open :-) I'm not making any threats; just wondering if that might be=

a good way to go. Perhaps this would require OASIS providing tools for
the TCs to use; we'd have to ask some vendors for contributions.

If we did use some text-based format (as above), would CVS provide us
with change logs?



Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<p>Hi Karl,<br>
Perhaps I've mised some key part of this thread, but I think that manda=
ting a source document format will cause a lot of unnecessary work for =
a lot of people.   Certainly from a requirements perspective, I'd have =
to register that our TC requires the ability to do multi-editor change =
control, the ability to manage a large document (between 400-500 pages)=
, support for complex document forms, figures, multiple editors, etc.  =

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]