Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives

xmlschema-dev



Need to combine duplicate tags in the file - 4/4/2007 9:43:00 AM
Re: Permit (greedy) conflicting wildcards - 4/4/2007 12:05:00 PM
Re: redefine and interoperability problems - 4/4/2007 2:39:00 PM
RE: redefine and interoperability problems - 4/5/2007 10:41:00 AM
RE: redefine and interoperability problems - 4/13/2007 5:59:00 AM
RE: redefine and interoperability problems - 4/13/2007 10:01:00 AM
RE: redefine and interoperability problems - 4/17/2007 5:35:00 PM
Re: redefine and interoperability problems - 4/18/2007 7:29:00 PM
Re: redefine and interoperability problems - 4/18/2007 5:36:00 AM
Re: redefine and interoperability problems - 4/18/2007 8:37:00 PM
schema extension question - 4/19/2007 12:18:00 PM
RE: schema extension question - 4/20/2007 4:54:00 AM
multiple namespaces - 4/23/2007 3:49:00 PM
Re: multiple namespaces - 4/23/2007 6:36:00 AM
Re: multiple namespaces - 4/23/2007 5:06:00 PM
RE: multiple namespaces - 4/23/2007 5:41:00 PM
Re: multiple namespaces - 4/23/2007 6:10:00 PM
RE: multiple namespaces - 4/23/2007 6:31:00 PM
Re: Permit (greedy) conflicting wildcards - 4/24/2007 1:13:00 PM
Editorial suggestions for XSD 1.1 - 4/24/2007 1:42:00 PM
RE: multiple namespaces - 4/23/2007 4:21:00 PM
RE: redefine and interoperability problems - 4/5/2007 1:23:00 AM
Re: redefine and interoperability problems - 4/5/2007 12:44:00 PM
extending schema - 4/10/2007 1:38:00 AM
Re: extending schema - 4/15/2007 7:57:00 PM
Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/15/2007 5:57:00 PM
How to take union of elements inside two different complex types? - 4/15/2007 8:05:00 PM
Difference between xs:simpleType & xs:complexType - 4/15/2007 8:44:00 PM
RE: Difference between xs:simpleType & xs:complexType - 4/16/2007 2:42:00 PM
RE: Difference between xs:simpleType & xs:complexType - 4/16/2007 12:22:00 AM
RE: Difference between xs:simpleType & xs:complexType - 4/16/2007 3:55:00 AM
Re: Difference between xs:simpleType & xs:complexType - 4/16/2007 5:03:00 PM
Re: Difference between xs:simpleType & xs:complexType - 4/16/2007 3:53:00 PM
Re: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/16/2007 11:02:00 AM
RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/16/2007 7:16:00 PM
RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/17/2007 1:11:00 PM
RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/16/2007 11:59:00 PM
RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/17/2007 12:49:00 AM
RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? - 4/16/2007 6:59:00 PM
Re: extending schema - 4/16/2007 10:08:00 PM
xs:redefine and interoperability problems - 4/5/2007 2:28:00 AM
RE: Permit (greedy) conflicting wildcards - 4/9/2007 1:18:00 PM
RE: Permit (greedy) conflicting wildcards - 4/10/2007 11:27:00 AM
RE: Permit (greedy) conflicting wildcards - 4/10/2007 10:58:00 AM
RE: Permit (greedy) conflicting wildcards - 4/10/2007 11:51:00 AM
Re: Permit (greedy) conflicting wildcards - 4/10/2007 12:21: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