Altova Mailing List Archives>Archive Index >comp.text.xml Archive Home >Recent entries >Thread Prev - Re: XML naming conventions and good practice >Thread Next - Re: XML naming conventions and good practice Re: XML naming conventions and good practiceTo: NULL Date: 5/17/2009 9:08:00 PM Peter Flynn set the following eddies spiralling through the space-time continuum: > Prai Jei wrote: >> Which it was - sales information from a till. (Item sold, quantity, >> price, account number.) It was the target system that required it in XML. > > Ah. One of those. Nothing so simple as > > <transaction id="abc123"> > <item code="xyz789" quantity="3" price="29.99" account="1234567890"/> > </transaction> That sort of thing but there are a few more fields requested. The verbosity of the output format is significant if the data has to be transmitted across a s---l---o---w wide area network connection. Ties up the till too long, customers leave the checkout queue and walk out. We get round that by having the sales information written first to a PC on the local network (fast) which then relays it to the target system in its own time. >>> <div0 type="law tract"> >>> <div1 type="primary text"> >>> <p><lb n="4"><term id="g1">Is mesiuch cach fear fine cunai a >>> fintiud</term> <term id="g2">naide rean</term> <term id="g3">naide >>> [ & mucel mo vpon þis wyse ] > > It's from a mediaeval legal document written in Old Irish, with glosses > on the meaning of almost every phrase. Not easy to represent in any > system, especially when it's important because some of the laws might > still be in force. I wondered what language it was, it certainly looked Gaelic but the absence of accents (acute or grave) on any vowels made it impossible to be certain. -- ξ:) Proud to be curly Interchange the alphabetic letter groups to reply | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
