Re: 3 Common Patterns in XML Processing
One comment on lists: Often it is not known whether an element can be a list. There might be a schema associated with it which describes it having multiple occurrences but sometimes this is either not known to the writer of the code which handles that element or it is overlooked. e.g. if <book> had the possibility of multiple <title> elements. It might be very rare that there is ever a book/title so the usual XPath used in code might be book/title. This means that there will be rare occasions when book/title returns a set of nodes rather than a single node. It is a pain to always remember to write book/title just in case a list is involved and without a schema who would know to do that anyway unless they do it for every XPath and cater for it in every bit of code. ---- Stephen D Green
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format