This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Implementation FAQ:processing v3 schema with standard tools"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
(Added resolution for .NET 1.1 issues) |
||
| Line 1: | Line 1: | ||
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. | 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. | ||
| − | * | + | *There are some known issue with Microsoft .NET v1.1, refer to the following: |
| + | ** [http://blogs.msdn.com/rruggeri/archive/2006/07/22/674877.aspx Implementing HL7 v3 Using the .NET Framework 1.1] | ||
*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 know to be valid. They validate using MSXML v6. | ||
Revision as of 13:38, 13 September 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.
- There are some known issue with Microsoft .NET v1.1, refer to the following:
- 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.
