RJLRef: ~/02f592/02f592genxmlStatus.021216 From BondJamesBond@geggis.com Mon Dec 16 21:45:05 2002 From: "Chris Geggis" To: "'Bob Lechner'" Subject: RE: gen2xml - You have an empty base/Master under gen2xml?r Date: Mon, 16 Dec 2002 21:44:52 -0500 Dr. Lechner, > 2. Please unprotect: saturn.cs.uml.edu(26)> lg /usr/proj3/case/gen/base/Master/CVSROOT/log.pl -rwx------ 1 cgeggis genxml 22 Oct 4 06:41 /usr/proj3/case/gen/base/Master/CVSROOT/log.pl This is all set. I guess this would've prevented you from checking anything out of CVS :-( > 3. Since UML can't print .vsd figures, please provide ALSO a .ps or .pdf version. I'm attaching 2 ps files. I've also updated CVS to include them. Visio doesn't have a pdf format. > 5. I don't know what your CVS status is - because you never checked out genxml to the gen/genxml tree. I saw genxml in the modules file. That's not enough. If you really did 'cvs add genxml' and 'cvs ci genxml' then your genxml tree shold have been checked in and could be checked out again. Each checked-in dir'y node of module genxml would have a CVS sub-diry with Entries ROot etc. files. I did a "cvs export -r finalSub genxml/(doc|lib|src|bin)" (where finalSub was the tag) to do any final and/or milestone releases. This prevents the CVS directories from showing up. Adding the subdirectory (doc|lib|src|bin) prevents any other files from being clobbered. Thanks, Chris Geggis chris@geggis.com -----Original Message----- From: Bob Lechner [mailto:lechner@cs.uml.edu] Sent: Monday, December 16, 2002 6:15 PM To: Chris Geggis Cc: Bob Lechner Subject: Re: gen2xml - You have an empty base/Master under gen2xml?r .... . . Note that cvs diff (like diff) is useless on .doc (like .o) binary files. CVS can usefully hold the latest or siginificant rev# versions of .doc files. laTex was better for CVS since .tex is line oriented text.` I recomend you test 'cvs co genxml' in a DIFFERENT place to avoid clobbering genxml as is. If it doesn't work you need to add module genxl to $CVSROOT. Good luck, Bob Lechner PS: I'll be at Poonsup's thesis review Tues 1-3PM and later. (it'll be very worthwhile to JavaXML programmers) 01f522 reviews will be Wed 5/6/7 PM. THurs I'l be at Dept mtg 1130-130, then free in PM. > From BondJamesBond@geggis.com Mon Dec 16 01:01:16 2002 > From: "Chris Geggis" > To: "'Bob Lechner'" > Subject: RE: final report on gen2xml? > Date: Mon, 16 Dec 2002 00:58:13 -0500 > > Dr. Lechner, > I sincerely apologize. I meant to mail you the revised > Engineering/Maintenance Spec and I mailed you the revised requirements > by mistake. I'm sure this was confusing and again I apologize. > I hope this email clears everything up. Please let me know if it doesn't. > > I'm not sure what you mean about the CVS repository though. Everything > is in there. > > CVSROOT=/usr/proj3/case/gen/base/Master > cvs co genxml > > Should give you everything. There is a datamodel.msdat in the dat > subdirectory which was used as a base test case. I also tried it on > arbitrary larger msdat files and everything seemed to work as expected. > > Thanks, > Chris Geggis > chris@geggis.com > > -----Original Message----- > From: Bob Lechner [mailto:lechner@cs.uml.edu] > Sent: Sunday, December 15, 2002 10:03 PM > To: cgeggis@saturn.cs.uml.edu > Cc: Bob Lechner > Subject: final report on gen2xml? > > Hi Chris - thank you for the new docs. > (requirements and .vsd only)??? I saw no new maintenance specs./ > > I don't see any CVS Repository - I presume there are no CVS files > but one subdiry (loginfo) has CVS files. What does this mean? > CVS diffs are np help on .doc files even if saved as (word-wrapped) > .txt - CVS and diff are line-oriented > (they'd work fine on pr_dumped *.dat files tho :-) > > The quotes below come from your revised[?] requirements.doc, > but I can't connect them to the final submission or to > $CASE/02s592/gen2xml/doc content. (All docs should identify > you and 02f592 and current date on page 1. E.g. User Guide) > > What I am missing is your project final report, connecting > all the docs (dots?/directories?) together. > I suspect your last email is the main new content of that report, > which should start by referring to the Requirements doc, > then maintenance spec, and end with testing status/results. > (BTWay, where is your test subdir'y?) > > Please tell me in some status section of the final report, > about the docs and tests in your requirements list, > and what is different about the actually delivered items and the > expected ones. I need traceability between documents so others > can follow your lead on this project starting with the final report. > > Thanks, > Bob Lechner > > "The documentation that will complement this project will be > this Design/Requirements document, an engineering specification, > and a user guide." > > ... > > "A set of test files will be created to convert between the two formats. > Some examples will be provided in the Engineering Specification. An > example of some of the tests that will be done is as follows: > Files that are converted from *.xml to *.msdat will be tested with > chgen. > Tests will ensure that the suite of tools works for XML 1.0 and > chgenv12." > > ------=_NextPart_000_000E_01C2A49E.37799C60 > Content-Type: application/msword; > name="eng_maint_spec.doc" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; >...