Prepared for:

MR. NOR EZAN BIN OMAR

Prepared By:
MOHD SYUZAIRI BIN SHAHRIR 2007139483
NUR HAYATUL SYIMA BT HANIFAH 2007113963
MOHD LUTFI BT YUNOS 2007113913
NORASFAHANA BT JAMIL 2007113909
UMMI KALTHUM BT MOHD TAMRINAN 2007113997
NUR SYAHIRAH BT BASIRON 2007113983
The Dublin Core standard is a simple yet effective element
set for describing a wide range of networked resources. The
Dublin Core standard includes two levels: Simple and
Qualified. Simple Dublin Core comprises fifteen elements;
Qualified Dublin Core includes three additional elements
(Audience, Provenance and Rights Holder)

Another way to look at Dublin Core is as a "small language

for making a particular class of statements about resources".

In the diverse world of the Internet, Dublin Core can be seen

as a "metadata pidgin for digital tourists": easily grasped, but
not necessarily up to the task of expressing complex
relationships or concepts.
 Dublin Core principles

1.The One-to-One Principle.

-In general Dublin Core metadata describes one
manifestation or version of a resource, rather than
assuming that manifestations stand in for one another

2.The Dumb-down Principle.

-The qualification of Dublin Core properties is guided
by a rule known colloquially as the Dumb-Down
Principle

3.Appropriate values.
-This may impose certain constraints on how metadata
is constructed, but the requirement of usefulness for
discovery should be kept in mind.
The "Dublin" in the name refers to Dublin, Ohio, U.S., where
the work originated from an invitational workshop (the
"OCLC/NCSA Metadata Workshop") hosted in 1995 by
OCLC, a library consortium that is based there. (NCSA is the
National Center for Supercomputing Applications.)

The "Core" refers to the fact that the metadata element set is
a basic but expandable "core" list.
1.Simplicity of creation and maintenance
-has been kept as small & simple as possible to allow
non-specialist to create simple description records.

2. Commonly understood semantics

-can help the digitals tourist, a non specialist searcher. Find his
or her way by supporting a common set of elements, the
semantic of which are university understood & support.
3. International scope
-Develop in English, but version are being created in many
other language including Thai, Japanese, French, Greek,
Indonesia ,etc.

4. Extensibility
-Core developers have recognized the importance of
providing a mechanism for extending the DC element set
for additional resource discovery needs
The Dublin Core standard includes two levels: Simple and Qualified.

1. Simple Dublin Core

-The Simple Dublin Core Metadata Element Set (DCMES) consists
of 15 metadata elements:

1.Title 9. Format
2.Creator 10. Identifier
3.Subject 11. Coverage
4.Description 12. Relation
5.Publisher 13. Sources
6.Contributor 14. Language
7.Right 15. Relation
8.Type
2. Qualified Dublin Core

includes a set of recommended encoding schemes,

designed to aid in the interpretation of an element value.

These schemes include controlled vocabularies and formal

notations or parsing rules.

Audience, Provenance and RightsHolder are elements,

but not part of the Simple Dublin Core fifteen elements. Use
Audience, Provenance and RightsHolder only when using
Qualified Dublin Core.
 HTML, DUBLIN CORE, and
NON - DUBLIN CORE METADATA

• There are two such formats that usually use to make

Dublin Core;

1. Hypertext Markup Language (HTML)

2. Extensible Markup Language (XML)

• Non-Dublin Core Element;

-such as Email from the A-Core
<meta name = "DC.Creator"
content = "Da Costa, Jos&eacute;">
<meta name = "AC.Email"
content =
"dacostaj@peoplesmail.org">
THE META TAG

• The META tag of HTML is designed to encode a named

Dublin Core and other metadata element.

• For example;

<meta name = "DC.Creator"

content = "Simpson, Homer">

<meta name = "PREFIX.ELEMENT_NAME"

content = "ELEMENT_VALUE">

ELEMENT NAME was: Creator

ELEMENT VALUE was: Simpson, Homerand
PREFIX was : DC
THE LINK TAG
• The LINK tag of HTML may be used to associate an
element name prefix with the reference definition of the
element set that it identifies.

•For example;

<link rel = "schema.DC"

href = "http://purl.org/DC/elements/1.0/">
<link rel = "schema.AC“
href = "http://metadata.net/ac/2.0/">

<link rel = "schema.PREFIX“

href = "LOCATION_OF_DEFINITION ">

<html>
<head>
<title> A Dirge </title>
<link rel = "schema.DC"
href = "http://purl.org/DC/elements/1.0/">
<meta name = "DC.Title"
content = "A Dirge">
<meta name = "DC.Creator"
content = "Shelley, Percy Bysshe">
</head>
<body>
</body>
</html>
1.Created in order to have an internationally agreed-upon set of the elements
that could be filled in by the creator of an electronic document

2.DC is now being implemented through the use of HTML

3.The DC Set consists of 15 elements that can be divided into 3 main groups

4.Developing and maintaining international standards for describing resources

or materials

5.Supporting the whole community of users and developments in finding

resources

6.Promoting the use of Dublin Core solutions to the world

7.Making guidelines and procedures to help implementers define and describe

their usage of Dublin Core Metadata
3 main groups:

 Content of resource

 Title
• The name given to the resource by the CREATOR or PUBLISHER.
• <meta name = "DC.Title"
content = "Polycyclic aromatic hydrocarbon
contamination">

Subject and keywords

• The topic of the resource, or keywords or phrases that describe the
subject or content of the resource.
• <meta name = "DC.Subject"
content = "vietnam war">
<meta name = "DC.Subject"
scheme = "LCSH"
content = "Vietnamese Conflict, 1961-1975">
  Description
• A textual description of the content of the resource, including abstracts in the case
of document-like objects or content descriptions in the case of visual resources.
• <meta name = "DC.Description“
lang = "en"
content = "The Author gives some Account of Himself
and Family
-- His First Inducements to Travel -- He is
Shipwrecked, and Swims for his Life -- Gets safe on
Shore in the Country of Lilliput -- Is made a Prisoner, and carried up the Country">

 Source
• The work, either print or electronic, from which this resource is derived, if applicable
• <meta name = "DC.Source"
content = "Shakespeare's Romeo and Juliet">
 Language
• Language of the intellectual content of the resource
• <meta name = "DC.Language"
scheme = "rfc1766"
content = "en-US">

 Relation
• Relationship to other resources
• <meta name = "DC.Relation.IsPartOf" content =
"http://foo.bar.org/abc/proceedings/1998/">

 Coverage
• The spatial locations and temporal duration’s characteristic of the resource
• <meta name = "DC.Coverage"
scheme = "TGN"
content = "Columbus (C,V)">
 Intellectual properties

 Author/ Creator
• The person(s) or organization(s) primarily responsible for the
intellectual content of the resource
• <meta name = "DC.Creator"
content = "Gogh, Vincent van">
<meta name = "DC.Creator"
content = "van Gogh, Vincent">

 Publisher
• The agent or agency responsible for making the object available
• <meta name = "DC.Publisher"
content = "University of California Press">
 Other contributor
• The person(s), such as editors and transcribers, who have made other significant
intellectual contributions to the work
• <meta name = "DC.Contributor.Photographer"
content = "Adams, Ansel">

Right elements
• intended to be a link (a URL or other suitable URL as appropriate) to a copyright notice,
a rights-management statement
• <meta name = "DC.Rights"
lang = "en"
content = "Copyright Acme 1999 - All rights reserved.">
<meta name = "DC.Rights"
content = "http://foo.bar.org/cgi-bin/terms">
Resource as an instance
 Date
• The date of publication
• <meta name = "DC.Date"
content = "1972">
 Resource Type
• The genre of the object, such as novel, poem, or dictionary
• <meta name = "DC.Type"
content = "poem">
 Format
• The data representation of the object, such as Postscript file or Windows executable
file
• <meta name = "DC.Format"
content = "video/mpeg; 14 minutes">

 Resource identifier
• String or number used to uniquely identify the object
• <meta name = "DC.Identifier"
scheme = "ISBN"
content = "1-56592-149-6">
Advantages of Dublin core
1.Commonly understood semantics.

2.Easy to find and describing things online and digital

material such as video, sound, image, text, and composite
media like web pages.

3.Providing for effective retrieval of those resources in the

networked environment.

4.Dublin core is the emerging international and standard for

Web-based resources description.

5.Personalize and customize the user experience

6.They are simpler to update and display and are easier to
use for many simple look-up task.

7.Dublin core can readily be represented in HTML and in

XML.

8.Better information means better decisions

9.Target information for the task at hand

10.Connect people with information efficiently

11.Make information available across the enterprise

12.Promote re-use of existing content

 CONCLUSION
In conclusion, Dublin Core is a standard that can
make the work become easier and it help the
users to understand the information that they need
in Web page. The Dublin Core also makes
everyone in the world can understand the
language in Web page because the provenances
of Dublin Core have built up the version of Dublin
Core in many languages.