There are other things we in business can do with said animal... Such as: 1. Buying a stronger whip. 2. Changing riders. 3. Say things like, "This is the way we have always ridden this horse." 4. Appointing a committee to study the horse. 5. Arranging to visit other sites to see how they ride dead horses. 6. Increasing the standards to ride dead horses. 7. Appointing a tiger team to revive the dead horse. 8. Creating a training session to increase our riding ability. 9. Comparing the state of dead horses in todays environment. 10. Change the requirements declaring that "This horse is not dead." 11. Hire contractors to ride the dead horse. 12. Harnessing several dead horses together for increased speed. 13. Declaring that "No horse is too dead to beat." 14. Providing additional funding to increase the horse's performance. 15. Do a Cost Analysis study to see if contractors can ride it cheaper. 16. Purchase a product to make dead horses run faster. 17. Declare the horse is "better, faster and cheaper" dead. 18. Form a quality circle to find uses for dead horses. 19. Revisit the performance requirements for horses. 20. Say this horse was procured with cost as an independent variable. 21. Promote the dead horse to a supervisory position.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 02, 2005 1:53 PM To: [EMAIL PROTECTED]; [email protected] Subject: RE: [EDI-L] The Ubiquity of XML - again. Mike: Thanks for phrasing the real issue so succinctly. Now, can we please bury this poor creature and move on? -Bob -----Original Message----- From: Mike Rawlins [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 02, 2005 4:47 PM To: EDI-L Mailing List Subject: Re: [EDI-L] The Ubiquity of XML - again. William, I think you're beating a dead horse. Very few people on this list need to be convinced of the value of XML. That isn't the issue. The issue is determining when XML's benefits to the major hubs justify the cost in moving from installed EDI systems which work very well, for the most part. I'm sure it will happen eventually. Cheers, Mike At 03:56 PM 2/2/2005 -0500, William J. Kammerer wrote: >See below. People actually do use XML for "incoming customer Purchase >Orders." This was seen on the xsl-list. I have no idea whether the >XML PO was based on an open standard like UBL, but that's not the >important point I wish to make. Everyone reading the note on xsl-list >is probably familiar with XML syntax and XSLT stylesheets - whether >they are mathematicians, teachers, agronomists, chemists, petroleum >engineers, programmers, web designers, or whatever. There's safety in >numbers. Wouldn't that be a hoot if a particle physicist helped this >guy out? That wouldn't be such a stretch to imagine. But how many >particle physicists know Gentran? > >William J. Kammerer >Novannet >Columbus, OH 43221-3859 . USA >+1 (614) 487-0320 > >----- Original Message ----- >From: "Varley, Roger" <[EMAIL PROTECTED]> >To: "Xsl-List (E-mail)" <[EMAIL PROTECTED]> >Sent: Wednesday, 02 February, 2005 12:11 PM >Subject: [xsl] Formatting Text Output > > >Hi > >I have a requirement that involves incoming customer Purchase Orders in >xml format and I need to extract the relevant data and output that >information in a text file. The item code, description and order >quantity need to appear in columns aligned with the colomn headings. >I've got it all working and I'm seperating the columns with ><xsl:text>	....	</xsl:text> to obtain the required spacing. > >The problem that I've got is that the product description is variable >length and therefore the number of 	 characters that need inserting >to line up the following colomns depends upon the length of the >description - and I can't find any sort of length() function. Any >suggestions how I go about this? > >Regards >Roger >--~------------------------------------------------------------------ >XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list <http://www.mulberrytech.com/xsl/xsl-list> >To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/ <http://lists.mulberrytech.com/xsl-list/> >or e-mail: <mailto:[EMAIL PROTECTED]> >--~-- > > > > >. >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 <http://groups.yahoo.com/group/EDI-L> > >Yahoo! Groups Links > > > > --------------------------------------------------------------- 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 <http://groups.yahoo.com/group/EDI-L> Yahoo! Groups Links . 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 <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/ <http://groups.yahoo.com/group/EDI-L/> * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed] . 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/
