XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Is CVS A Practical Means to Manage XML Versions In A Production Environment




BTW, one project that I used Subversion with a client was a 38784C
authoring and publishing environment.  I know you can relate |-)!

Betty


Thanks Betty, that I can.  

I'm amazed how many layers there are in 40051.  Daunting and needs dedicated
authoring I think.  The problem is not editing the XML.  That's easy.  Even
Notepadplusplus is fine if you know what you're doing, but for systems that
have to do a val/ver pass, I think a dedicated database works best.  ID
maintenance across the entity sets is a lot cleaner and easier to verify.
DoD has been squeezed between print and screen for so long, the structures
have evolved pretty well to support both if you know how to use that type
def.  Their problem is getting XSL-FOs documented well enough that the users
of the GFI know what to expect relative to auto-generated sets.
Multi-volume finally worked when I found the bug in the FO for
autogenerating WP nos and we could go forward on schedule.  The folks at
IMMC did a heckuva good job setting those up.  For a set that size, they
structured it well. 

But the FOs should be open source.   Let the contractors fix bugs without
making it a contract issue.  We all need them, so community expense.

len



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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS