# Structured Data REST Protocol for End to End Data Mashup
## 7 Implementation
### Pre-Mashup Configuration (OTC Model)  
This section describes how the ordinary user can define mashup requirement of the data in user-friendly manner and what kinds of outputs are generated after pre-mashup configuration. Here, not only the output of pre-mashup configuration is important but also the user-friendly approach used by ordinary user needs to be observed. The success of any mashup tool depends on output of the pre-mashup configuration and the way this output is generated by ordinary user. In our proposed work, a very simple approach (i.e., filling the web forms/selecting the radio buttons) is used by an ordinary user to create the SDXMapping which is the output of pre-mashup configuration. In the proposed work, defining mashup requirement of the data is as simple as making the list of the name of attributes. Structured data mashup box can also be associated with data mashup definition soon after the declaration of the requirement of the data mashup. We took the following sample data set to execute proposed work for experimental purpose only and it has nothing to do with real world's data. Suppose, Data Mashup Definition (DMD) defined by EU#01 are as follows  
DMD for SDMB#01 (Admission Services) = (notice_id, notice_title, name_of_university, contact_no, link_to_apply, name_of_course, last_date) DMD for SDMB#02 (Job Services) = (job_id, job_title, job_description, salary, contact_no, link_to_apply, years_of_exp, last_date) DMD for SDMB#03 (Lodging Services) = (hotel_name, hotel_address, total_rooms, room_charges, contact_no, booking_link)  
Figure 7: Data Mashup Service Network. Let us understand the SDXMapping of lodging services between various stakeholders of hybrid data mashup as shown in Figure 1 where EU#01 works as data service consumer for MSP#01 and DSP#03.MSP#01 further works as data service consumer for DSP#01 and DSP#02. Suppose in Figure 1,  
EU#01 = www.user1.com  
MSP#01 = www.msp1.com  
DSP#01 = www.hotel1.com  
DSP#02 = www.hotel2.com  
DSP#03 = www.hotel3.com  
According to above assumptions, Figure 1 can be redrawn as given in the Figure 8.  
The graphical interface, which we developed in the proposed work for pre-mashup configuration has been shown in Figure 9. This interface easily creates the SDXMapping between EU #01 and MSP#01 and looks like 'Column Match Problem'. It can be noticed in Figure 9 that attribute \"hotel_name\" of EU#01's data mashup definition is mapped with attribute \"hotlName\" of MSP#01's mashup service. Similarly, the other attribute's mapping can also be observed. The SDXMapping is created as a result of pre-mashup configuration between data service consumer and MSP/DSP but once only. Similar kinds of user-friendly graphical interfaces were also developed for pre-mashup configuration between other stakeholders in this example. It can be observed here that this kind of graphical approach for pre-mashup configuration is easier for any kind of ordinary user because it simply includes clicking on the radio buttons. Other kinds of user-friendly graphical interfaces can also be designed for an ordinary user for pre-mashup configuration. Attributes of data service consumer are shown in leftmost vertical column and attributes of MSP/DSP are shown in horizontal top rows in Figure 9.  
Figure 8: Hybrid Data Mashup for Lodging Services. Figure 9: SDXMapping between EU#01 and MSP#01. Let us consider the data set taken for end to end SDXMapping between EU#01 and other stakeholders (i.e., MSP#01 and DSP#03) in Table 8. It is called end to end SDXMapping because there is a direct mapping between DMDAttributes of EU#01 and MCAAttributes of MSP#01 as well as a direct mapping between DMDAttributes of EU#01 and MCAAttributes of DSP#03. Let us consider the data set taken for end to end SDXMapping between MSP#01 and other stakeholders (i.e., DSP#01 and DSP#02) in Table 9. It is clear from Figure 9 that MSP#01 directly interacts with DSP#01 and DSP#02 hence there is need of end to end SDXMapping between them.