Altova Mailing List Archives

xml-dev



[xml-dev] Adding metadata to a flat structure to create a hierarchy - 3/11/2014 9:32:00 AM
Re: [xml-dev] Adding metadata to a flat structure to create a - 3/11/2014 11:47:00 AM
[xml-dev] Re: Is programming sexier than data design? - 3/11/2014 3:35:00 PM
[xml-dev] Why isn't the semicolon a reserved character? - 3/15/2014 9:42:00 PM
Re: [xml-dev] Why isn't the semicolon a reserved character? - 3/16/2014 5:10:00 AM
Re: [xml-dev] Why isn't the semicolon a reserved character? - 3/15/2014 11:34:00 PM
=?utf-8?q?=5Bxml-dev=5D_Trial_cards_for_the_course_=28Was=3A_Re?= - 3/18/2014 4:16:00 AM
[xml-dev] [ANN] Balisage 2014 Submissions due in one month - 3/18/2014 6:58:00 PM
Re: [xml-dev] [ANN] Balisage 2014 Submissions due in one month - 3/18/2014 9:20:00 PM
[xml-dev] A seemingly odd question: What is XML? - 3/20/2014 9:33:00 AM
Re: [xml-dev] A seemingly odd question: What is XML? - 3/20/2014 10:31:00 AM
Re: [xml-dev] A seemingly odd question: What is XML? - 3/20/2014 2:06:00 PM
Re: [xml-dev] A seemingly odd question: What is XML? - 3/20/2014 2:44:00 PM
[xml-dev] Re: A seemingly odd question: What is XML? - 3/20/2014 1:12:00 PM
Re: [xml-dev] Re: A seemingly odd question: What is XML? - 3/20/2014 2:35:00 PM
Re: [xml-dev] Re: A seemingly odd question: What is XML? - 3/20/2014 4:13:00 PM
Re: [xml-dev] Re: A seemingly odd question: What is XML? - 3/20/2014 4:59:00 PM
[xml-dev] RFC for XML Object Parsing - 3/23/2014 5:41:00 AM
AW: [xml-dev] RFC for XML Object Parsing - 3/23/2014 12:07:00 PM
[xml-dev] Terminology (was: RFC for XML Object Parsing) - 3/23/2014 6:13:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/23/2014 11:31:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/23/2014 11:51:00 PM
RE: AW: [xml-dev] RFC for XML Object Parsing - 3/23/2014 11:18:00 PM
[xml-dev] XML For The Average Monkey - 3/24/2014 2:39:00 AM
Re: [xml-dev] XML For The Average Monkey - 3/24/2014 3:21:00 AM
Re: [xml-dev] XML For The Average Monkey - 3/25/2014 4:25:00 PM
RE: [xml-dev] XML For The Average Monkey - 3/24/2014 4:05:00 AM
RE: [xml-dev] XML For The Average Monkey - 3/24/2014 11:07:00 PM
[xml-dev] "oid" - the Object ID in XML - 3/24/2014 5:25:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 7:26:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 7:31:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/24/2014 8:16:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/24/2014 9:21:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 10:49:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/24/2014 8:02:00 PM
Re: [xml-dev] RFC for XML Object Parsing - 3/25/2014 8:59:00 AM
FW: [xml-dev] RFC for XML Object Parsing - 3/24/2014 8:04:00 PM
Re: FW: [xml-dev] RFC for XML Object Parsing - 3/24/2014 8:24:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 8:28:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 9:20:00 PM
RE: [xml-dev] RFC for XML Object Parsing - 3/24/2014 11:43:00 PM
RE: [xml-dev] XML For The Average Monkey - 3/25/2014 12:24:00 AM
RE: [xml-dev] XML For The Average Monkey - 3/25/2014 2:42:00 PM
RE: [xml-dev] XML For The Average Monkey - 3/25/2014 3:50:00 PM

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.