This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Candidate Mapping Notations"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
*The OMG QVT (Query-Verify-Transform) languages, defined in the [http://www.omg.org/spec/QVT/1.1/Beta2/PDF QVT Specification] | *The OMG QVT (Query-Verify-Transform) languages, defined in the [http://www.omg.org/spec/QVT/1.1/Beta2/PDF QVT Specification] | ||
| − | *The tabular mapping notation used by the mapping and transformation tools on the | + | *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] |
| + | |||
XSLT is a third 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. | XSLT is a third 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. | ||
Revision as of 12:44, 6 June 2010
As at June 2010, two main candidate notations have been identified for evaluation:
- The OMG QVT (Query-Verify-Transform) languages, defined in the QVT Specification
- The tabular mapping notation used by the mapping and transformation tools on the HL7 GForge site
XSLT is a third 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.
