ORM Verbalization in Malay & Mandarin Lim Shin Huei Terry Halpin.

Slides:



Advertisements
Similar presentations
Multilinguality & Semantic Search Eelco Mossel (University of Hamburg) Review Meeting, January 2008, Zürich.
Advertisements

Database Design: ER Modelling
1 CHAPTER 4 RELATIONAL ALGEBRA AND CALCULUS. 2 Introduction - We discuss here two mathematical formalisms which can be used as the basis for stating and.
1 Modeling Reactive Behavior in ORM © 2003, T. A. Halpin & Gerd Wagner Terry Halpin Northface University Salt Lake City, USA.
1 Enviromatics Spatial database systems Spatial database systems Вонр. проф. д-р Александар Маркоски Технички факултет – Битола 2008 год.
Modeling the Data: Conceptual and Logical Data Modeling
Chapter 6 Methodology Logical Database Design for the Relational Model Transparencies © Pearson Education Limited 1995, 2005.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Methodology Logical Database Design for the Relational Model
Chapter 3: Modeling Data in the Organization
Methodology Conceptual Database Design
Chapter 3 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Importance of data modeling Importance of data modeling Write good.
NORMA Lab. 1 Installing NORMA Entering a simple ORM schema Generating a Relational View Generating DDL code Generating other code 1 Note: Some of these.
1 NORMA Lab. 4 File: NORMA_Lab4.ppt. Author: T. Halpin. Last updated: 2011 September 6 Revision: Adding Value Constraints, Set-comparison Constraints Adding.
1 © Prentice Hall, 2002 CMIS564: E/R Modeling Dr. Bordoloi Based on Chapter 3; Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
IS 325 Notes for Wednesday September 18, 2013.
Quick and Easy Costumization Enhancement ModulesOn-Site Development SAP B1 Usability Package How to sell SAP Business One with B1UP ”click to continue”..
An Approach to Task Modelling for User Interface Design Costin Pribeanu National Institute for Research and Development in Informatics, Bucureşti, Romania.
Fuzzy Logic. Lecture Outline Fuzzy Systems Fuzzy Sets Membership Functions Fuzzy Operators Fuzzy Set Characteristics Fuzziness and Probability.
An Introduction to Software Architecture
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
A Z Approach in Validating ORA-SS Data Models Scott Uk-Jin Lee Jing Sun Gillian Dobbie Yuan Fang Li.
1 NORMA Lab. 2 Revision: Unary and Binary Fact Types Ternary Fact Types Inclusive-Or Constraints External Uniqueness Constraints Value Constraints Derived.
CSC 395 – Software Engineering Lecture 13: Object-Oriented Analysis –or– Let the Pain Begin (At Least I’m Honest!)
1 NORMA Lab. 6 Adding Sample Populations Controlling Error Message Display File: NORMA_Lab6.ppt. Author: T. Halpin. Last updated: 2009 June 12.
Dreamweaver MX. 2 Overview of Templates n Templates represent a web page design or _______ that will be common to multiple pages. n There are two situations.
1 NORMA Lab. 7 Generating Reports More Display Options File: NORMA_Lab6.ppt. Author: T. Halpin. Last updated: 2009 June 9.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant.
1 NORMA Lab. 5 Duplicating Object Type and Predicate Shapes Finding Displayed Shapes Using the Diagram Spy Using Multiple Windows Using the Context Window.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Metamodels for Object Role Modeling Hongyan Song March 2005.
UML-1 3. Capturing Requirements and Use Case Model.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
UML-1 8. Capturing Requirements and Use Case Model.
1 Introduction to modeling ER modelling Slides for this part are based on Chapters 8 from Halpin, T. & Morgan, T. 2008, Information Modeling and Relational.
Part4 Methodology of Database Design Chapter 07- Overview of Conceptual Database Design Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
1 Introduction to modeling Object-role modelling (ORM) Slides for this part are based on Chapters 3-7 from Halpin, T. & Morgan, T. 2008, Information Modeling.
CSE314 Database Systems Lecture 3 The Relational Data Model and Relational Database Constraints Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
1 NORMA Lab. 3 File NORMA_Lab3.ppt. Author: T. Halpin. Last updated 2009 May 25 Revision: Unary and Binary fact types Adding Pages Objectification Independent.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Chapter 3 Special Section Focus on Karnaugh Maps.
Chapter – 8 Software Tools.
Introduction to modeling
A Test Case Suite for Hornlog+ RuleML 1.01 A Test Case Suite for Hornlog+ RuleML 1.01 CS6795 Semantic Web Techniques Team 3: Zhenzhi Cui Radhika Yadav.
1/28 A 2-valued Logic Approach to Querying Factbases Terry Halpin 1 and Matthew Curland 2 1 INTI International University, Malaysia 2 ORM Solutions, USA.
1 Reference Scheme Reduction on Subtypes in ORM Andy Carver and Terry Halpin INTI International University, Malaysia
MDD-Kurs / MDA Cortex Brainware Consulting & Training GmbH Copyright © 2007 Cortex Brainware GmbH Bild 1Ver.: 1.0 How does intelligent functionality implemented.
Data Modeling Using the Entity- Relationship (ER) Model
Product Training Program
Interface Concepts Modeling Core Team
Business System Development
Methodology Logical Database Design for the Relational Model
Enhanced Verbalization of ORM Models
Object-Oriented Analysis and Design
Database Management Systems
Chapter 7: Entity-Relationship Model
Business Process Measures
NORMA Lab. 4 Revision: Adding Value Constraints, Set-comparison Constraints Adding Frequency Constraints Adding Ring Constraints Adding Subtyping Adding.
NORMA Lab. 7 Generating Reports More Display Options
NORMA Lab. 2 Revision: Unary and Binary Fact Types Ternary Fact Types
NORMA Lab. 5 Duplicating Object Type and Predicate Shapes
SYS466 Domain Classes – Part 1.
ETSI TC MTS TDL SC meeting Reports
Towards Semantically Grounded Decision Rules Using ORM+
NORMA Lab. 6 Adding Sample Populations
CHAPTER 2 - Database Requirements and ER Modeling
ETSI TC MTS TDL SC meeting Reports
ETSI TC MTS TDL SC meeting Reports
Presentation transcript:

