Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives

xml-dev



Re: [xml-dev] Rules of Thumb for Creating XML Vocabularies for - 2/1/2009 12:54:00 PM
[xml-dev] RE: Rules of Thumb for Creating XML Vocabularies for - 2/1/2009 6:35:00 PM
[xml-dev] Re: Rules of Thumb for Creating XML Vocabularies for - 2/1/2009 11:59:00 PM
RE: [xml-dev] RE: Keep business-process-specific data separate? - 2/2/2009 11:06:00 AM
[xml-dev] Schematron XQuery binding - 2/2/2009 11:33:00 AM
[xml-dev] The beauty and power of declarative syntaxes and - 2/2/2009 1:27:00 PM
RE: [xml-dev] RE: Keep business-process-specific data separate? - 2/2/2009 3:55:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 2/2/2009 5:14:00 PM
[xml-dev] XSTL stylesheet workarounds for exceptions - 2/2/2009 9:04:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 2/2/2009 9:42:00 PM
RE: RE: [xml-dev] Re: Rules of Thumb for Creating XML Vocabularies - 2/3/2009 8:42:00 AM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/3/2009 1:14:00 PM
[xml-dev] SAX - 2/3/2009 1:51:00 PM
[xml-dev] SAX - not well formed data - 2/3/2009 2:03:00 PM
[xml-dev] any-to-any structure transformations article - 2/3/2009 7:06:00 PM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/4/2009 12:54:00 PM
[xml-dev] ANN: Altova MissionKit v2009 - 2/4/2009 4:06:00 PM
[xml-dev] [ANN] CodeSynthesis XSD/e 3.0.0 released - 2/5/2009 7:57:00 AM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/5/2009 12:30:00 PM
[xml-dev] [ANN] Xml Schema Lightener 2.0 utility: making schemas - 2/5/2009 3:10:00 PM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/5/2009 7:24:00 PM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/6/2009 3:03:00 AM
Re: [xml-dev] XSTL2.0 stylesheet workarounds for exceptions - 2/6/2009 1:47:00 PM
[xml-dev] XSTL stylesheet workarounds for exceptions - 2/9/2009 10:19:00 AM
[xml-dev] keyword search over XML streams - 2/9/2009 2:44:00 PM
[xml-dev] A bad idea to use the XML Schema list type? - 2/9/2009 3:11:00 PM
[xml-dev] XML representation of SQL queries? - 2/9/2009 4:05:00 PM
[xml-dev] XML representation of SQL queries? - 2/9/2009 11:59:00 PM
[xml-dev] DOM level 1 java parsers? - 2/10/2009 10:17:00 PM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/11/2009 10:08:00 PM
[xml-dev] Schema fragments form style sheets? - 2/12/2009 9:49:00 AM
ezmlm warning - 2/12/2009 1:24:00 PM
[xml-dev] 3 approaches to structure lists, plus an analysis of each - 2/14/2009 10:41:00 PM
[xml-dev] xmllint - 2/14/2009 11:12:00 PM
Re: [xml-dev] 3 approaches to structure lists, plus an analysis of - 2/14/2009 11:23:00 PM
RE: [xml-dev] 3 approaches to structure lists, plus an analysis of - 2/15/2009 2:22:00 PM
[xml-dev] [Announce] Expanded syllabus now includes XQuery in March - 2/16/2009 1:47:00 PM
[xml-dev] python and xacml - 2/16/2009 7:00:00 PM
[xml-dev] Email about the apartment - 2/16/2009 7:01:00 PM
[xml-dev] Should an XML vocabulary be a Swiss Army Knife or a - 2/16/2009 9:41:00 PM
Re: [xml-dev] XSTL stylesheet workarounds for exceptions - 2/17/2009 12:52:00 PM
[xml-dev] Using xsd:list and getting data from xml file - 2/18/2009 6:35:00 PM
[xml-dev] XML Conferences in 2009? - 2/18/2009 10:18:00 PM
[xml-dev] ANNOUNCE: MarkLogic User Conference 2009 - 2/18/2009 11:35:00 PM
[xml-dev] I have implemented SAX based XPath Engine - 2/19/2009 1:08:00 AM
RE: [xml-dev] 3 approaches to structure lists, plus an analysis of - 2/19/2009 1:34:00 AM
Re: [xml-dev] Using xsd:list and getting data from xml file - 2/19/2009 12:51:00 PM
Re: [xml-dev] RE: 4 approaches to structure lists, plus an analysis - 2/19/2009 3:54:00 PM
Re: [xml-dev] XML Conferences in 2009? - 2/19/2009 4:35:00 PM
RE: [xml-dev] XML Conferences in 2009? - 2/19/2009 4:41:00 PM
[xml-dev] [ANN] XML Prague 2009 March 21-22, only one month to go ... - 2/20/2009 8:57:00 AM
[xml-dev] Re: Hello,Kseniya here. - 2/20/2009 3:25:00 PM
[xml-dev] ANN: XProc Tutorial - 2/21/2009 1:40:00 PM
[xml-dev] Remove Nodes But Keep Children - 2/22/2009 12:40:00 AM
[xml-dev] Difference between "normalize" and "canonicalize"? - 2/25/2009 11:39:00 AM
Re: [xml-dev] Difference between "normalize" and "canonicalize"? - 2/25/2009 11:47:00 AM
RE: [xml-dev] Difference between "normalize" and "canonicalize"? - 2/25/2009 12:19:00 PM
[xml-dev] RE: Difference between "normalize" and "canonicalize"? - 2/26/2009 12:04:00 AM
Re: [xml-dev] RE: Difference between "normalize" and "canonicalize"? - 2/26/2009 6:21:00 PM
"vocabulary constraints" and other constraints (was: Re: [xml-dev] RE: Difference between "normalize" and "canonicalize"?) - 2/28/2009 2:36:00 AM
Re: [xml-dev] "vocabulary constraints" and other constraints (was:Re: [xml-dev] RE: Difference between "normalize" and "canonicalize"?) - 2/28/2009 2:53:00 AM
Re: [xml-dev] Difference between "normalize" and "canonicalize"? - 2/25/2009 1:18:00 PM
Re: [xml-dev] XML Conferences in 2009? - 2/25/2009 8:14:00 PM
Re: [xml-dev] RE: Difference between "normalize" and "canonicalize"? - 2/26/2009 12:31:00 AM
[xml-dev] Calls for Participation -- Balisage & Processing XML - 2/26/2009 2:22:00 AM
[xml-dev] Twitterers - 2/26/2009 1:19:00 PM
Re: [xml-dev] Twitterers - 2/26/2009 3:41:00 PM
[xml-dev] [ann] oXygen XML Editor 10.1 - new XML Schema diagram and - 2/26/2009 4:11:00 PM
[xml-dev] [Ann] SketchPath Tool - Now available as Word2007 Addin - 2/26/2009 10:14:00 PM


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent