Altova Mailing List Archives

xml-dev



[xml-dev] MXV - Model-driven XML Vocabulary design using OASIS UBL - 12/1/2009 8:32:00 PM
[xml-dev] Draft PER of Associating Style Sheets with XML documents - 12/4/2009 5:20:00 PM
[xml-dev] Schema-Free Query Vs. Structure Transformation - 12/4/2009 6:38:00 PM
[xml-dev] [ANN] Release of XMLmind XSL-FO Converter v4.3.2 - 12/7/2009 8:17:00 AM
[xml-dev] Write Programs That Don't *Do* Anything ... Express - 12/10/2009 12:51:00 PM
Re: [xml-dev] Write Programs That Don't *Do* Anything ... Express - 12/10/2009 1:03:00 PM
Re: [xml-dev] Write Programs That Don't *Do* Anything ... Express - 12/10/2009 3:09:00 PM
Re: [xml-dev] Help with Xquery - 12/11/2009 1:58:00 AM
[xml-dev] New release of CAMeditor v1.7 now available - with NIEM 2.1 - 12/12/2009 4:10:00 AM
[xml-dev] "The QName URN Namespace" (draft-rsalz-qname-urn-01) - 12/15/2009 12:40:00 PM
Re: [xml-dev] "The QName URN Namespace" (draft-rsalz-qname-urn-01) - 12/15/2009 1:01:00 PM
RE: [xml-dev] "The QName URN Namespace" (draft-rsalz-qname-urn-01) - 12/15/2009 1:20:00 PM
[xml-dev] New XQuery / XPath Working Drafts - 12/15/2009 8:57:00 PM
[xml-dev] [ANN] XML Prague 2010 Final Call for Participation (CFP) - 12/16/2009 8:07:00 AM
[xml-dev] [Announce] PsychoPath XPath 2.0 Schema Aware Processor - 12/16/2009 3:24:00 PM
[xml-dev] [ann] oXygen XML Editor version 11.1 - 12/17/2009 7:16:00 PM
[xml-dev] [ANN] XML Prague 2010 Final Call for Participation (CFP) - 12/21/2009 10:51:00 AM
[xml-dev] Best Practice: Element with data or element with child - 12/21/2009 2:54:00 PM
Re: [xml-dev] Best Practice: Element with data or element with child - 12/21/2009 3:18:00 PM
[xml-dev] Where does the term "element" come from? - 12/24/2009 12:29:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 12:45:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 3:27:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 3:46:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 3:59:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 4:26:00 PM
Re: [xml-dev] Where does the term "element" come from? - 12/24/2009 1:49:00 PM
[xml-dev] Open source XQuery CMS - 12/25/2009 3:25:00 PM
Re: [xml-dev] Open source XQuery CMS - 12/25/2009 4:07:00 PM
Re: [xml-dev] Open source XQuery CMS - 12/26/2009 1:13:00 AM
[xml-dev] Namespace prefixes are a security risk - 12/28/2009 4:16:00 PM
Re: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 4:34:00 PM
Re: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 5:12:00 PM
RE: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 5:40:00 PM
Re: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 5:59:00 PM
Re: [xml-dev] Namespace prefixes are a security risk - 12/29/2009 1:29:00 AM
Re: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 4:28:00 PM
Re: [xml-dev] Namespace prefixes are a security risk - 12/28/2009 4:54:00 PM
[xml-dev] Marketplace XML Vocabularies - 12/31/2009 1:27:00 PM
Re: [xml-dev] Marketplace XML Vocabularies - 12/31/2009 2:59:00 PM
RE: [xml-dev] Marketplace XML Vocabularies - 12/31/2009 7:43:00 PM
RE: [xml-dev] Marketplace XML Vocabularies - 12/31/2009 7:54:00 PM
RE: [xml-dev] Marketplace XML Vocabularies - 12/31/2009 9:31: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.