Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives

xml-dev



[xml-dev] JDOM XSLT TransformerConfigurationException - 1/2/2009 1:54:00 PM
Re: [xml-dev] JDOM XSLT TransformerConfigurationException - 1/4/2009 10:58:00 AM
Re: [xml-dev] JDOM XSLT TransformerConfigurationException - 1/5/2009 2:38:00 AM
[xml-dev] Announce: XML Prague 2009 Last Call for Papers - 1/6/2009 1:02:00 AM
Re: [xml-dev] Here's why it's not always a good idea to embed - 1/6/2009 1:10:00 PM
Re: [xml-dev] JDOM XSLT TransformerException (newbie) - 1/6/2009 1:25:00 PM
[xml-dev] [Announce] XQilla 2.2.0 released - 1/6/2009 3:17:00 PM
Re: [xml-dev] Here's why it's not always a good idea to embed - 1/6/2009 3:29:00 PM
RE: [xml-dev] Here's why it's not always a good idea to embedvalidation information (e.g., schemaLocation) in instance documents - 1/6/2009 4:23:00 PM
RE: [xml-dev] Here's why it's not always a good idea to embedvalidation information (e.g., schemaLocation) in instance documents - 1/6/2009 4:37:00 PM
Re: Metalink XML Download Description Format (draft-bryan-metalink-01) - 1/7/2009 2:27:00 AM
XML Technologies You Need For XML Workflow-Based Applications - 1/7/2009 2:22:00 PM
Validating Compound Documents using NVDL - 1/8/2009 8:03:00 PM
XML Schema Incompatibilities with Data Binding Tools - 1/9/2009 7:52:00 PM
What makes a data component good for standardizing? - 1/10/2009 2:34:00 PM
Announce: XML Prague 2009 CFP extended until Jan 16 - 1/12/2009 10:41:00 PM
XSLT Stylesheet query (newbie) - 1/12/2009 10:53:00 PM
A good XML editor for documents? - 1/14/2009 12:37:00 PM
Widget versioning - the widget, the spec, the platform api - 1/15/2009 10:53:00 AM
RE: [xml-dev] What makes a data component good for standardizing? - 1/15/2009 12:52:00 PM
Serialization with SAX - 1/15/2009 9:30:00 PM
Meaning of "Design for the unanticipated user" - 1/17/2009 1:42:00 PM
Norbert Mikula - 1/17/2009 5:29:00 PM
RESTful, Secure, Non-SSL Authentication - 1/17/2009 5:47:00 PM
RE: [xml-dev] Norbert Mikula - 1/17/2009 8:52:00 PM
B2MML schemas and definition of Equipment Classes - 1/19/2009 10:01:00 PM
=?UTF-8?B?UkU6IFt4bWwtZGV2XSBNZWFuaW5nIG9mICJEZXNpZ24gZm9yIHRoZSB1bmFudGljaXBhdGVkIHVzZXIi?= - 1/20/2009 2:35:00 PM
XSLT Stylesheet test for special character - 1/21/2009 2:04:00 AM
[ANN] Axl Library 0.5.6 'Bohemian like you' release is ready! - 1/21/2009 11:22:00 AM
Validate an instance document that has a replaceable datacomponent, specified by a taxonomy - 1/21/2009 5:36:00 PM
Validate **against** a schema OR validate **with** a schema? - 1/22/2009 12:27:00 PM
Re: [xml-dev] XSLT Stylesheet test for special character - 1/22/2009 12:57:00 PM
XSLT Stylesheet Exclude Parental Search Results? - 1/22/2009 1:01:00 PM
Re: [xml-dev] Validate **against** a schema OR validate **with** a schema? - 1/23/2009 4:04:00 AM
[ANN] XMLmind XSL-FO Converter 4.3 released - 1/23/2009 9:35:00 AM
Interesting (and useful) tidbits about the ID datatype - 1/23/2009 4:12:00 PM
XSLT stylesheet looping through the same node (recursion?) - 1/26/2009 1:31:00 PM
Re: [xml-dev] XSLT Stylesheet Exclude Parental Search Results? - 1/26/2009 1:36:00 PM
Re: [xml-dev] XSLT stylesheet looping through the same node - 1/27/2009 1:04:00 PM
Re: [xml-dev] XSLT stylesheet looping through the same node - 1/28/2009 1:06:00 PM
XSD elementFormDefault="unqualified" destroys the benefits ofnamespace modularity - 1/28/2009 1:34:00 PM
Keep business-process-specific data separate? - 1/28/2009 4:12:00 PM
Re: [xml-dev] Keep business-process-specific data separate? - 1/28/2009 4:20:00 PM
RE: [xml-dev] Keep business-process-specific data separate? - 1/28/2009 4:31:00 PM
RE: Keep business-process-specific data separate? - 1/28/2009 5:10:00 PM
Re: [xml-dev] Keep business-process-specific data separate? - 1/28/2009 6:38:00 PM
RE: [xml-dev] Keep business-process-specific data separate? - 1/29/2009 12:56:00 AM
RE: Keep business-process-specific data separate? - 1/29/2009 1:07:00 PM
[Summary] Keep business-process-specific data separate? - 1/29/2009 2:16:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 1/29/2009 4:16:00 PM
RE: [xml-dev] RE: Keep business-process-specific data separate? - 1/29/2009 4:42:00 PM
RE: Keep business-process-specific data separate? - 1/30/2009 1:33:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 1/30/2009 2:04:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 1/30/2009 3:24:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 1/30/2009 4:12:00 PM
RE: [xml-dev] RE: Keep business-process-specific data separate? - 1/30/2009 9:21:00 PM
Re: [xml-dev] RE: Keep business-process-specific data separate? - 1/31/2009 1:43:00 AM
Rules of Thumb for Creating XML Vocabularies for WorkflowApplications [Was: Keep business-process-specific data separate?] - 1/31/2009 1:17:00 PM
[ANN] XML Prague final program announced - 1/29/2009 2:03:00 PM
Same element, different type - 1/29/2009 7:13:00 PM
Fw: [xml-dev] XSLT stylesheet looping through the same node (recursion?) - 1/30/2009 12:58:00 PM
xml 1.0 document declaration question. - 1/31/2009 11:10:00 AM
Attention! Your PayPal account was limited! - 1/31/2009 7:34: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