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) |
Rene spronk (talk | contribs) m |
||
| Line 2: | Line 2: | ||
*Known issue with some .NET based tools. (??namespace issues, as far as I know, details needed) | *Known issue with some .NET based tools. (??namespace issues, as far as I know, details needed) | ||
| − | *The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' construct used in datatypes schema. There are a few of those, if removed from the schema they can be imported in Symphonia. | + | *The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' construct used in the base datatypes schema. There are a few of those, if removed from 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 05:09, 7 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.
- Known issue with some .NET based tools. (??namespace issues, as far as I know, details needed)
- The Symphonia toolkit (version ??) has a problem with minOccurs=0 maxOccurs=0 construct used in the base datatypes schema. There are a few of those, if removed from 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.
