Scribd
Upload
3 views

UNIT 4 Introduction To XML

Uploaded by

Devi Ashritha Ambitus
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
3 views

UNIT 4 Introduction To XML

Uploaded by

Devi Ashritha Ambitus
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

UNIT-4

XML Documents
WHAT IS XML ?
 XML is abbreviated as eXtensible Markup Language. XML is used as
the markup language,it is differed by other markup language by its
properties of designing and describing the data.
 The origin of XML language is generated using Standard Generalized
Markup Language (SGML).
 XML consist of its unique characteristics like tag specification which
gives more advantage to XML
 XML was designed to store and transport data
WHAT IS XML ?
• The XML above is quite self-descriptive:
• It has sender information
• It has receiver information
• It has a heading
• It has a message body
• But still, the XML above does not DO anything. XML is just information wrapped in tags.
Difference Between XML and HTML
XML and HTML were designed with different goals:

• XML was designed to carry data - with focus on what data is.
• HTML was designed to display data - with focus on how data looks.
• XML tags are not predefined like HTML tags.
• The tags in the example above (like <to> and <from>) are not
defined in any XML standard. These tags are "invented" by the
author of the XML document.
• HTML works with predefined tags like <p>, <h1>, <table>, etc.
• With XML, the author must define both the tags and the document
structure.
USAGE OF XML
(1) XML is used to improve the production of HTML records for enormous
sites.
(2) XML is utilized for exchange the information between organizations
and systems.
(3) XML is used to offloading and reloading data sets.
(4) XML is used to store and arrange the data, which can customize your
data handling needs.
(5) XML can easily be merged with style sheets to create almost any
desired output.
6) Virtually, any type of data can be expressed as an XML document.
XML SYNTAX
Creating the XML code is very easy and it is strict. It is easy to
understand and easy way to use. So, the software-based
application can easily support the XML.
XML DECLARATION : XML document is starting with XML
declaration.
SYNTAX RULE FOR DECLARATION
 XML document is the case sensitive it is start by specifying
“xml”
 XML document must start first with XML declaration
statement
 An HTTP protocol can override the value of encoding that
you put in the XML declaration
XML

XML DECLARATION -UTF-8 is also the default encoding for HTML5, CSS, JavaScript, PHP, and
SQL.

TAGS & ELEMENT

XML TEXT
Difference between Element and
attribute

In the first example, gender is an attribute. In


the last example, gender is an element. Both
examples provide the same information.
XML DTD

• DTD stands for Document Type Definition.


• A DTD defines the structure and the legal elements and
attributes of an XML document.
• DTD IS CLASSIFIED BY TWO TYPES
1) Internal DTD declaration
2) External DTD declaration
INTERNAL and EXTERNAL DTD
DECLARATION
TYPES OF DBMS ARCHITECTURE
• A database stores critical information and helps access data quickly
and securely. Therefore, selecting the correct Architecture of DBMS
helps in easy and efficient data management.
• Types of DBMS Architecture
1-Tier Architecture
2-Tier Architecture
3-Tier Architecture
3 Tier Architecture
A 3 Tier Architecture in DBMS is the most popular client server architecture in
DBMS in which the development and maintenance of functional processes, logic,
data access, data storage, and user interface is done independently as separate
modules.
Three Tier architecture contains a presentation layer, an application layer, and a
database server.
3-Tier database Architecture design is an extension of the 2-tier client-server
architecture.
A 3-tier architecture has the following layers:
1. Presentation layer (your PC, Tablet, Mobile, etc.)
2. Application layer (server)
3. Database Server
3 Tier Architecture

The goal of Three Tier client-server


architecture is:

 To separate the user applications and


physical database
 To support DBMS characteristics 
Program-data independence
 Supporting multiple views of the data
NORMALIZATION
• Normalization is the process of organizing the data in the database.
• Normalization is used to minimize the redundancy from a relation or
set of relations. It is also used to eliminate the undesirable
characteristics like Insertion, Update and Deletion Anomalies.
• Normalization divides the larger table into the smaller table and links
them using relationship.
• The normal form is used to reduce redundancy from the database
table.
• Normalization: process of efficiently organizing data in the DB.
NORMALIZATION
GOAL
• Eliminate redundant data in a DB, Ensure data dependencies make sense.
• Guidelines for ensuring that DBs are normalized →normal forms: 1NF,
2NF, 3NF, BCNF.
ADVANTAGE OF NORMALIZATION
• A smaller database can be maintained as normalization eliminates the
duplicate data. Overall size of the database is reduced as a result.
DISADVANTAGES OF NORMALIZATION
• More tables to join as by spreading out data into more tables, the need to
join table’s increases and the task becomes more tedious.
• The database becomes harder to realize as well
TYPES OF NORMALIZATION
1NF
2NF
A table is in 2NF if each non-primary key column is fully functionally dependent on the
primary key.

This violates 2NF because the Customer


Name column depends on only part of the
primary key (Customer ID). To normalize
this table to 2NF, we can split it into two
tables.
3NF
3NF builds on 2NF by requiring that each non-primary key column in a table is not
transitively dependent on the primary key. This means that a table should not have
transitive dependencies, where a non-primary key column depends on another non-
primary key column.
Boyce-Codd Normal Form (BCNF)
• BCNF is a stricter form of 3NF that applies to tables with more
than one candidate key. BCNF requires that each non-trivial
dependency in a table is a dependency on a candidate key.

You might also like