I get your point, Chris, but doesn't that sort of beg the normal definition of what constitutes a header ? ;^)
Mike At 05:50 PM 1/27/2005 +0000, Chris Johnson wrote: >Quoted text is from ><[EMAIL PROTECTED]>, by Mike >Rawlins <[EMAIL PROTECTED]> > > >semantic clarity or processing efficiency to be gained by putting the > >detail as a child of the header. FYI - X12.59, which specifies the > >several aspects of the semantics of X12 EDI transaction sets, has the > >detail as a child of the header. I conceptually understand the > >rationale, but must confess I find little practical application. > >So long as there is only one header per document it makes no difference. >If there were multiple header/detail sets per document then you would >want to use the hierarchy to associate detail with the relevant header. > --------------------------------------------------------------- Michael C. Rawlins, Rawlins EC Consulting www.rawlinsecconsulting.com Using XML with Legacy Business Applications (Addison-Wesley, 2003) www.awprofessional.com/titles/0321154940 . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
