Você está na página 1de 38

UNIVERSITI TEKNOLOGI MARA

Diploma In Information Management


IMD253: Organization Of Information

Dublin Core
Prepared by
AHMAD NAIM BIN MUZAMMIL 2007113907
MOHD AZRI BIN MISNAN
2007113965
FATIN NAZARIAH BT MOHD RADZALI
2006211798 Dublin
SALINA BT MAT SALIM 2006152929
Core
Prepared for
EN NOR EZAN BIN OMAR

Date of presentation
12 OCTOBER 2009
Introduction

Presented by:
SALINA BT MAT SALIM Dublin
Core
Introduction
• Dublin is referring to Dublin, Ohio, US.
• the work originated from an invitational workshop
(the "OCLC/NCSA Metadata Workshop") hosted in
1995 by Online Computer Library Center
• The "Core" refers to the fact that the metadata
element set is a basic but expandable "core" list.
• The semantics of Dublin Core were established and
are maintained by an international, cross-disciplinary
group of professionals from librarianship, computer
science, text encoding, museums, and other related
fields of scholarship and practice.

Presented SALINA BT MAT SALIM


Introduction
• Dublin Core Metadata Element Set is a suite of
semantic definitions of 15 descriptive elements,
specifically intended to support electronic resource
discovery.
• Dublin Core does not impose a controlled vocabulary.
Instead it specifies that descriptive information about
the content or other attributes of the entity being
described - eg its author, language and date of
creation - can appear in particular fields (the
'elements') in a particular format
• Different methods can be used to record or transfer
the metadata, including HTML, XML, RDF and
relational databases.
Presented SALINA BT MAT SALIM
Using Dublin
Core
- Simple Dublin Core

Dublin
Presented by: Core
AHMAD NAIM BIN MUZAMMIL
Using Dublin Core
- Simple Dublin Core
Simple Dublin Core
Core Comprises 15 elements that can divide to 3 main group;
content of resources, intellectual property, resource as an instance.

content of Intellectual Resources as an


resources property instance
-Title -Author/creator -Date
-Subject and -Publisher -Resource type
keywords -Others contributor -Format
-Description -Right element -Resource identifier
-Source
-Language
-Relation
-Coverage

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Content of resource
1. Title
• The name given to the resource
• Example
Title="How to Make Pastry"

2. Subject and keywords


• The topic of the content of the resource. Subject will be
expressed as keywords or key phrases or classification
codes that describe the topic of the resource.
• Example
Subject="Aircraft leasing and renting"

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Content of resource
3. Description
• Description may include but is not limited to: an abstract, table
of contents, reference to a graphical representation of content
or a free-text account of the content.
• Example
Description="Illustrated guide to airport markings and lighting
signals, with particular reference to SMGCS (Surface Movement
Guidance and Control System) for airports with low visibility
conditions."

4. Source
• A Reference to a resource from which the present resource is
derived.
• Example
Source="Image from page 54 of the 1922 edition of Romeo and
Juliet"
Presented AHMAD NAIM BIN MUZAMMIL
Using Dublin Core
- Simple Dublin Core
Content of resource
5. Language
• A language of the intellectual content of the resource.
Defines two- and three-letter primary language tags with
optional subtags. Examples include "en" or "eng" for
English, "akk" for Akkadian, and "en-GB" for English used in
the United Kingdom.
• Example
Language="en"

6. Relation
• A reference to a related resource.
• Example
Title="Dead Ringer"
Relation="Gemstar e-book"
[Relationship described is requires]
Presented AHMAD NAIM BIN MUZAMMIL
Using Dublin Core
- Simple Dublin Core
Content of resource
7. Coverage
• The extent or scope of the content of the resource.
Coverage will typically like a place name or
geographic co-ordinates, time range.
• Example
Coverage="1995-1996"
Coverage="Boston, MA"
Coverage="17th century"
Coverage="Upstate New York"

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Intellectual property
8. Author/creator
• An entity primarily responsible for making the content of the
resource. It’s include a person, an organization, or a service.
• Example
Creator="Shakespeare, William"
Creator="Wen Lee"
Creator="Hubble Telescope"
Creator="Internal Revenue Service. Customer Complaints Unit"
 
9. Publisher
• The entity responsible for making the resource available. Examples
of a Publisher include a person, an organization, or a service.
• Example
Publisher="University of South Where"
Publisher="Funky Websites, Inc."
Publisher="Carmen Miranda"

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Intellectual property
10. Others contributor
• An entity responsible for making contributions to the content of the resource.
Examples of a Contributor include a person, an organization or a service.
Typically, the name of a Contributor should be used to indicate the entity.

11. Right element


• Information about rights held in and over the resource. Rights element will
contain a rights management statement for the resource, or reference a
service providing such information. Rights information often encompasses
Intellectual Property Rights (IPR), Copyright, and various Property Rights. If
the rights element is absent, no assumptions can be made about the status
of these and other rights with respect to the resource.
• Example
Rights="Access limited to members"
Rights="http://cs-tr.cs.cornell.edu/Dienst/Repository/2.0/Terms& quot;

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Resources as an instance
12. Date
• A date associated with an event in the life cycle of the resource.
Typically, Date will be associated with the creation or availability of
the resource. Recommended best practice for encoding the date
value is defined in a profile of ISO 8601 and follows the YYYY-MM-
DD format.
• Example
Date="1998-02-16"

13. Resource type


• The nature or genre of the content of the resource. Type includes
terms describing general categories, functions, genres, or
aggregation levels for content.
• Example
Type="Image"
Presented AHMAD NAIM BIN MUZAMMIL
Using Dublin Core
- Simple Dublin Core
Resources as an instance
14. Format
• The physical or digital manifestation of the resource. Typically,
Format may include the media-type or dimensions of the
resource. Examples of dimensions include size and duration.
Format may be used to determine the software, hardware or
other equipment needed to display or operate the resource.
• Example
Title="Dublin Core icon"
Identifier="http://purl.org/metadata/dublin_core/images/dc2.gif
& quot;
Type="Image"
Format="image/gif"
Format="4 kB"

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Simple Dublin Core
Resources as an instance
15. Resource identifier
• An unambiguous reference to the resource within a given
context. Recommended best practice is to identify the resource
by means of a string or number conforming to a formal
identification system. Examples of formal identification
systems include the Uniform Resource Identifier (URI)
(including the Uniform Resource Locator (URL), the Digital
Object Identifier (DOI) and the International Standard Book
Number (ISBN).
• Example
Identifier="http://purl.oclc.org/metadata/dublin_core/& quot;
Identifier="ISBN:0385424728"
Identifier="H-A-X 5690B" [publisher number]

Presented AHMAD NAIM BIN MUZAMMIL


Using Dublin Core
- Qualifier Dublin Core
(additional)

Presented by:
FATIN NAZARIAH BT MOHD
Dublin
RADZALI Core
Using Dublin Core
- Qualifier Dublin Core
(additional)
Qualifier Dublin Core
Subsequent to the specification of the original 15
elements, an ongoing process to develop exemplary
terms extending or refining the Dublin Core
Metadata Element Set (DCMES) was begun. The
additional terms were identified, generally in
working groups of the Dublin Core Metadata
Initiative, and judged by the DCMI (Dublin Core
Metadata Initiative) Usage Board to be in
conformance with principles of good practice for the
qualification of Dublin Core metadata elements.

Presented FATIN NAZARIAH BTE MOHD RADZALI


Using Dublin
Core
- Qualifier Dublin Core
(additional)
Qualifier Dublin Core
16. Audience
• A class of entity for whom the resource is intended or useful. A
class of entity may be determined by the creator or the publisher
or by a third party.
• Example
Audience="elementary school students"

17. Provenance
• A statement of any changes in ownership and custody of the
resource since its creation that are significant for its authenticity,
integrity and interpretation. The statement may include a
description of any changes successive custodians made to the
resource.
• Example
Provenance="This copy once owned by Benjamin Spock.”
Presented FATIN NAZARIAH BTE MOHD RADZALI
Using Dublin Core
- Qualifier Dublin Core
(additional)
Qualifier Dublin Core
18. Right holder
• A person or organization owning or managing rights over the resource.
Recommended best practice is to use the URI or name of the Rights Holder
to indicate the entity.
• Example
RightsHolder="Stuart Weibel"

19. Instructional method


• A process, used to engender knowledge, attitudes and skills, that the
resource is designed to support. Instructional Method will typically include
ways of presenting instructional materials or conducting instructional
activities, patterns of learner-to-learner and learner-to-instructor
interactions, and mechanisms by which group and individual levels of
learning are measured.
• Example
InstructionalMethod="Experiential learning"

Presented FATIN NAZARIAH BTE MOHD RADZALI


Using Dublin Core
- Qualifier Dublin Core
(additional)
Qualifier Dublin Core
20. Accrual method
• The method by which items are added to a collection. Recommended best
practice is to use a value from a controlled vocabulary.
• Example
AccrualMethod="Deposit"
 
21. Accrual periodicity
• The frequency with which items are added to a collection. Recommended
best practice is to use a value from a controlled vocabulary.
• Example
AccrualPeriodicity="Annual"

22. Accrual policy


• The policy governing the addition of items to a collection. Recommended
best practice is to use a value from a controlled vocabulary.
• Example
AccrualPolicy="Active"

Presented FATIN NAZARIAH BTE MOHD RADZALI


Encoding
Scheme

Dublin
Presented by: Core
MOHD AZRI BIN MISNAN
Encoding
Scheme
Encoding scheme
• DCMI Period Encoding Scheme: specification of
the limits of a time interval and methods for
encoding this in a text string
• Several methods are available to indicate a time
interval. These include, but are not limited to:
• a name, normally defined in an enumeration such as
a list of artistic, cultural, historical, archaeological,
geological or cosmological eras or periods, a list of
ruler's names, families or dynasties, etc.
• the limits of the interval, using either numeric or
named values, the latter optionally including qualifiers
such as start of, end of, middle of, etc.
Presented MOHD AZRI BIN MISNAN
Encoding
Scheme
Identifying a time interval - the DCMI Period
encoding scheme
Component Definition Default
Label Component
Value
start The instant corresponding to -INF
the commencement of the time
interval
end The instant corresponding to INF
the termination of the time
interval
scheme The encoding used for the W3C-DTF
representation of the time-
instants in the start and end
components
name Presented
A name for the time interval
MOHD AZRI BIN MISNAN
-
Encoding
Scheme
Encoding DCMI Period
The components of a DCMI Period identifier have
no meaning when disaggregated, since in any
particular instance it is the complete set which
indicates the specific time interval. For systems in
which data is encoded using a limited character
set, this is conveniently accomplished by
packaging the components into a single text string
according to the DCSV recommendation [DCSV].

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
Encoding DCMI Period
• A DCMI Point value string using DCSV syntax, and using the
component names defined above, appears as follows:
• east=v1; north=v2; elevation=v3; units=v4; zunits=v5;
projection=v6; name=v7 where v1 - v7 are component values
as defined in the table above.
• Examples
Perth, Western Australia:
name=Perth, W.A.; east=115.85717; north=-31.95301
Bridgnorth, Shropshire, U.K.:
east=372000; north=293000; units=m; projection=U.K.
National Grid
The Greenwich Meridian:
east=0;
The highest point in Australia, illustrating the use of 3-D
coordinates (and how flat Australia is):
east=148.26218; north=-36.45746; elevation=2228; name=Mt.
Kosciusko

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
DCMI Box Encoding Scheme: specification of
the spatial limits of a place, and methods for
encoding this in a text string
• Several methods are available to indicate a place. These include,
but are not limited to:
• a name, normally defined in an identifiable enumeration such as
a gazetteer or list of jurisdictional localities;
• a unique geocode, such as a postal code;
• the coordinates of a point, using geographic values or some
well-defined projection and units;
• a set of arcs or faces describing the polygon or polyhedron
comprising the perimeter of the place;
• the limits of a regular shaped container which encompasses the
place, typically a rectangular box in two or three dimensions,
using geographic values or some well-defined projection and
units.
Presented MOHD AZRI BIN MISNAN
Encoding
Scheme
Identifying a place - the DCMI
Box schemeDefinition
Component Default Component
Label View
northlimit The constant coordinate INF
for the northernmost face
or edge
eastlimit The constant coordinate INF
for the easternmost face
or edge
southlimit The constant coordinate -INF
for the southernmost face
or edge
westlimit The constant coordinate -INF
for the westernmost face
Presented orAZRI
MOHD edge
BIN MISNAN
Encoding
Scheme
Identifying a place - the DCMI
Component Label Definition Default Component
Box scheme View
downlimit The constant coordinate for the -INF
lowermost face or edge
units The units applying to unlabelled signed decimal degrees
numeric values of northlimit,
eastlimit, southlimit, westlimit

zunits The units applying to unlabelled metres


numeric values of uplimit,
downlimit
projection The name of the projection used geographic coordinates
with any parameters required, on Earth for northlimit,
such as ellipsoid parameters, eastlimit, southlimit,
datum, standard parallels and westlimit; height above
meridians, zone, etc mean-sea-level for
Presented MOHD AZRI BIN MISNAN
uplimit, downlimit
Encoding
Scheme
Encoding DCMI Box with DCSV syntax
The components specified above have no meaning
when disaggregated, since in any particular
instance it is the complete set which acts to
indicate the specific location. For systems in which
data is encoded using a limited character set, this
is conveniently accomplished by packaging the
components into a single text string according to
the DCSV syntax [DCSV].

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
Encoding DCMI Box with DCSV syntax
• A DCMI Box value string using DCSV syntax, and using the
component names defined above, appears as follows:
northlimit=v1; eastlimit=v2; southlimit=v3; westlimit=v4;
uplimit=v5;downlimit=v6; units=v7; zunits=v8;
projection=v9; name=v10
where v1 - v10 are component values as defined in the table
above.
• Examples
Western Australia:
name=Western Australia; northlimit=-13.5; southlimit=-
35.5;westlimit=112.5; eastlimit=129
Lake Jindabyne:
northlimit=5980000; westlimit=644000; eastlimit=647000;
southlimit=5966000;units=m; projection=UTM zone 55 south

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
Purpose
Simplicity of creation and maintenance
• The Dublin Core element set has been kept as small and simple as
possible to allow a non-specialist to create simple descriptive records
for information resources easily and inexpensively, while providing for
effective retrieval of those resources in the networked environment.

Commonly understood semantics


• The Dublin Core can help the "digital tourist" -- a non-specialist
searcher -- find his or her way by supporting a common set of
elements, the semantics of which are universally understood and
supported. For example, scientists concerned with locating articles by
a particular author, and art scholars interested in works by a particular
artist, can agree on the importance of a "creator" element.

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
Purpose
International scope
• The Dublin Core Element Set was originally developed in English, but
versions are being created in many other languages, including Finnish,
Norwegian, Thai, Japanese, French, Portuguese, German, Greek, Indonesian,
and Spanish. The DCMI Localization and Internationalization Special Interest
Group is coordinating efforts to link these versions in a distributed registry.

Extensibility
• While balancing the needs for simplicity in describing digital resources with
the need for precise retrieval, Dublin Core developers have recognized the
importance of providing a mechanism for extending the DC element set for
additional resource discovery needs. It is expected that other communities
of metadata experts will create and administer additional metadata sets,
specialized to the needs of their communities.

Presented MOHD AZRI BIN MISNAN


Encoding
Scheme
Function
• There was agreement that an important function of the Dublin Core
might be to provide a locus for the mapping of data elements from
heterogeneous metadata systems, to facilitate interoperability.
• Dublin Core could provide a "window" to specific data resources that
use other descriptive metadata models. Once found, the user would
then query that database in its native form.
• This function of the Dublin Core would approximate that of a directory
of directories serving to get one to a specific location within which
one might search for objects of interest.
• The Dublin Core elements were designed to describe Web documents.
Consequently, they do not distinguish a relationship between object
and source since they pertain to the "item" only as it is represented in
a Web page.

Presented MOHD AZRI BIN MISNAN


Benefits of Dublin
Core

Presented by: Dublin


FATIN NAZARIAH BT MOHD RADZALI
Core
Benefits of
Dublin Core
Benefits
• The metadata in shared environment needs to make sense in a
“bigger” context. It becomes valuable when it comes to
integration of data from various sources. It is thus important
that each of these metadata records is well described.
• To make the information meaningful, we also need to “know”
where the terms are coming from. For example, the used
controlled vocabularies, thesauri etc.
• Uses of minimal rules that are requested by standards and try
to make the records coming from distributed sources as
consistent as is possible.
• Qualified metadata allows the service providers the opportunity
to aggregate and sort information for browsing.

Presented FATIN NAZARIAH BTE MOHD RADZALI


Conclusion

Presented by:
SALINA BT MAT SALIM Dublin
Core
Conclusion
Conclusion
DC has not achieved wide acceptance within the
wider web community. Estimates of sites identified
using DC range from well under 1% to a maximum of
3%; that identification is often restricted to the top
level of sites rather than embracing every digital
object on the particular site. DC is unlikely to
become the global standard for most content on the
internet and intranets. It is however significant as
the 'lingua franca' for the exchange of data and for
cross-database searches of cultural material online.
It may also serve as a building block for construction
of the semantic web.

Presented SALINA BT MAT SALIM


UNIVERSITI TEKNOLOGI MARA
Diploma In Information Management
IMD253: Organization Of Information

Thank You
Dublin
Core

Você também pode gostar