Home > Articles > Web Services > XML

  • Print
  • + Share This
This chapter is from the book

16.3 Data Warehouse Specification

This section deals with the data warehouse specification. An XML data warehouse is defined as a set of materialized views. In the first subsection we present our view model for XML documents. Next, we present the graphic tool that enables the data warehouse designer to specify the XML views.

16.3.1 View Model for XML Documents

Since the data warehouse is defined as a set of views, the main issue of data warehouse definition is the view model. We present briefly in this section the main characteristics of our view model. This model has been presented in detail in work by X. Baril and Z. Bellahsène (Baril and Bellahsène 2000).

Our view model fulfills the following requirements:

  • Closure property: A view defined on XML document(s) should yield an XML document as output. This allows us to transparently use a view or a document. From the data warehouse point of view, this property implies that the unified view of sources is an XML document.

  • Restructuring possibilities: The view mechanism enables restructuring elements of the source(s) document(s). We can distinguish two classes of views: (1) select views that extract existing documents from sources, and (2) composite views that create new elements or attributes. For this latter class, new elements of the result may be created from several source elements. Furthermore, aggregation functions (i.e., sum, avg, min, max, count, etc.) can be used to define new values. Moreover, sorting and grouping elements is also provided.

  • DTD inference: The view result should be associated to a DTD. This DTD is inferred from the view definition and possibly from source DTDs if they exist. The inferred DTD can be used to optimize the view storage or to query the view. From the data warehouse point of view, the inferred DTD is used to give a global integrated schema on which user queries can be formulated.

Each view is composed of a result pattern that specifies the structure of the result. This result pattern uses variables that are defined in fragments. A fragment is a collection of patterns: Each pattern uses variables to define data to match in a source. A fragment is composed of several patterns defining the same variables on different sources and provides the union of their data.

For example, let us consider a source "senior.xml" containing information about senior researchers and a source "senior.xml" containing information about Ph.D. students. To define a fragment "f1" containing the names and birthdays of senior researchers and Ph.D. students, we would define two patterns: one pattern matching names and birthdays of the senior researchers on source "senior.xml" and another one matching names and birthdays of the Ph.D. students on source "student.xml".

To define composite views, the result pattern can be based on several fragments. For this purpose, fragments are linked using join conditions. A join condition involves two variables defined in two different fragments.

Listing 16.1 shows a complete example of a view specification involving two fragments. Let us consider a view retrieving for each author their name, surname, and a list of the titles of their publications. The view is composed of a result pattern, two fragments, and a join condition. The fragment "f3" contains a pattern that matches the "author" elements, while "f4" contains a pattern that matches the "inproceedings" elements, with their "title" attribute and "authorlink" subelements. These subelements contain a "ref" attribute that references the author of the publication. The join element gives the join condition between the two fragments "f3" and "f4". The result element contains the result pattern. Each item of the view result is an "author" element, containing a "name" attribute (having the value of the "name" variable) and a "title" subelement (having the value of the "title" variable). The group-by element indicates that the result is grouped by "name" values (i.e., for an author there are possibly several "title" subelements). The part of the DTD validating this specification is presented in section 16.4.2, "View Definition," later in this chapter.

Listing 16.1 Example of View Definition

<view id="authorspublications">
<result>
 <result.node name="author" type="element">
  <result.node name="name" type="attribute">
   <result.node name="name" type="variable"></result.node>
  </result.node>
  <result.node name="title" type="element">
   <result.node name="title" type="variable"></result.node>
  </result.node>
 </result.node>
 <groupby name="name"></groupby>
</result>
<fragment id="f3">
 <pattern id="p3" source="1">
  <pattern.node name="author" type="element">
   <pattern.node name="id" type="attribute"
                 bind="id"></pattern.node>
   <pattern.node name="name" type="attribute"
                 bind="name"></pattern.node>
   <pattern.node name="surname" type="attribute"
                 bind="surname"></pattern.node>
  </pattern.node>
 </pattern>
</fragment>
<fragment id="f4">
 <pattern id="p4" source="1">
  <pattern.node name="inproceedings" type="element">
   <pattern.node name="title" type="attribute" bind="title"></pattern.node>
   <pattern.node name="authorlink" type="element">
    <pattern.node name="ref" type="attribute" bind="ref"></pattern.node>
   </pattern.node>
  </pattern.node>
 </pattern>
</fragment>
<join leftfragment="f3" leftvariable="id"
      rightfragment="f4" rightvariable="ref">
</join>
</view>

16.3.2 Graphic Tool for Data Warehouse Specification

We propose a graphic tool to help the user in the specification of the data warehouse. The editor allows us to create this specification without knowledge of the exact structure of the warehouse definition. We have proposed (in Baril and Bellahsène 2001) helpers for view definitions that we plan to integrate with DAWAX. These helpers allow us to define patterns without knowledge of the source structure. They use the DTD (if available) and the dataguide to propose choices for the pattern specification.

Figure 16.2 shows the graphic editor for the data warehouse specification. The XML document defining the data warehouse is represented as a tree. New elements (sources, views, fragments, etc.) can be added by way of a contextual popup menu. The popup menu suggests possible choices for adding or updating the current element. In the example, the popup menu for a view element suggests the addition of a fragment or a join, and the deletion of a view.

16fig02.gifFigure 16.2. Data Warehouse Definition Editor

The fragment "f4" of the view given as an example is displayed in Figure 16.2. It contains a pattern ("p4") with an identifier and a source attribute. The root pattern node of the pattern is displayed, and due to space limitations, its child nodes are not expanded in the tree.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020