ORM Verbalization in Malay & Mandarin Lim Shin Huei Terry Halpin

Introduction ORM data models enable many kinds of business constraints to be visualized graphically These are best validated with domain experts by verbalizing them in a controlled natural language and populating them with examples. We are currently extending ORM technology to automatically verbalize ORM models in Malay & Mandarin. These languages require special treatment in order to render natural verbalization, especially Noun Classifiers. We discuss the basic ideas behind our approach and demonstrate an initial prototype

Logical Elements & Noun Classifiers We first transform ORM constraints to an underlying logical form, which is then transformed to linguistic forms suited to the target natural languages. The logic form patterns include slots for various logical elements such as quantifiers and operators which have corresponding textual representations. Here is a list of the correspondences for the modal operators.

Here is a list of the most common quantifiers and their verbalizations in three languages. We use the symbol “  ” to denote any appropriate noun classifier for the term being quantified.

Here are a few examples of noun classifiers, with Malay classifiers listed before Mandarin classifiers. Note: Mandarin often has many choices of classifier for the same usage category. In Malay, ‘Orang’ can be used as a noun phrase or a classifier; if an entity type is named ‘Orang’ (meaning Person), no noun classifier is used for it.

Quantifiers are used in verbalizing many kinds of ORM constraints, including internal and external uniqueness and frequency constraints. Here we discuss only internal uniqueness constraints on binary fact types. We focus mainly on the n:1 patterns shown below. Patterns for 1:n, 1:1 and m:n cases may be dealt with similarly.

An ORM predicate may have many readings, which may be in mixfix form, e.g. The fact type “Person played Sport for Country” uses the predicate reading “… played … for …”. The structure of a predicate reading is irrelevant to the logical form, which denotes a predicate by a single symbol (e.g. R or S). Verbalizations may be displayed in positive form (e.g. Each Person was born on at most one Date.) or negative form (e.g. It is impossible that some Person was born on more than one Date.). Mappings for other logical or linguistic elements such as Boolean operators (and, or, not etc. respectively render as “dan” and “atau” and “ bukan” in Malay, and as “ 和 ” and “ 或 ” and “ 不 ” in Mandarin) and pronouns are also needed (e.g. “that” and “the same” respectively render as “itu” and “yang sama” in Malay, and as “ 那  ” and “ 一样的 ” in Mandarin).

Here are the logical forms of the verbalizations for the n:1 patterns. The Malay and Mandarin forms include a noun classifier (denoted here by  ) to categorize the kind of thing being counted. The absence of a simple, alethic uniqueness constraint on a role of an n:1 binary is explicitly verbalized (e.g. It is possible that more than one Person was born in the same Country). E.g. the English logical form of the above is   y:B  2.. x:A xRy. In Malay this is   y:B  2..  x:A xRy; in Mandarin  y:B  2..  x:A xRy .

Implementing ORM Verbalization in Malay & Mandarin Mandarin differs from Malay in allowing more than one choice of noun classifier for the same usage category/noun type. E.g. the combination of mandatory role and  2 frequency constraints on Fishmonger’s role in the fact type Fishmonger sells FishKind, may be verbalized in English as “Each Fishmonger sells more than one FishKind.”. In Malay, the classifier for FishKind is “jenis”. Showing logical words in bold and classifiers in red, this verbalizes in Malay as: “Setiap PenjualIkan menjual lebih daripada satu jenis Spesies Ikan.”. In Mandarin however, any of these verbalizations could be used: 每个鱼贩卖多过一种鱼类 ; 每位鱼贩卖多过一种鱼类 ; 每名鱼 贩卖多过一种鱼类. Which one is best, is decided by the user.

In ORM, each object type has a distinct name which is a noun phase (such as “Postgraduate Student”, “Lecturer”, etc). Using “NounType” for usage category, and “Classifier” for noun classifier, the situation for Mandarin may be modeled as shown. The fact type NounType has Classifier may be prepopulated with known data. However, in general the fact type NounPhrase is of NounType needs to be populated by the user.

For Malay, where the NounType has Classifier is n:1, that derived classifier isthe only possibility. For Mandarin, often more than one classifier is derived, so the user is presented with a list of possible classifiers from which to choose his/her preferred one (see prototype demo later). This metamodel fragment provides one way to view the situation if, instead of using a separate model for each language, one wishes to use a single model with multiple display options based on the language choice.

Here is a screenshot from our prototype tool for entering and verbalizing binary fact types in ORM using Bahasa Malaysia (shown here as the option BM) or Mandarin.

This screenshot shows the Classifier properties dialog that enables users to pick the suitable classifier to use for the relevant NounType.

The table shows the corresponding positive verbalizations in English and Mandarin. The negative form of the verbalizations may be displayed by selecting the negative (-) button. Verbalizations in Malay are performed in a similar manner.

This shows the final screen for the n:1 fact type Politician was born in Country in Malay Verbalization.

Conclusion This paper described our initial work in verbalizing ORM models in Malay and Mandarin, with special attention to verbalizing noun classifiers. Future plans include implementing our approach via language extensions to the NORMA tool, and fully covering all of the many ORM graphical constraint varieties in these Asian languages.