1. MFI Core model and basic mapping Keith Gordon WG2 N1602

2. Roles  Editor: Masao Okabe  In support: Keith Gordon

3. Packages > CoreModelBasicMappingModel

4. Core Model Model 1..1 0..* ModellingLanguage ▲expressedIn describingLanguage expressedModel ModelElement 0..* 1..* ▼comprises containingModel containedModelElement

5. Relationship to MDR-3 1..1 0..* ModellingLanguage Model ModelElement 0..* 1..* ▲expressedIn ▼comprises describingLanguage expressedModel containingModel containedModelElement > Attached_Item > Administered_Item > Identified_Item > Registered_Item 0..* 1..1 > Designatable_Item 0..* 1..1 DesignationDefinition Context 0..* 1..*

6. Core Model and Mapping 1..1 0..* ModellingLanguage Model ModelElement 0..* 1..* ▲expressedIn ▼comprises describingLanguage expressedModel containingModel containedModelElement mappedElementelementSet ModelElementSet ◄mappedThrough 1..*0..* 1..10..* ModelMapping subjectModelmappingFrom ◄subjectOf objectModelmappingTo ◄objectOf 1..10..* subjectSetmappingFrom ◄subjectOf 1..10..* objectSetmappingTo ◄objectOf 1..10..* ModelElementSetMapping modelElementSetMappingDegree [1..1] 0..1containingModelMapping ▼comprises 1..* containedModelMappingComponent ModelElementSetMappingType 1..1 0..* describedComponent description ▲describes > ModelElementSetMappingDegree semanticallyEquivalent semanticallySimilar

7. Mapping example #1 PRODUCT product-description product-code Product code : String description : String Object Class to Entity Type Object Class to Entity Type mapping Object Class to Entity Type Semantically Equivalent

8. Mapping example #2 Product code : String description : String Supplier number: String name: String address: Address 0..* 1..* ◄supplies ProductSupplier startDate: Date rating: Integer SUPPLIER supplier-name supplier-address supplier-number PRODUCT product-description product-code PRODUCT-SUPPLIER product-supplier-start-date product-supplier-rating product-code (FK) supplier-number (FK) acts-assupplied-by P Object Class to Entity Type Many-to-many association replaced by an intersection entity type Object Class to Entity Type Semantically Equivalent

9. Mapping example #3 Department name : String ExternalCustomer number: String name: String address: Address 1..1 0..* ◄places Order number: String startDate: Date ExternalOrder DepartmentalOrder 1..1 0..* ◄places Object Class to Entity Type Exclusive Arc replaced by Sub- classes Object Class to Entity Type Semantically Equivalent ORDER (m) number (m) date placed by placer of EXTERNAL CUSTOMER (m) number (m) name (m) address placed by DEPARTMENT (m) name placer of

10. Mapping example #4 Object Class to Entity Type Process decomposed Object Class to Entity Type Semantically Equivalent FULFILL ORDER ISSUE INVOICE RECORD PAYMENT Object Class to Entity Type Process amalgamation Object Class to Entity Type Semantically Equivalent CHECK ORDER PICK GOODS DESPATCH GOODS HANDLE PAYMENT StartStop

11. Mapping example #5 Object Class to Entity Type Sequence dependency replacement Object Class to Entity Type Semantically Similar FULFIL ORDER ISSUE INVOICE RECORD PAYMENT Order Received Payment Recorded FULFIL ORDER ISSUE INVOICE RECORD PAYMENT Order Received Payment Recorded Payment Received Invoice Issued

12. Mapping example #6 Concept Union Object Class to Entity Type Semantically Equivalent Ontology A Scotch Whisky Ontology B Single Scotch Whisky Blended Scotch Whisky

13. Mapping example #7 Concept Intersection Object Class to Entity Type Semantically Equivalent Ontology A axiom1: “Scotch whisky is whisky made in Scotland. Ontology B axiom2: “Scotch whisky is a kind of whisky.” axiom3: “Scotch whisky is made in Scotland.”

14. Where we agree  The metaclasses (and their names) - generally  The attributes (and their names) - generally  The associations (and their multiplicities and names)

15. Where we disagree  Whether to use separators or camel case for names. (recommendation: upper camel case for metaclasses, lower camel case for attributes, associations, etc)  How to document associations in the text:  with one reference?  with two references?  (CA prefers associations documented separately) (recommendation: two references)  How and where to explain the relationship to MDR-3.  Okabe-san is not too happy with “model mapping”.  Whether a model must have an IRI.

16. Any questions?