Warren Turkal wrote: > Subject: iso-codes: please split date_withdrawn data into subelements > Package: iso-codes > Version: 1.0a-1 > Severity: wishlist > > Please split the data_withdrawn info into multiple subelements. It would > be very valuable when using the data to load a database and using XSLT > to transform the file into SQL insert statements. With some of the > fields (like data_withdrawn) having internal structure, it somewhat > defeats the purpose of using a structured language like XML. I am > proposing something like the following fragment: > > Hi. Interesting. Can you post an example of how you would expect this to be used ? I had been expecting it to be used in, eg. code that iterated over a database - spotted a code in the DB that had been withdrawn - compared it to the date of withdrawal, and then did some action. e.g. in SQL. in this case, having a single date (in ISO-8601 format) would be easier to parse. Not having used XSLT much, I hadn't designed the schema to cope. Can you give an example?
Regards Alastair -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
