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: | At July 2010, three candidate notations have been identified for evaluation: | ||
| − | *The | + | *The Open Mapping Language, based on that 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 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 | *The OMG MDMI (Model Based Message Interoperability) language | ||
Revision as of 10:07, 23 July 2010
At July 2010, three candidate notations have been identified for evaluation:
- The Open Mapping Language, based on that 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.
