Chapter 2: Designing XML DTDs
|
|
|
- Arleen Weaver
- 8 years ago
- Views:
Transcription
1 2. Designing XML DTDs 2-1 Chapter 2: Designing XML DTDs References: Tim Bray, Jean Paoli, C.M. Sperberg-McQueen: Extensible Markup Language (XML) 1.0, [ See also: [ Elliotte R. Harold, W. Scott Means: XML in a Nutshell, 3rd Ed. O Reilly, 2004, ISBN Didier Martin, Mark Birbeck, Michael Kay: Professional XML, 2nd Ed. Wrox, Henning Lobin: Informationsmodellierung in XML und SGML. Springer-Verlag, Erhard Rahm, Gottfried Vossen: Web & Datenbanken. Dpunkt Verlag, Meike Klettke, Holger Meyer: XML & Datenbanken. Dpunkt Verlag, Akmal B. Chaudhri et al.: XML Data Management. Addison-Wesley, Eve Maler, Jeanne El Andaloussi: Developing SGML DTDs: From Text to Model to Markup. Prentice Hall PTR, 1996.
2 2. Designing XML DTDs 2-2 Objectives After completing this chapter, you should be able to: develop an XML DTD for a given application. translate a given Entity-Relationship-Diagram or relational database schema into an XML DTD.
3 2. Designing XML DTDs 2-3 Overview 1. Motivation, Example Database 2. Single Rows 3. Grouping Rows: Tables 4. Relationships
4 2. Designing XML DTDs 2-4 Motivation (1) In order to use XML, one must specify the document/data file structure. This specification does not necessarily have to be in the form of a DTD, but DTDs are simple and there are many tools that work with DTDs. DTDs were inherited from SGML, and are more intended for documents. Databases have other restrictions that cannot be expressed in DTDs, therefore XML documents might be valid with respect to the specified DTD that do not correspond to a legal database state. XML Schema was developed as an alternative to DTDs that fulfills better the special requirements of databases.
5 2. Designing XML DTDs 2-5 Motivation (2) Often, XML is used as an exchange format between databases. Then it is clear that one must find an XML structure that corresponds to the given DB. There are a lot of methods, tools, and theory for developing database schemas. Therefore, even if one does not (yet) store the data in a database, it makes sense to develop first a DB schema in order to design an XML data structure. If XML is used as a poor man s database, and not for real documents which typically have a less stringent structure.
6 2. Designing XML DTDs 2-6 Example Database (1) STUDENTS SID FIRST LAST 101 Ann Smith 102 Michael Jones (null) 103 Richard Turner 104 Maria Brown EXERCISES CAT ENO TOPIC MAXPT H 1 Rel. Algeb. 10 H 2 SQL 10 M 1 SQL 14 RESULTS SID CAT ENO POINTS 101 H H M H H M H M 1 7
7 2. Designing XML DTDs 2-7 Example Database (2) STUDENTS: one row for each student in the course. SID: Student ID (unique number). FIRST, LAST: First and last name. address (can be null). EXERCISES: one row for each exercise. CAT: Exercise category. E.g. H : homework, M : midterm exam, F : final exam. ENO: Exercise number (within category). TOPIC: Topic of the exercise. MAXPT: Max. no. of points (How many points is it worth?).
8 2. Designing XML DTDs 2-8 Example Database (3) RESULTS: one row for each submitted solution to an exercise. SID: Student who wrote the solution. This references a row in STUDENTS. CAT, ENO: Identification of the exercise. Together, this uniquely identifies a row in EXERCISES. POINTS: Number of points the student got for the solution. A missing row means that the student did not yet hand in a solution to the exercise.
9 2. Designing XML DTDs 2-9 Example Database (4) SID First (0, ) Student Last solved Points Cat (0, ) Exercise Topic ENO MaxPt This is an equivalent schema in the ER-Model. ER = Entity-Relationship. Entities are another name for objects (object types / classes are shown as boxes in the ER-diagram). Relationships between objects (object types) are shown as diamonds. Attributes are pieces of data that are stored about objects or relationships (shown as ovals). Optional attributes are marked with a circle. Key attributes (which uniquely identify objects) are underlined.
10 2. Designing XML DTDs 2-10 Overview 1. Motivation, Example Database 2. Single Rows 3. Grouping Rows: Tables 4. Relationships
11 2. Designing XML DTDs 2-11 Table Rows: Method I A simple and natural way to encode relational data is to use one empty element per table row: <STUDENT SID= 101 FIRST= Ann LAST= Smith = smith@acm.org /> This could be declared as follows: <!ELEMENT STUDENT EMPTY> <!ATTLIST STUDENT SID CDATA #REQUIRED FIRST CDATA #REQUIRED LAST CDATA #REQUIRED CDATA #IMPLIED> See next slide for the data type of SID.
12 2. Designing XML DTDs 2-12 Data Types, Keys (1) In SGML, SID can be declared as NUMBER (instead of CDATA). NUMBER-values are sequences of digits ( 0). In XML, this is not supported. The nearest one could come would be NMTOKEN, but that would also permit letters (as well as -, _, :,.). This might make the real data type even less clear. If references to students are needed (see below), ID might be the right type for the attribute SID. This is supported in SGML and XML. However, now the restriction is lost that SID is a number. But note that ID-values must start with a letter. Or _ or :. Thus, the data values have to be changed, e.g. S101 instead of 101.
13 2. Designing XML DTDs 2-13 Data Types, Keys (2) Note also that ID-values must be globally unique in an XML document. In contrast, key values have to be unique only within a relation (corresponding to an element type in this translation). Finally, composed keys (e.g., CAT and ENO) cannot be directly translated to ID-attributes. In the example, one could concatenate the two attributes, this would also solve the problem that ID-values must start with a letter: E.g., H1, H2, M1. The problem with this is that it is now more difficult to access category and exercise number separately. It might be good to choose the attribute name ID instead of SID (purpose clear even without DTD).
14 2. Designing XML DTDs 2-14 Data Types, Keys (3) These problems to represent data types in XML has led to the XML Schema proposal. Specifications in XML Schema are an alternative to DTDs. XML Schema permits basically all that is possible in classical databases (and more), but it is much more complicated than DTDs. Whereas DTDs use a different syntax than the XML data syntax, XML Schema specifications are valid XML documents. Unfortunately, this also means that XML Schema specifications are significantly longer than the corresponding DTD. When the XML data are only an export from a database, and not directly modified, it is unnecessary to specify all constraints also for the XML file. They are automatically satisfied.
15 2. Designing XML DTDs 2-15 Data Types, Keys (4) The most common XML data types for attributes are CDATA (strings), ID (unique identifiers), NMTOKEN (words/codes), and enumeration types. E.g., if it is clear that the only possible exercise categories are homeworks, midterm, and final, exercises could be represented as follows: <!ELEMENT EXERCISE EMPTY> <!ATTLIST EXERCISE CAT (H M F) #REQUIRED ENO CDATA #REQUIRED TOPIC CDATA #REQUIRED MAXPT CDATA #REQUIRED>
16 2. Designing XML DTDs 2-16 Special Characters If the XML file is generated by exporting data from a database, characters that are forbidden within attribute values must be escaped: Replace < by <. Replace & by &. Replace an apostrophe ( ) by '. If this character is used as a string delimiter. Special national characters must be represented in UTF-8, or an XML declaration that specifies an encoding must be used.
17 2. Designing XML DTDs 2-17 Table Rows: Method II (1) An alternative is to use a nested structure with an element per attribute, plus one per row: <STUDENT> <SID>101</SID> <FIRST>Ann</FIRST> <LAST>Smith</LAST> < >smith@acm.org</ > </STUDENT> Advantage (?): Only elements, no attributes. Disadvantage: Longer.
18 2. Designing XML DTDs 2-18 Table Rows: Method II (2) The declaration in an XML DTD would look as follows: <!ELEMENT STUDENT (SID, FIRST, LAST, ?)> <!ELEMENT SID (#PCDATA)> <!ELEMENT FIRST (#PCDATA)> <!ELEMENT LAST (#PCDATA)> <!ELEMENT (#PCDATA)> In SGML, one could use & instead of, to permit an arbitrary sequence of the subelements. In XML, one would have to simulate this with. For a larger number of columns, this gives very long and complex content models.
19 2. Designing XML DTDs 2-19 Method I vs. Method II (1) In the document processing community, one usually puts the real text into the element content, so that one would still get the important information if all tags were removed. In the example, one could discuss whether SID and should be attributes as in Method I, but at least first name and last name should be elements as in Method II. The database community has no such rules.
20 2. Designing XML DTDs 2-20 Method I vs. Method II (2) Example for a mixture of both methods: <STUDENT ID= S101 = smith@acm.org > <FIRST>Ann</FIRST> <LAST>Smith</LAST> </STUDENT> This can be declared as follows: <!ELEMENT STUDENT (FIRST, LAST)> <!ATTLIST STUDENT ID ID #REQUIRED CDATA #IMPLIED> <!ELEMENT FIRST (#PCDATA)> <!ELEMENT LAST (#PCDATA)>
21 2. Designing XML DTDs 2-21 Method I vs. Method II (3) Method II is of course advantageous if attributes values are XML data. If one does not know the structure, the content model ANY can be used (note that there are no parentheses around ANY). Enumeration values and unique identifications are only possible with Method I. Of course, also in Method II, special characters must be escaped. An alternative is to use a CDATAsection.
22 2. Designing XML DTDs 2-22 Overview 1. Motivation, Example Database 2. Single Rows 3. Grouping Rows: Tables 4. Relationships
23 2. Designing XML DTDs 2-23 Grouping Rows (1) One possibility is to create one element for each relation/table, e.g. <?xml version= 1.0 encoding= ISO ?> <GRADES-DB> <STUDENTS> <STUD SID= 101 FIRST= Ann.../> <STUD SID= 102 FIRST= Michael.../>... </STUDENTS>... </GRADES-DB>
24 2. Designing XML DTDs 2-24 Grouping Rows (2) An alternative is to have no such containers: <?xml version= 1.0 encoding= ISO ?> <GRADES-DB> <STUDENT SID= 101 FIRST= Ann LAST= Smith /> <STUDENT SID= 102 FIRST= Michael LAST= Jones />... <EXERCISE CAT= H ENO= 1 TOPIC= Rel. Algeb. />... <RESULT SID= 101 CAT= H ENO= 1 POINTS= 10 />... </GRADES-DB>
25 2. Designing XML DTDs 2-25 Grouping Rows (3) If there are no table groups, one can require that all rows of a single table are written consecutively: <!ELEMENT GRADES-DB (STUDENT*, EXERCISE*, RESULT*)> <!ELEMENT STUDENT EMPTY>... An alternative is to require no specific sequence: <!ELEMENT GRADES-DB (STUDENT EXERCISE RESULT)*>
26 2. Designing XML DTDs 2-26 Grouping Rows (4) Within a table, one can group rows by an attribute: <EXERCISES> <CAT LETTER= H > <EX ENO= 1 TOPIC= Rel. Algeb. MAXPT= 10 /> <EX ENO= 2 TOPIC= SQL MAXPT= 10 /> </CAT> <CAT LETTER= M > <EX ENO= 1 TOPIC= SQL MAXPT= 14 /> </CAT> </EXERCISES> EX does not need an attribute CAT : Its value can be derived from the enclosing CAT element.
27 2. Designing XML DTDs 2-27 Ordered Data (1) In relational databases, the rows within a table have no specific sequence. If the sequence is important, and cannot be recovered by ordering the rows by one of the columns, a column must be added that encodes the sequence (e.g. a number). XML documents are always ordered. Therefore it might be possible to leave out columns that can be derived from the position in the file.
28 2. Designing XML DTDs 2-28 Ordered Data (2) If e.g. the exercise number is always sequential, it does not have to be stored explicitly: <EXERCISES> <CAT LETTER= H > <EX TOPIC= Rel. Algeb. MAXPT= 10 /> <EX TOPIC= SQL MAXPT= 10 /> </CAT> <CAT LETTER= M > <EX TOPIC= SQL MAXPT= 14 /> </CAT> </EXERCISES>
29 2. Designing XML DTDs 2-29 Overview 1. Motivation, Example Database 2. Single Rows 3. Grouping Rows: Tables 4. Relationships
30 2. Designing XML DTDs :n Relationships (1) The example database contains only a many-tomany (n:m) relationship, which is discussed below. An example for a one-to-many (1:n) relationship is: Professor Name (0, ) Phone teaches (1,1) Term Course Title One professor teaches many courses (between 0 and =, i.e. arbitrarily many), but each course is taught by exactly one professor (min 1, max 1).
31 2. Designing XML DTDs :n Relationships (2) In the relational model, the relationship teaches is implemented by adding the key of professor as a foreign key to the course table: PROFESSORS NAME PHONE Brass Zimmermann COURSES TERM TITLE PROF Summer 2004 Databases Design Brass Winter 2004 Foundations of the WWW Brass Summer 2004 Compiler Construction Zimmermann
32 2. Designing XML DTDs :n Relationships (3) One-to-many relationships can be easily represented by nesting the elements for the many side (in this case Course) into the elements for the one side (Professor): See example on next slide. This nesting can be extended to arbitrary depth to represent a tree of one-to-many relationships. Example: Suppose that the times when the course meets (class) has to be stored for each course (courses can meet several times per week).
33 2. Designing XML DTDs :n Relationships (4) <?xml version= 1.0 encoding= ISO ?> <COURSE-DB> <PROFESSOR NAME= Brass PHONE= > <COURSE TERM= Summer 2004 TITLE= Database Design /> <COURSE TERM= Winter 2004 TITLE= Foundations of the WWW /> </PROFESSOR> <PROFESSOR NAME= Zimmermann PHONE= > <COURSE TERM= Summer 2004 TITLE= Compiler Construction /> </PROFESSOR> </COURSE-DB>
34 2. Designing XML DTDs :n Relationships (5) <?xml version= 1.0 encoding= ISO ?> <COURSE-DB> <PROFESSOR NAME= Brass PHONE= > <COURSE TERM= Summer 2004 TITLE= Database Design > <CLASS DAY= MON FROM= 10 TO= 12 /> <CLASS DAY= THU FROM= 16 TO= 18 /> </COURSE> <COURSE TERM= Winter 2004 TITLE= Foundations of the WWW > <CLASS DAY= WED FROM= 14 TO= 16 /> </COURSE>...
35 2. Designing XML DTDs 2-35 Foreign Keys (1) An alternative is to represent the professor-course relationship with ID- and IDREF-attributes: <!ELEMENT COURSE-DB (PROFESSOR COURSE)*> <!ELEMENT PROFESSOR EMPTY> <!ATTLIST PROFESSOR NAME ID #REQUIRED PHONE CDATA #REQUIRED> <!ELEMENT COURSE EMPTY> <!ATTLIST COURSE TERM CDATA #REQUIRED TITLE CDATA #REQUIRED PROF IDREF #REQUIRED> This is very similar to the relational solution.
36 2. Designing XML DTDs 2-36 Foreign Keys (2) <?xml version= 1.0 encoding= ISO ?> <COURSE-DB> <PROFESSOR NAME= Brass PHONE= /> <COURSE TERM= Summer 2004 PROF= Brass TITLE= Database Design /> <COURSE TERM= Winter 2004 PROF= Brass TITLE= Foundations of the WWW /> <PROFESSOR NAME= Zimmermann PHONE= > <COURSE TERM= Summer 2004 PROF= Zimmermann TITLE= Compiler Construction /> </COURSE-DB>
37 2. Designing XML DTDs 2-37 Foreign Keys (3) IDREF-attributes are similar to foreign keys, but there are the following differences: ID/IDREF-attribute values must be identifiers. E.g. S. Brass could not be used as value of an ID-attribute. IDREF attributes can refer to any element that as an ID-attribute. One cannot specify that PROF in COURSE must point to a professor. In the example, only PROFESSOR has an ID-attribute. Then this problem does not occur. The relational model permits keys that consist of several attributes (not supported in DTDs).
38 2. Designing XML DTDs 2-38 n:m Relationships (1) The student grades database contains a many-tomany (n:m) relationship: One student can solve many exercises. One exercise can be solved by many students. In this case references are unavoidable (at least if duplicate storage of the same entities is excluded): Either the results are nested under students (then result elements must point to exercises), or results are nested under exercises (then they must point to students).
39 2. Designing XML DTDs 2-39 n:m Relationships (2) <?xml version= 1.0 encoding= ISO ?> <GRADES-DB> <STUDENT SID= 101 FIRST= Ann LAST= Smith = > <RESULT CAT= H ENO= 1 POINTS= 10 /> <RESULT CAT= H ENO= 2 POINTS= 8 /> <RESULT CAT= M ENO= 3 POINTS= 12 /> </STUDENT>... <EXERCISE CAT= H ENO= 1 TOPIC= Rel. Algeb. MAXPT= 10 />... </GRADES-DB>
40 2. Designing XML DTDs 2-40 n:m Relationships (3) <?xml version= 1.0 encoding= ISO ?> <GRADES-DB> <STUDENT ID= S101 FIRST= Ann LAST= Smith = />... <EXERCISE CAT= H ENO= 1 TOPIC= Rel. Algeb. MAXPT= 10 > <RESULT STUD= S101 POINTS= 10 /> <RESULT STUD= S102 POINTS= 9 /> <RESULT STUD= S103 POINTS= 5 /> </EXERCISE>... </GRADES-DB>
41 2. Designing XML DTDs 2-41 n:m Relationships (4) As is well known in databases, one can replace a many-to-many relationship by an association entity (RESULTS) and two one-to-many relationships. One of the relationships is represented by nesting the elements, the other relationship is represented by references. Given an arbitrary ER-diagram, one would first replace the many-tomany relationships in this way by association entities, and then cut the resulting graph of one-to-many relationships into trees. References are needed for cutted edges, the trees are represented by nesting. This technique was already used for the very old hierarchical data model.
Chapter 3: XML Namespaces
3. XML Namespaces 3-1 Chapter 3: XML Namespaces References: Tim Bray, Dave Hollander, Andrew Layman: Namespaces in XML. W3C Recommendation, World Wide Web Consortium, Jan 14, 1999. [http://www.w3.org/tr/1999/rec-xml-names-19990114],
Last Week. XML (extensible Markup Language) HTML Deficiencies. XML Advantages. Syntax of XML DHTML. Applets. Modifying DOM Event bubbling
XML (extensible Markup Language) Nan Niu (nn@cs.toronto.edu) CSC309 -- Fall 2008 DHTML Modifying DOM Event bubbling Applets Last Week 2 HTML Deficiencies Fixed set of tags No standard way to create new
Quiz! Database Indexes. Index. Quiz! Disc and main memory. Quiz! How costly is this operation (naive solution)?
Database Indexes How costly is this operation (naive solution)? course per weekday hour room TDA356 2 VR Monday 13:15 TDA356 2 VR Thursday 08:00 TDA356 4 HB1 Tuesday 08:00 TDA356 4 HB1 Friday 13:15 TIN090
The Entity-Relationship Model
The Entity-Relationship Model 221 After completing this chapter, you should be able to explain the three phases of database design, Why are multiple phases useful? evaluate the significance of the Entity-Relationship
DTD Tutorial. About the tutorial. Tutorial
About the tutorial Tutorial Simply Easy Learning 2 About the tutorial DTD Tutorial XML Document Type Declaration commonly known as DTD is a way to describe precisely the XML language. DTDs check the validity
Introduction to XML. Data Integration. Structure in Data Representation. Yanlei Diao UMass Amherst Nov 15, 2007
Introduction to XML Yanlei Diao UMass Amherst Nov 15, 2007 Slides Courtesy of Ramakrishnan & Gehrke, Dan Suciu, Zack Ives and Gerome Miklau. 1 Structure in Data Representation Relational data is highly
Semistructured data and XML. Institutt for Informatikk INF3100 09.04.2013 Ahmet Soylu
Semistructured data and XML Institutt for Informatikk 1 Unstructured, Structured and Semistructured data Unstructured data e.g., text documents Structured data: data with a rigid and fixed data format
XML: extensible Markup Language. Anabel Fraga
XML: extensible Markup Language Anabel Fraga Table of Contents Historic Introduction XML vs. HTML XML Characteristics HTML Document XML Document XML General Rules Well Formed and Valid Documents Elements
Structured vs. unstructured data. Semistructured data, XML, DTDs. Motivation for self-describing data
Structured vs. unstructured data 2 Semistructured data, XML, DTDs Introduction to databases CSCC43 Winter 2011 Ryan Johnson Databases are highly structured Well-known data format: relations and tuples
Database Design Overview. Conceptual Design ER Model. Entities and Entity Sets. Entity Set Representation. Keys
Database Design Overview Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Conceptual design The Entity-Relationship (ER) Model, UML High-level, close to human thinking Semantic
Structured vs. unstructured data. Motivation for self describing data. Enter semistructured data. Databases are highly structured
Structured vs. unstructured data 2 Databases are highly structured Semistructured data, XML, DTDs Well known data format: relations and tuples Every tuple conforms to a known schema Data independence?
Databases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on our hands is a dead shark. Woody
2. Conceptual Modeling using the Entity-Relationship Model
ECS-165A WQ 11 15 Contents 2. Conceptual Modeling using the Entity-Relationship Model Basic concepts: entities and entity types, attributes and keys, relationships and relationship types Entity-Relationship
14 Databases. Source: Foundations of Computer Science Cengage Learning. Objectives After studying this chapter, the student should be able to:
14 Databases 14.1 Source: Foundations of Computer Science Cengage Learning Objectives After studying this chapter, the student should be able to: Define a database and a database management system (DBMS)
Database Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB
Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB Outline Database concepts Conceptual Design Logical Design Communicating with the RDBMS 2 Some concepts Database: an
Translating between XML and Relational Databases using XML Schema and Automed
Imperial College of Science, Technology and Medicine (University of London) Department of Computing Translating between XML and Relational Databases using XML Schema and Automed Andrew Charles Smith acs203
CS 501- Software Engineering. Legal Data Markup Software DTD Design Document. Version 1.0
CS 501- Software Engineering Legal Data Markup Software DTD Design Document Version 1.0 Document Revision History Date Version Description Author 11/27/00 1.0 Draft for Delivery LDMS Team Confidential
04 XML Schemas. Software Technology 2. MSc in Communication Sciences 2009-10 Program in Technologies for Human Communication Davide Eynard
MSc in Communication Sciences 2009-10 Program in Technologies for Human Communication Davide Eynard Software Technology 2 04 XML Schemas 2 XML: recap and evaluation During last lesson we saw the basics
Outline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst
Outline Data Modeling Yanlei Diao UMass Amherst v Conceptual Design: ER Model v Relational Model v Logical Design: from ER to Relational Slides Courtesy of R. Ramakrishnan and J. Gehrke 1 2 Conceptual
SQL DATA DEFINITION: KEY CONSTRAINTS. CS121: Introduction to Relational Database Systems Fall 2015 Lecture 7
SQL DATA DEFINITION: KEY CONSTRAINTS CS121: Introduction to Relational Database Systems Fall 2015 Lecture 7 Data Definition 2 Covered most of SQL data manipulation operations Continue exploration of SQL
Database Design Process. Databases - Entity-Relationship Modelling. Requirements Analysis. Database Design
Process Databases - Entity-Relationship Modelling Ramakrishnan & Gehrke identify six main steps in designing a database Requirements Analysis Conceptual Design Logical Design Schema Refinement Physical
Database Systems. Lecture 1: Introduction
Database Systems Lecture 1: Introduction General Information Professor: Leonid Libkin Contact: libkin@ed.ac.uk Lectures: Tuesday, 11:10am 1 pm, AT LT4 Website: http://homepages.inf.ed.ac.uk/libkin/teach/dbs09/index.html
XML and Data Integration
XML and Data Integration Week 11-12 Week 11-12 MIE253-Consens 1 Schedule Week Date Lecture Topic 1 Jan 9 Introduction to Data Management 2 Jan 16 The Relational Model 3 Jan. 23 Constraints and SQL DDL
XML Schema Definition Language (XSDL)
Chapter 4 XML Schema Definition Language (XSDL) Peter Wood (BBK) XML Data Management 80 / 227 XML Schema XML Schema is a W3C Recommendation XML Schema Part 0: Primer XML Schema Part 1: Structures XML Schema
XML and Data Management
XML and Data Management XML standards XML DTD, XML Schema DOM, SAX, XPath XSL XQuery,... Databases and Information Systems 1 - WS 2005 / 06 - Prof. Dr. Stefan Böttcher XML / 1 Overview of internet technologies
Introduction to normalization. Introduction to normalization
Introduction to normalization Lecture 4 Instructor Anna Sidorova Agenda Presentation Review of relational models, in class exersise Introduction to normalization In-class exercises Discussion of HW2 1
OData Extension for XML Data A Directional White Paper
OData Extension for XML Data A Directional White Paper Introduction This paper documents some use cases, initial requirements, examples and design principles for an OData extension for XML data. It is
Exercise 1: Relational Model
Exercise 1: Relational Model 1. Consider the relational database of next relational schema with 3 relations. What are the best possible primary keys in each relation? employ(person_name, street, city)
Standard Recommended Practice extensible Markup Language (XML) for the Interchange of Document Images and Related Metadata
Standard for Information and Image Management Standard Recommended Practice extensible Markup Language (XML) for the Interchange of Document Images and Related Metadata Association for Information and
A Document Management System Based on an OODB
Tamkang Journal of Science and Engineering, Vol. 3, No. 4, pp. 257-262 (2000) 257 A Document Management System Based on an OODB Ching-Ming Chao Department of Computer and Information Science Soochow University
Entity-Relationship Model
UNIT -2 Entity-Relationship Model Introduction to ER Model ER model is represents real world situations using concepts, which are commonly used by people. It allows defining a representation of the real
How To Use Xml In A Web Browser (For A Web User)
Anwendersoftware a Advanced Information Management Chapter 3: XML Basics Holger Schwarz Universität Stuttgart Sommersemester 2009 Overview Motivation Fundamentals Document Type Definition (DTD) XML Namespaces
Content Management for Declarative Web Site Design
Content Management for Declarative Web Site Design Richard Cooper and Michael Davidson Computing Science University of Glasgow DIWeb 1 8/6/2004 Talk Overview Motivation for uniform declarative approach
1. Write the query of Exercise 6.19 using TRC and DRC: Find the names of all brokers who have made money in all accounts assigned to them.
1. Write the query of Exercise 6.19 using TRC and DRC: Find the names of all brokers who have made money in all accounts assigned to them. TRC: DRC: {B.Name Broker(B) AND A Account (A.BrokerId = B.Id A.Gain
Relational Databases for Querying XML Documents: Limitations and Opportunities. Outline. Motivation and Problem Definition Querying XML using a RDBMS
Relational Databases for Querying XML Documents: Limitations and Opportunities Jayavel Shanmugasundaram Kristin Tufte Gang He Chun Zhang David DeWitt Jeffrey Naughton Outline Motivation and Problem Definition
A Workbench for Prototyping XML Data Exchange (extended abstract)
A Workbench for Prototyping XML Data Exchange (extended abstract) Renzo Orsini and Augusto Celentano Università Ca Foscari di Venezia, Dipartimento di Informatica via Torino 155, 30172 Mestre (VE), Italy
www.gr8ambitionz.com
Data Base Management Systems (DBMS) Study Material (Objective Type questions with Answers) Shared by Akhil Arora Powered by www. your A to Z competitive exam guide Database Objective type questions Q.1
CS 4604: Introduc0on to Database Management Systems. B. Aditya Prakash Lecture #5: En-ty/Rela-onal Models- - - Part 1
CS 4604: Introduc0on to Database Management Systems B. Aditya Prakash Lecture #5: En-ty/Rela-onal Models- - - Part 1 Announcements- - - Project Goal: design a database system applica-on with a web front-
Entity Relationship Diagram
Yufei Tao Department of Computer Science and Engineering Chinese University of Hong Kong A primary goal of database design is to decide what tables to create. Usually, there are two principles: 1 Capture
Literature for the 1 st part
Database and Knowledge-base Systems Range: 3+1, 5 credits, finished by examination Lecturer: Prof. Ing. Jiří Bíla, DrSc. (bila@vc.cvut.cz) (Vice-Rector for External Relations, CTU) Other teachers: ing.
Instant SQL Programming
Instant SQL Programming Joe Celko Wrox Press Ltd. INSTANT Table of Contents Introduction 1 What Can SQL Do for Me? 2 Who Should Use This Book? 2 How To Use This Book 3 What You Should Know 3 Conventions
Database Design and Programming
Database Design and Programming Peter Schneider-Kamp DM 505, Spring 2012, 3 rd Quarter 1 Course Organisation Literature Database Systems: The Complete Book Evaluation Project and 1-day take-home exam,
Database Design Patterns. Winter 2006-2007 Lecture 24
Database Design Patterns Winter 2006-2007 Lecture 24 Trees and Hierarchies Many schemas need to represent trees or hierarchies of some sort Common way of representing trees: An adjacency list model Each
2009 Martin v. Löwis. Data-centric XML. Other Schema Languages
Data-centric XML Other Schema Languages Problems of XML Schema According to Schematron docs: No support for entities idiomatic or localized data types (date, time) not supported limited support for element
Chapter 3. Data Modeling Using the Entity-Relationship (ER) Model
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Chapter Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts Entities and Attributes Entity
Lesson 8: Introduction to Databases E-R Data Modeling
Lesson 8: Introduction to Databases E-R Data Modeling Contents Introduction to Databases Abstraction, Schemas, and Views Data Models Database Management System (DBMS) Components Entity Relationship Data
Chapter 6: Physical Database Design and Performance. Database Development Process. Physical Design Process. Physical Database Design
Chapter 6: Physical Database Design and Performance Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS 464 Spring 2003 Topic 23 Database
Data Integration for XML based on Semantic Knowledge
Data Integration for XML based on Semantic Knowledge Kamsuriah Ahmad a, Ali Mamat b, Hamidah Ibrahim c and Shahrul Azman Mohd Noah d a,d Fakulti Teknologi dan Sains Maklumat, Universiti Kebangsaan Malaysia,
CHAPTER 6 DATABASE MANAGEMENT SYSTEMS. Learning Objectives
CHAPTER 6 DATABASE MANAGEMENT SYSTEMS Management Information Systems, 10 th edition, By Raymond McLeod, Jr. and George P. Schell 2007, Prentice Hall, Inc. 1 Learning Objectives Understand the hierarchy
The Relational Model. Ramakrishnan&Gehrke, Chapter 3 CS4320 1
The Relational Model Ramakrishnan&Gehrke, Chapter 3 CS4320 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. Legacy systems in older models
by LindaMay Patterson PartnerWorld for Developers, AS/400 January 2000
Home Products Consulting Industries News About IBM by LindaMay Patterson PartnerWorld for Developers, AS/400 January 2000 Copyright IBM Corporation, 1999. All Rights Reserved. All trademarks or registered
Lecture 6. SQL, Logical DB Design
Lecture 6 SQL, Logical DB Design Relational Query Languages A major strength of the relational model: supports simple, powerful querying of data. Queries can be written intuitively, and the DBMS is responsible
CSE 530A Database Management Systems. Introduction. Washington University Fall 2013
CSE 530A Database Management Systems Introduction Washington University Fall 2013 Overview Time: Mon/Wed 7:00-8:30 PM Location: Crow 206 Instructor: Michael Plezbert TA: Gene Lee Websites: http://classes.engineering.wustl.edu/cse530/
COMP 5138 Relational Database Management Systems. Week 5 : Basic SQL. Today s Agenda. Overview. Basic SQL Queries. Joins Queries
COMP 5138 Relational Database Management Systems Week 5 : Basic COMP5138 "Relational Database Managment Systems" J. Davis 2006 5-1 Today s Agenda Overview Basic Queries Joins Queries Aggregate Functions
XEP-0043: Jabber Database Access
XEP-0043: Jabber Database Access Justin Kirby mailto:justin@openaether.org xmpp:zion@openaether.org 2003-10-20 Version 0.2 Status Type Short Name Retracted Standards Track Expose RDBM systems directly
Designing Databases. Introduction
Designing Databases C Introduction Businesses rely on databases for accurate, up-to-date information. Without access to mission critical data, most businesses are unable to perform their normal daily functions,
XML Implementation Guide: General Information
: General Information Copyright 2000 Mortgage Industry Standards Maintenance Organization (MISMO). All rights reserved Permission to use, copy, modify, and distribute the MISMO DTD and its accompanying
Introduction to Database Systems. Chapter 1 Introduction. Chapter 1 Introduction
Introduction to Database Systems Winter term 2013/2014 Melanie Herschel melanie.herschel@lri.fr Université Paris Sud, LRI 1 Chapter 1 Introduction After completing this chapter, you should be able to:
TRANSITIONING EXISTING CONTENT: INFERRING ORGANIZATION-SPECIFIC DOCUMENTS. Arijit Sengupta 1, Sandeep Purao 1, 2
TRANSITIONING EXISTING CONTENT: INFERRING ORGANIZATION-SPECIFIC DOCUMENTS Arijit Sengupta 1, Sandeep Purao 1, 2 1: Department of CIS, Robinson College of Business, Georgia State University, Atlanta, GA
7. XQuery 7-1. Chapter 7: XQuery. Scott Boag, Don Chamberlin, Mary F. Fernńndez, Daniela Florescu, Jonathan Robie,
7. XQuery 7-1 Chapter 7: XQuery References: Scott Boag, Don Chamberlin, Mary F. Fernńndez, Daniela Florescu, Jonathan Robie, Jérôme Siméon (Eds.): XQuery 1.0: An XML Query Language. W3C Recommendation
Concepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method
Concepts of Database Management Seventh Edition Chapter 6 Database Design 2: Design Method Objectives Discuss the general process and goals of database design Define user views and explain their function
<Namespaces> Core XML Technologies. Why Namespaces? Namespaces - based on unique prefixes. Namespaces. </Person>
Core XML Technologies Namespaces Why Namespaces? bob roth 814.345.6789 Mariott If we combine these two documents
Managing Typed Hybrid XML and Relational Data Sources for Web Content Management
Managing Typed Hybrid XML and Relational Data Sources for Web Content Management Richard Cooper? and Michael Davidson? Computing Science, University of Glasgow, 17 Lilybank Gardens, Glasgow G12 8QQ rich@dcs.gla.ac.uk
Chapter 5: Introduction to SGML and XML
5. Introduction to SGML and XML 5-1 Chapter 5: Introduction to SGML and XML References: Liora Alschuler: ABCD... SGML A User s Guide to Structured Information. International Thomson Computer Press (ITP),
Answer Key. UNIVERSITY OF CALIFORNIA College of Engineering Department of EECS, Computer Science Division
Answer Key UNIVERSITY OF CALIFORNIA College of Engineering Department of EECS, Computer Science Division CS186 Fall 2003 Eben Haber Midterm Midterm Exam: Introduction to Database Systems This exam has
The Relational Model. Why Study the Relational Model? Relational Database: Definitions. Chapter 3
The Relational Model Chapter 3 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase,
TIM 50 - Business Information Systems
TIM 50 - Business Information Systems Lecture 15 UC Santa Cruz March 1, 2015 The Database Approach to Data Management Database: Collection of related files containing records on people, places, or things.
Introduction to Computing. Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn
Introduction to Computing Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn Databases The Hierarchy of Data Keys and Attributes The Traditional Approach To Data Management Database A collection of
Instructor: Michael J. May Semester 1 of 5775. The course meets 9:00am 11:00am on Sundays. The Targil for the course is 12:00pm 2:00pm on Sundays.
Syllabus for ISM 14-324: Database Systems Department of Software and Information Systems Achi Racov School of Engineering Kinneret College on the Sea of Galilee Instructor: Michael J. May Semester 1 of
Xml Mediator and Data Management
Adaptive Data Mediation over XML Data Hui Lin, Tore Risch, Timour Katchaounov Hui.Lin, Tore.Risch, Timour.Katchaounov@dis.uu.se Uppsala Database Laboratory, Uppsala University, Sweden To be published in
XML. Document Type Definitions XML Schema
XML Document Type Definitions XML Schema 1 Well-Formed and Valid XML Well-Formed XML allows you to invent your own tags. Valid XML conforms to a certain DTD. 2 Well-Formed XML Start the document with a
Application of XML Tools for Enterprise-Wide RBAC Implementation Tasks
Application of XML Tools for Enterprise-Wide RBAC Implementation Tasks Ramaswamy Chandramouli National Institute of Standards and Technology Gaithersburg, MD 20899,USA 001-301-975-5013 chandramouli@nist.gov
Data Integration through XML/XSLT. Presenter: Xin Gu
Data Integration through XML/XSLT Presenter: Xin Gu q7.jar op.xsl goalmodel.q7 goalmodel.xml q7.xsl help, hurt GUI +, -, ++, -- goalmodel.op.xml merge.xsl goalmodel.input.xml profile.xml Goal model configurator
Databases and BigData
Eduardo Cunha de Almeida eduardo.almeida@uni.lu Outline of the course Introduction Database Systems (E. Almeida) Distributed Hash Tables and P2P (C. Cassagnes) NewSQL (D. Kim and J. Meira) NoSQL (D. Kim)
XML WEB TECHNOLOGIES
XML WEB TECHNOLOGIES Chakib Chraibi, Barry University, cchraibi@mail.barry.edu ABSTRACT The Extensible Markup Language (XML) provides a simple, extendable, well-structured, platform independent and easily
Course: Introduction to XML
1 / 69 Course: Introduction to XML Pierre Genevès CNRS University of Grenoble, 2012 2013 2 / 69 What you should probably know... Prog(p)... var k : int;... for i =... {... } let y=x; write(y)... Parsing
1 File Processing Systems
COMP 378 Database Systems Notes for Chapter 1 of Database System Concepts Introduction A database management system (DBMS) is a collection of data and an integrated set of programs that access that data.
OBJECT ORIENTED EXTENSIONS TO SQL
OBJECT ORIENTED EXTENSIONS TO SQL Thomas B. Gendreau Computer Science Department University Wisconsin La Crosse La Crosse, WI 54601 gendreau@cs.uwlax.edu Abstract Object oriented technology is influencing
Fundamentals of Database Design
Fundamentals of Database Design Zornitsa Zaharieva CERN Data Management Section - Controls Group Accelerators and Beams Department /AB-CO-DM/ 23-FEB-2005 Contents : Introduction to Databases : Main Database
Database Design and the E-R Model
C H A P T E R 7 Database Design and the E-R Model Practice Exercises 7.1 Answer: The E-R diagram is shown in Figure 7.1. Payments are modeled as weak entities since they are related to a specific policy.
XML. CIS-3152, Spring 2013 Peter C. Chapin
XML CIS-3152, Spring 2013 Peter C. Chapin Markup Languages Plain text documents with special commands PRO Plays well with version control and other program development tools. Easy to manipulate with scripts
Relational Database Basics Review
Relational Database Basics Review IT 4153 Advanced Database J.G. Zheng Spring 2012 Overview Database approach Database system Relational model Database development 2 File Processing Approaches Based on
Data Tool Platform SQL Development Tools
Data Tool Platform SQL Development Tools ekapner Contents Setting SQL Development Preferences...5 Execution Plan View Options Preferences...5 General Preferences...5 Label Decorations Preferences...6
The Relational Model. Why Study the Relational Model? Relational Database: Definitions
The Relational Model Database Management Systems, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Microsoft, Oracle, Sybase, etc. Legacy systems in
How To Improve Performance In A Database
Some issues on Conceptual Modeling and NoSQL/Big Data Tok Wang Ling National University of Singapore 1 Database Models File system - field, record, fixed length record Hierarchical Model (IMS) - fixed
Foundations of Information Management
Foundations of Information Management - WS 2009/10 Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Alexander Markowetz Born 1976 in Brussels, Belgium
Database Management. Technology Briefing. Modern organizations are said to be drowning in data but starving for information p.
Technology Briefing Database Management Modern organizations are said to be drowning in data but starving for information p. 509 TB3-1 Learning Objectives TB3-2 Learning Objectives TB3-3 Database Management
SQL Server. 1. What is RDBMS?
SQL Server 1. What is RDBMS? Relational Data Base Management Systems (RDBMS) are database management systems that maintain data records and indices in tables. Relationships may be created and maintained
Oracle SQL. Course Summary. Duration. Objectives
Oracle SQL Course Summary Identify the major structural components of the Oracle Database 11g Create reports of aggregated data Write SELECT statements that include queries Retrieve row and column data
Jet Data Manager 2012 User Guide
Jet Data Manager 2012 User Guide Welcome This documentation provides descriptions of the concepts and features of the Jet Data Manager and how to use with them. With the Jet Data Manager you can transform
Using XML to Test Web Software Services. Modern Web Sites
Using XML to Test Web Software Services Jeff Offutt Information & Software Engineering George Mason University Fairfax, VA USA www.ise.gmu.edu/faculty/ofut/ Joint research with Suet Chun Lee, GMU PhD student
Oracle Database 10g: Introduction to SQL
Oracle University Contact Us: 1.800.529.0165 Oracle Database 10g: Introduction to SQL Duration: 5 Days What you will learn This course offers students an introduction to Oracle Database 10g database technology.
EXTENDED LEARNING MODULE A
EXTENDED LEARNING MODULE A DESIGNING DATABASES AND ENTITY- RELATIONSHIP DIAGRAMMING Student Learning Outcomes 1. Identify how databases and spreadsheets are both similar and different. 2. List and describe
Semantic Errors in SQL Queries: A Quite Complete List
Semantic Errors in SQL Queries: A Quite Complete List Christian Goldberg, Stefan Brass Martin-Luther-Universität Halle-Wittenberg {goldberg,brass}@informatik.uni-halle.de Abstract We investigate classes
Managing XML Documents Versions and Upgrades with XSLT
Managing XML Documents Versions and Upgrades with XSLT Vadim Zaliva, lord@crocodile.org 2001 Abstract This paper describes mechanism for versioning and upgrding XML configuration files used in FWBuilder
Developing a Framework for Building Open Distance Learning Websites in the Literature and Culture Domain
Developing a Framework for Building Open Distance Learning Websites in the Literature and Culture Domain Alexander Schatten, A Min Tjoa Insitute for Software Technology, Vienna University of Technology
An Approach to Eliminate Semantic Heterogenity Using Ontologies in Enterprise Data Integeration
Proceedings of Student-Faculty Research Day, CSIS, Pace University, May 3 rd, 2013 An Approach to Eliminate Semantic Heterogenity Using Ontologies in Enterprise Data Integeration Srinivasan Shanmugam and
A Brief Introduction to MySQL
A Brief Introduction to MySQL by Derek Schuurman Introduction to Databases A database is a structured collection of logically related data. One common type of database is the relational database, a term
Computer Programming I
Computer Programming I COP 2210 Syllabus Spring Semester 2012 Instructor: Greg Shaw Office: ECS 313 (Engineering and Computer Science Bldg) Office Hours: Tuesday: 2:50 4:50, 7:45 8:30 Thursday: 2:50 4:50,
7. Classification. Business value. Structuring (repetition) Automation. Classification (after Leymann/Roller) Automation.
7. Classification Business Process Modelling and Workflow Management Business value Lecture 4 (Terminology cntd.) Ekkart Kindler kindler@upb.de Structuring (repetition) Automation UPB SS 2006 L04 2 Classification