[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: file format
At 23 Jun 2000 21:46 -0300, G. Ken Holman wrote: ... > but before we get into file formats we still haven't yet discussed > the data flows that are up for discussion. I think we need agreement on > the approach before we spend time deciding what each of the files looks like. 1. Our deliverables don't include an "XSLT Process" (unless, like David, we're working on an XSLT processor). The diagram should show the XSLT stylesheet that are also inputs to the XSLT processor/process. 2. Similarly, the "package content" should include the XSLT stylesheets that turn the inputs into the outputs. 3. You could put the "XSLT Processes" box on the "Users" side of the thick dotted line since, I believe, it the users who will be creating the "Configuration X" files. 4. You could use vertical ellipses to indicate that there are more submissions than "Submission A" and "Submission n". 5. Why is "Submission n" in italics when "Configuration X" has only the "X" in italics? Regards, Tony Graham ====================================================================== Tony Graham mailto:tgraham@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9632 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC