This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Implementation FAQ:processing v3 schema with standard tools"

From HL7Wiki
Jump to navigation Jump to search
(add .NET 2.0)
m
Line 5: Line 5:
 
**The HL7 v3 schemas work right out of the box when using Microsoft.NET Framework 2.0
 
**The HL7 v3 schemas work right out of the box when using Microsoft.NET Framework 2.0
 
*The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
 
*The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
*MSXML (versions prior to v6): messages don't validate, although they're know to be valid. They validate using MSXML v6.
+
*MSXML (versions prior to v6): messages don't validate, although they're known to be valid. They validate using MSXML v6.

Revision as of 17:05, 27 December 2006

This page documents implementers' experience with tools. Note that the contents of this page do not constitute a recommendation for specific tools by any part of the HL7 organization, the intent is to document experiences and show workarounds if required.

  • Microsoft .NET Framework
  • The Symphonia toolkit (version ??) has a problem with minOccurs=0 maxOccurs=0 and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
  • MSXML (versions prior to v6): messages don't validate, although they're known to be valid. They validate using MSXML v6.