Ph.D. Thesis - Business Informatics Group

More documents

Recommendations

Info

Chapter 2 From DTDs to Ecore-based Metamodels Figure 2.2: Process of Designing the WebML Metamodel Such a model has to conform to the WebML DTD describing the WebML language concepts at the metamodel-level (M2). The WebML DTD in turn is based on the DTD-grammar [W3C06] defined at the meta-metamodel-level (M3). Note that, while in case of WebML, a DTD is used to define a modeling language and therefore can be assigned to the M2 level, DTDs typically are used at M1 in order to describe the structure of data stored in XML documents. Analogously, MOF concepts defined at M3 are used to describe metamodels in the sense of MDE at M2. In the present case, this is the targeted WebML metamodel of which instances in terms of WebML models can be formulated at M1. This discussion shows that the two M3 level formalisms, in terms of the DTD-grammar and MOF respectively, represent the concepts on which to identify correspondences. In turn, these correspondences serve as a basis for the M2-level done by the framework presented in Section 2.3. M3 M2 M1 DTD-Grammar conformsTo WebML DTD conformsTo WebML XML Doc Correspondences implies Metamodel Transformation implies Model Transformation conformsTo MOF WebML Metamodel conformsTo WebML Model Figure 2.3: Interrelationships Between the Language Layers of DTD and MOF In the following, UML class diagrams [OMG05e] are used as a common formalism to explain and to illustrate the major concepts of the DTD-grammar (cf. Subsection 2.2.1) and MOF (cf. Subsection 2.2.2). This explanation serves as the basis for identifying differences in the expressiveness of the two meta-meta-languages (cf. Subsection 2.2.3). 20
2.2 DTDs and Ecore at a Glance 2.2.1 Document Type Definition (DTD) Concepts The UML class diagram given in Figure 2.4 is based on previous work [KKR04] and depicts the DTD concepts present in the WebML DTD. These concepts need to be considered for finding correspondences to MOF concepts and consequently are reviewed briefly in the following. * DTD XMLDTD ParameterEntityDec 1 1..* 1 * name:String value:String XMLStringAtt 1..* XMLElemType name:String 1 * XMLAttribute name:String declaration:AttDec XMLTokenAtt kind:TokenKind XMLEnumAtt XMLAtomicET value:String XMLCompositeET XMLEmptyET XMLAnyET 1 1..* XMLEnumLiteral XMLCompositeET MixedContent «enumeration» ContCard • zero-or-one • zero-or-many • one-or-many XMLCompositeET ElemContent XMLElemType * 1 XMLContentParticle cardinality:ContCard [0..1] 1..* nested:Boolean 2..* XMLSequence XMLChoice «enumeration» AttDec • default_value •#REQUIRED •#IMPLIED •#FIXED «enumeration» TokenKind • ID • IDREF • IDREFS •NMTOKEN •NMTOKENS Figure 2.4: Overview of Relevant DTD Language Concepts In general, DTD’s contain markup declarations comprising element types (XMLElemType) and attributes (XMLAttributes) for defining the logical structure as well as primarily entity declarations (e.g., ParameterEntityDec), as a reuse mechanism for certain reoccurring markup declarations, defining the physical structure. Element types, being first-class citizens in DTDs, have a name and are specialized into XMLAtomicET (contains no other element types but character data), XMLEmptyET (no content is allowed), XMLAnyET (the content is not constrained), XMLCompositeETMixed- Content (a mix of character data and child element types), and XMLCompositeETElem- Content (consists of an XMLContentParticle). An XMLContentParticle either is an XMLSequence, an XMLChoice, or an XMLElemType. An XMLChoice or an XMLSequence can be enclosed in parentheses for grouping purposes and suffixed with a ’?’ (zero or one occurrences), ’*’ (zero or more occurrences), or ’+’ (one or more occurrences), whereas the absence of a particular symbol denotes a cardinality of exactly one. Attribute declarations define one or multiple XMLAttributes (i.e., name-value pairs) for a single element type. Each XMLAttribute has a name, a data type, and a default declaration. The most commonly used data types for attributes are: CDATA (XMLStringAtt), ID, IDREF (refers to one ID-typed element), IDREFS (refers to multiple ID-typed elements), 21
Page 1: Ph.D. Thesis From Mining to Mapping
Page 5: Abstract Model-Driven Engineering (
Page 9 and 10: Contents 1 Introduction 1 1.1 Motiv
Page 11 and 12: 7 Summary and Related Work 105 7.1
Page 13 and 14: List of Figures 1.1 Meta-layers of
Page 15 and 16: 10.7 Profile Generation Rule 7 - C2
Page 17 and 18: List of Tables 2.1 Transformation R
Page 19 and 20: Listings 3.1 WebML’s Concepts Gro
Page 21 and 22: Chapter 1 Introduction Contents 1.1
Page 23 and 24: 1.1 Motivation 1.1.2 Model-Driven E
Page 25 and 26: 1.1 Motivation data engineering fie
Page 27 and 28: 1.1 Motivation the green boxes repr
Page 29 and 30: 1.1 Motivation used for defining th
Page 31 and 32: 1.2 Contribution of This Thesis wit
Page 33 and 34: 1.3 Thesis Outline «exists» OO-H.
Page 35: Part I Mining
Page 38 and 39: M3 M2 M1 ML X L A M 1 ML Y L A ‘
Page 42 and 43: Chapter 2 From DTDs to Ecore-based
Page 48 and 49: Chapter 2 From DTDs to Ecore-bas
Page 52 and 53: EBoolean and no EEnum is generated
Page 54 and 55: Heuristic 6 - Inheritance Identific
Page 56 and 57: M3 «conformsTo» Phase 1 Phase 2 D
Page 58 and 59: Chapter 3 Evaluation of the DTD to
Page 60 and 61: 3.1.2 Package "Structure" Chapter 3
Page 66 and 67: ContentManagement Hypertext:: to 0.
Page 68 and 69: Basic Chapter 3 Evaluation of the D
Page 72 and 73: Chapter 4 Summary and Related Work
Page 78 and 79: 58 Chapter 4 Summary and Related Wo
Page 81 and 82: Chapter 5 A Framework for Building
Page 83 and 84: 5.2 Metamodel Bridging Framework ba
Page 85 and 86: 5.2 Metamodel Bridging Framework th
Page 87 and 88: 5.2 Metamodel Bridging Framework to
Page 89 and 90: 5.2 Metamodel Bridging Framework tw
Page 91 and 92:
Chapter 6 CAR - A Mapping Language
Page 93 and 94:
6.2 Mapping Operators These mapping
Page 95 and 96:
6.2 Mapping Operators 6.2.3 R2R Map
Page 97 and 98:
6.2 Mapping Operators Black-Box Vie
Page 99 and 100:
6.2 Mapping Operators * LHS Source
Page 101 and 102:
6.3 An Inheritance Mechanism for Ma
Page 103 and 104:
superClasses type Class 0..* 1 abst
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Angestellter_ANr 6.3 An Inheritance
Page 123 and 124:
Page 125 and 126:
Chapter 7 Summary and Related Work
Page 127 and 128:
7.2 Related Work 7.2.2 Ontology Map
Page 129:
Part III Roundtrip Transformations
Page 132 and 133:
8.1 Motivation Chapter 8 Why Roundt
Page 134 and 135:
Chapter 8 Why Roundtrip Transformat
Page 136 and 137:
Chapter 8 Why Roundtrip Transformat
Page 138 and 139:
Chapter 9 AspectCAR - An Aspect-ori
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
124 Chapter 9 AspectCAR - An Aspect
Page 146 and 147:
Page 148 and 149:
Chapter 10 ProfileGen - A Generator
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
X y Y C2C C2C R2C Gen Chapter 10 Pr
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
1 Chapter 10 ProfileGen - A Generat
Page 172 and 173:
Macro-View - DataModel2UMLModel Cha
Page 174 and 175:
Micro-View - EntityType 2 Class Cha
Page 176 and 177:
Page 178 and 179:
158 Chapter 10 ProfileGen - A Gener
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
providing only a restricted profile
Page 186 and 187:
Chapter 12 Conclusion and Outlook p
Page 188 and 189:
Combining Mapping Operators LHS Map
Page 190 and 191:
Automatic establishment of mapping
Page 192 and 193:
Chapter 12 Conclusion and Outlook o
Page 194 and 195:
Bibliography [BD07] Achim D. Brucke
Page 196 and 197:
Bibliography [Haa07] Laura M. Haas.
Page 198 and 199:
Bibliography [LLPM06] Björn Lundel
Page 200 and 201:
Bibliography [Par72] David L. Parna
Page 202 and 203:
Bibliography [W3C04] World Wide Web
Page 204 and 205:
Bibliography Teaching Assistant Mar
Page 206 and 207:
Bibliography International Workshop
show all

Ph.D. Thesis - Business Informatics Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?