ASSOCIATION SIMPLIFICATION. ISSUES WITH ASSOCIATIONS Defining Associations (and association sets) in order to represent links is cumbersome Associations.

Slides:

Advertisements

Similar presentations

OASIS OData Technical Committee. AGENDA Introduction OASIS OData Technical Committee OData Overview Work of the Technical Committee Q&A.

Advertisements

Chapter 6: Entity-Relationship Model (part I)

SAP/R3 Development workbench Data Dictionary R/3 table types: –Transparent tables Each table definition in DDIC has an underlying physical table of same.

Quick Start to VHDL VHDL Very Hard Difficult Language Very Hard Difficult Language!!!!!!!

UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.

Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to.

Chapter 6 UNDERSTANDING AND DESIGNING QUERIES AND REPORTS.

OPEN DATA PROTOCOL (ODATA) DEEP DIVE A common, open, RESTful Web protocol for querying and updating data that provides a uniform way to unlock data and.

UDDI Ashish Jain University of Colorado 3 October, 2001.

Cal Poly Knowledge Base Gigi Choy Alex Kleissner Eric Litak Frank Vasquez Brandon Wirick.

1 Pertemuan 6 The structure part of object data model (Lanjutan) Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.

Developing a Basic Web Page with HTML

PRJ566: PROJECT PLANNING AND MANAGEMENT Class Diagrams.

UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.

CSCI 242 Relational Data Modeling Copyright 2011, David C. Roberts, all rights reserved.

CSCI 6442 Entity-Relation Data Modeling Copyright 2012, David C. Roberts, all rights reserved.

1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.

ICOM 5016 – Introduction to Database Systems Lecture 4 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,

UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.

LINQ Boot Camp ADO.Net Entity Framework Presenter : Date : Mahesh Moily Nov 26, 2009.

Web Services Experience Language Web Services eXperience Language Technical Overview Ravi Konuru e-Business Tools and Frameworks,

Grant Number: IIS Institution of PI: Arizona State University PIs: Zoé Lacroix Title: Collaborative Research: Semantic Map of Biological Data.

Improving Design Workflow in Architectural Design Applications Presentation Doctoral Seminar 16/06/2006 Leuven (Belgium)

Unified Modeling Language, Version 2.0

Open Data Protocol * Han Wang 11/30/2012 *

Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.

DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.

Unified Modeling Language © 2002 by Dietrich and Urban1 ADVANCED DATABASE CONCEPTS Unified Modeling Language Susan D. Urban and Suzanne W. Dietrich Department.

Primer Themes: Creating a Cloud App With TOSCA Gerd Breiter Frank Leymann Thomas Spatzier.

CMSC420: Splay Trees Kinga Dobolyi Based off notes by Dave Mount.

Entity Relationship Diagram. Introduction Definition: Entity-relationship diagram is a data-modeling technique that visualises entities, the attributes.

Wednesday Warm-up (independent, level 0 noise): You have 20 feet of fencing and you want to build a dog kennel that is a perfect square. What will.

Class Diagram. Classes Software Design (UML) Class Name attributes operations A class is a description of a set of objects that share the same attributes,

Class and Sequence diagrams UML notation SE-2030 Dr. Mark L. Hornick 1.

Relationships Relationships between objects and between classes.

Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.

Lab 5 CPIT 250 System Analysis and Design.

Class Diagram Chapter 21 Applying UML and Patterns Craig Larman.

XHTML References and Rules William Pegram Revised 9/5/2012.

On Effective Object Manipulation in Virtual Environments making scene design easier.

A table is a set of data elements (values) that is organized using a model of vertical columns (which are identified by their name) and horizontal rows.

Part One Key Concepts in Salesian Youth Ministry.

1 Unified Modeling Language, Version 2.0 Chapter 2.

1 Announcements Reading for next week: Chapters 8 and 10  Last reading from the text for a little while (I promise) About those database accounts....

What we’ll cover today one short intro to linked data our ‘new bibliographic framework’ options, in linked data terms some tools, and ways to discover.

Analysis of Use Cases (and to some extent, standards) - Keith G Jeffery, Rebecca Koskela.

Chapter 6 Lesson C Creating Custom Forms. Lesson C Objectives Convert data blocks to control blocks Link data blocks to control blocks Create a form that.

Class Diagram Lecture # 1. Class diagram A Class Diagram is a diagram describing the structure of a system shows the system's classes Attributes operations.

ODATA DESIGN PRINCIPLES July 26, BUILD ON HTTP, REST OData is a RESTful HTTP Protocol Build on HTTP Entities modeled as Resources Relationships.

RDFa Primer Bridging the Human and Data webs Presented by: Didit ( )

UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.

AUTOMATIC GENERATION OF MODEL TRAVERSALS FROM METAMODEL DEFINITIONS Authors: Tomaž Lukman, Marjan Mernik, Zekai Demirezen, Barrett Bryant, Jeff Gray ACM.

Classification, Identification and BIM

Smith’s Aerospace © P. Bailey & K. Vander Linden, 2006 Classes and Objects Patrick Bailey Keith Vander Linden Calvin College.

Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.

Modeling with UML – Class Diagrams

EF Relations Object Composition

Inline Vs. External Policy Attachment SCA Policy Framework

Module 8: “Top Twelve” Now we come to reminders of things we want to be sure to take with you from today’s session. We have selected a “top twelve”

SysML v2 Formalism: Requirements & Benefits

Systems Analysis and Design With UML 2

1.1 Sets and Subsets.

Object Oriented Analysis and Design

Understand and Use Object Oriented Methods

CIMI Semantic Binding Issue

Module 9: “Top Twelve” LC RDA for NASIG - June 1, 2011

ER Example Expressed as IMM Core Instance Specifications

Please include this slide if you answered “yes” to at least one of the questions.

Presentation transcript:

ASSOCIATION SIMPLIFICATION

ISSUES WITH ASSOCIATIONS Defining Associations (and association sets) in order to represent links is cumbersome Associations are bi-directional Difficult to do Composition Want to model root as a single entity

ASSOCIATIONS TODAY <NavigationProperty Name="Titles" Relationship="Netflix.Catalog.v2.Genre_Titles" ToRole="Genre_Titles_Target" FromRole="Genre_Titles_Source" /> <NavigationProperty Name="Genre" Relationship="Netflix.Catalog.v2.Genre_Titles" ToRole="Genre_Titles_Source" FromRole="Genre_Titles_Target" /> <NavigationProperty Name="Titles" Relationship="Netflix.Catalog.v2.Genre_Titles" ToRole="Genre_Titles_Target" FromRole="Genre_Titles_Source" /> <NavigationProperty Name="Genre" Relationship="Netflix.Catalog.v2.Genre_Titles" ToRole="Genre_Titles_Source" FromRole="Genre_Titles_Target" />

HOW ASSOCIATIONS COULD LOOK <NavigationProperty Name="Titles" Type="Collection(Netflix.Catalog.V2.Title)" Partner="Genre"/> <NavigationProperty Name="Genre" Type"Netflix.Catalog.v2.Genre" nullable="false" Partner="Titles"/> <NavigationProperty Name="Titles" Type="Collection(Netflix.Catalog.V2.Title)" Partner="Genre"/> <NavigationProperty Name="Genre" Type"Netflix.Catalog.v2.Genre" nullable="false" Partner="Titles"/>

ROOT ENTITY Often you have a single root element, with properties, with relationships to other EntitySets Model as a "Named Entity" rooted at the entity container:

CHANGES Support specifying Type, Nullability, Partner in Navigation Property Partner may be optional Specify NavigationPropertyBinding in EntitySet Binding may be optional Addition of "Top Level Entity" Supports root entity

BENEFITS Simpler to read Information is localized where you expect to find it Enables one-way relationships Makes it easier to support Composition Doesn't change OData semantics, behavior, etc.

DISCUSSION Instead of root element make the EntityContainer an entity type