X3ML (3M)

Convert

3M, the Mapping Memory Manager, is an open-source schema-mapping tool run on the X3ML engine. 3M can be used to map and convert data from XML into Linked Data (LD) following the Resource Description Framework (RDF). 3M allows users to create, edit, and save mapping rules so that they can be reused in future data conversion.

To the Tool

To GitHub (X3ML Engine)

To GitLab (X3ML Interface)

3M and LINCS

LINCS uses 3M in the Conversion step of the Structured Data Workflow to convert structured data to Linked Open Data (LOD) following the rules of selected ontologies. LINCS uses CIDOC CRM as its core ontology, along with other ontologies, such as the Web Annotation Data Model (WADM) for specific domain requirements. However, 3M can be configured to work with any properly formed ontology.

LINCS likes 3M because it:

• Creates consistent data following the constraints of the ontology
• Converts new data following the same structure as past conversions
• Supports intermediary nodes, which are often required for CIDOC CRM mappings
• Requires no coding knowledge thanks to its graphical interface

If you are preparing data for contribution to the LINCS triplestore, please consult with the LINCS team before mapping your data in 3M. The LINCS team will work with you to create a conceptual mapping of your data, which you will use to ensure that the LD you create matches your original dataset and supports your research.

You can use the LINCS instance of 3M even if you are not contributing your data to the LINCS triplestore. You simply need to register for an account, wait for account approval from LINCS, and then you are free to use the instance with your data.

info

LINCS recommends you spend some time learning 3M before you start working with your data:

• Students typically take:
  • 1–3 days to become familiar with 3M
  • 2–3 weeks to become intermediate users
• Intermediate users typically take:
  • 1–4 weeks to complete a mapping, depending on the complexity of the data

For more information, see our Conversion Workflows.

Prerequisites

Users of 3M:

• Need to come with their own dataset
• Need to come with a conceptual mapping for their dataset
• Need to create a user account

3M supports the following inputs and outputs:

• Input: XML
• Output: RDF-XML, TTL, N-Triples

info

Need to get your data into XML? Learn more about Preparing Your Data for 3M.

Resources

To learn more about 3M, see the following resources or continue to explore our 3M documentation. Resources prior to 2022 refer to a previous version of 3M, but the information contained in them is useful nonetheless.

Technical Manuals:

• Kritsotakis et al. (2022) “3M Guidelines”
• Theodoridou et al. (2010) “Mapping Memory Manager (3M) Instance and Label Generator Rule Builder”

Introductions and Tutorials:

• Bruseker (2018) “General Introduction to the Use of X3ML Toolkit”
• Kräutli (2018) “CIDOC-CRM by Practice” [Video]
• Theodoridou (2021) “Mapping & Transforming Data for Semantic Integration: The X3ML Toolkit”
• Theodoridou (2018) “The X3ML Toolkit”

Technical Articles and Background Information:

• Marketakis et al. (2017) “X3ML Mapping Framework for Information Integration in Cultural Heritage and Beyond”
• Minadakis et al. (2015) “X3ML Framework: An Effective Suite for Supporting Data Mappings”

Case Study:

• Theodoridou (2014) “Mapping Cultural Heritage Information to CIDOC-CRM”

Information about the team that developed X3ML is available on the Tool Credits page.