This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Candidate Mapping Notations"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | At July 2010, three candidate notations have been identified for evaluation: | |
| − | |||
*The tabular mapping notation used by the mapping and transformation tools on the [http://gforge.hl7.org/gf/project/v2v3-mapping/frs/ HL7 GForge site] | *The tabular mapping notation used by the mapping and transformation tools on the [http://gforge.hl7.org/gf/project/v2v3-mapping/frs/ HL7 GForge site] | ||
| + | *The OMG QVT (Query-Verify-Transform) languages, defined in the [http://www.omg.org/spec/QVT/1.1/Beta2/PDF QVT Specification] | ||
| + | *The OMG MDMI (Model Based Message Interoperability) language | ||
| − | XSLT is | + | XSLT is another possibility, but is currently not being considered as it is usually not easy to read and understand. Proprietary structure-to-structure (S2S) mapping notations, such as that in Altova’s MapForce, are not being considered because they do not support semantic mapping. |
[[Neutral Mapping|Return to top page on mapping notations]] | [[Neutral Mapping|Return to top page on mapping notations]] | ||
Revision as of 09:42, 23 July 2010
At July 2010, three candidate notations have been identified for evaluation:
- The tabular mapping notation used by the mapping and transformation tools on the HL7 GForge site
- The OMG QVT (Query-Verify-Transform) languages, defined in the QVT Specification
- The OMG MDMI (Model Based Message Interoperability) language
XSLT is another possibility, but is currently not being considered as it is usually not easy to read and understand. Proprietary structure-to-structure (S2S) mapping notations, such as that in Altova’s MapForce, are not being considered because they do not support semantic mapping.
