Changes for page Exercises
Last modified by Carlijn Kokkeler on 2022/10/19 13:32
From version 20.1
edited by Carlijn Kokkeler
on 2022/10/19 12:56
on 2022/10/19 12:56
Change comment:
There is no comment for this version
To version 16.1
edited by Carlijn Kokkeler
on 2022/10/19 12:30
on 2022/10/19 12:30
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,37 +9,27 @@ 9 9 10 10 == 2. Key concepts == 11 11 12 -This microlearning centers around understanding the concept data modeling in design. Please note the following items for completing this exercise 13 -* Ensure to make a small Capture phase that draws the system CAPE and a message type "TransportOrder" 14 -* The system CAPE provides messages as JSON 12 +This microlearning centers around understanding the concept data modeling in design. 15 15 16 16 == 3. CDM, CDM & system message, message mapping == 17 17 By following the steps below, you should gain a better understanding of the differences between CDM, CDM messages, and system messages. 18 18 19 19 * Creating a CDM 20 - **Please import the file Order.xsd in your CDM. The code for this file can be found in section 4. Code for xsd files.18 + Please import the file Order.xsd in your CDM. The code for this file can be found in section 4. Code for xsd files. 21 21 * Creating a CDM message 22 - **Now, go to your CDM message and select Order as root entity.23 - **Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition.20 + Now, go to your CDM message and select Order as root entity. 21 + Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition. 24 24 * Creating a system message 25 - **In one of your System messages, import the file TransportOrder.xsd. The code for this file can be foundinsection4. Codeforxsdfiles.23 + In one of your System messages, import the file TransportOrder.xsd. The code for this file can be found at the bottom of this page. 26 26 * Creating a CDM message 27 - **Select CreateOrder as root entity and add all other entities and attributes to your system definition.25 + Select CreateOrder as root entity and add all other entities and attributes to your system definition. 28 28 * Complete message mapping 29 - ** Now that you have completed these steps, go to Message mapping and complete the mapping. Please add the following to the Design mapping 30 - *** Ensure to properly map the address type 31 - *** Ensure to properly document mappings where required 32 -* Update the CDM and CDM message and remove the housenumber attribute 33 - ** Update the mapping accordingly 34 -* Update the System and CDM message to set the country attributes as enumerations 35 - ** System message uses an ISO-2 standard for country code 36 - ** CDM message uses an ISO-3 standard for country code 37 - 27 + Now that you have completed these steps, go to Message mapping and complete the mapping. 38 38 39 39 The solutions to these exercises can be found [[here>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.Solutions.WebHome||target="blank"]]. 40 40 41 41 == 4. Code for xsd files == 42 - === 4.1Code for Order.xsd===32 +Code for Order.xsd: 43 43 {{code language="xml"}} 44 44 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 45 45 xmlns="http://www.carlijnsplatform.com/ns/capetms/cdm/1.0/" ... ... @@ -99,7 +99,7 @@ 99 99 </xs:schema> 100 100 {{/code}} 101 101 102 - === 4.2Code for TransportOrder.xsd===92 +Code for TransportOrder.xsd: 103 103 {{code language="xml"}} 104 104 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 105 105 xmlns="https://transportinc.nl/ns/tms/1.0/"