Understanding Data and Metadata: Types, Examples, and Metadata Standards, Slides of Information Security and Markup Languages

Download Understanding Data and Metadata: Types, Examples, and Metadata Standards and more Slides Information Security and Markup Languages in PDF only on Docsity!

Data and Metadata

Standardisation

Digital Object Types

Type Example

Text

Hypertext

Image

Video

Audio

3D Model

Interactive Visualisation

Software

Example: MIME-Encoded Binary Data

Content-type: multipart/mixed; boundary=“--114782935826962"

-- Content-Disposition: form-data; name="var1"

test

Content-Disposition: form-data; name="var2"; filename="2006 Proposed UCT-CoE Budget.xls" Content-Type: application/vnd.ms-excel

ÐÏࡱá >  þÿ   w  þÿÿÿ þÿÿÿ v ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿ   u'Í ÉÀ  á  °Á  â \ p  Hussein Suleman --114782935826962--

Data vs. Metadata

• Data refers to digital objects that contain

useful information for information seekers.

• Metadata refers to standardised descriptions

of objects, digital or physical.

• Many systems manipulate metadata records,

which contain pointers to the actual data.

• The definition is fuzzy as metadata contains

useful information as well and in some cases

could contain all the data e.g., metadata

describing a person.

Another Metadata Example

• Metadata
  • colour: white
  • title: RG
  • owner: UCT
  • lifetime: 2 months
  • size: 1
  • identifier: RG
  • description: white powdery stick

 Object:

Metadata Comparisons

 Metadata  name: chalk  owner: hussein  colour: white  size: 2.  description: used to write on board  location: honours lecture room  source: Waltons Stationers

 Metadata

 colour: white  title: RG  owner: UCT  lifetime: 2 months  size: 1  identifier: RG  description: white powdery stick

What problems can occur?

Creating Metadata

• Follow metadata guidelines.

• Use terms from controlled vocabularies.

• Avoid duplication of information across fields.

• Use accepted standards for common

elements.

• e.g., ISO 8601 for dates
  • 2005-03-03 instead of 03/03/

• Use XML-based encoding according to

standardised Schema/DTD.

Dublin Core

• Dublin Core is one of the most popular and simplest metadata

formats.

• 15 elements with recommended semantics.
• All elements are optional and repeatable.

Title Creator Subject

Description Publisher Contributor

Date Type Format

Identifier Source Language

Relation Coverage Rights

DC Metadata in XML

Hussein Suleman

Visit to UCT

the view that greets you as you

emerge from the tunnel under the freeway - WOW - and, no, the mountain isnt that close - it just looks that way in 2- D

Hussein Suleman

2002-11-27

image

image/jpeg

DC Metadata in Valid Qualified XML

<oaidc:dc xmlns="http://purl.org/dc/elements/1.1/" xmlns:oaidc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"> Hussein Suleman Visit to UCT the view that greets you as you emerge from the tunnel under the freeway - WOW - and, no, the mountain isnt that close - it just looks that way in 2-D Hussein Suleman 2002-11-27 image image/jpeg http://www.husseinsspace.com/pictures/200230uct/02uct1.jpg en-us http://www.husseinsspace.com unrestricted </oaidc:dc>

What Metadata Format?

• Do NOT just use Dublin Core all the time!

• Every project has its own metadata/data

requirements, therefore most use an internal

format.

• For maximum interoperability,

• Map metadata to most descriptive format for use

by close collaborators.

• Map metadata to DC for use by all and sundry.

• How do we “map” metadata formats? Docsity.com

Metadata Transformation

• Use XML parser to parse data.
• Use SAX/DOM to extract individual elements and generate new format.
• Example (to convert UCT to DC):
  • my $parser = new DOMParser; my $document = $parser->parsefile (‘uct.xml’)->getDocumentElement; foreach my $title ($document->getElementsByTagName (‘title’)) { print “\n”; } foreach my $author ($document->getElementsByTagName (‘author’)) { print “”.$author->getFirstChild->getData.”\n”; } print “UCT\n”; foreach my $version ($document->getElementsByTagName (‘version’)) { foreach my $number ($version->getElementsByTagName (‘number’)) { print “”. $number->getFirstChild->getData.”\n”; } }
• There must be an easier way …

Metadata Transformation (XSLT) 2/

• Ok, but map to what?

Example: RFC

<rfc1807 xmlns="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1807.txt“ xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance“ xsi:schemaLocation="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1807.txt http://www.openarchives.org/OAI/1.1/rfc1807.xsd"> <bib-version >1</bib-version> 395 2007-01-01 University of Cape Town - Department of Computer Science Conference Paper Arnab, Alapan Hutchison, Andrew <other_access >url:http://pubs.cs.uct.ac.za/archive/00000395/</other_access> en Because many current payment systems are poorly implemented, or of incompetence, private data of consumers such as payment details, addresses and their purchase history can be compromised. Furthermore, current payment systems do not offer any non-repudiable verification to a completed transaction, which poses risks to all the parties of the transaction -- the consumer, the merchant and the financial institution. One solution to this problem was SET, but it was never really a success because of its complexity and poor reception from consumers. In this paper, we introduce a third party payment system that aims to preserve privacy by severing the link between their purchase and payment records, while providing a traceable transaction that maintains its integrity and is non-repudiable. Our system also removes much of the responsibilities placed on the merchant with regards to securing sensitive data related to customer payment, thus increasing the potential of small businesses to take part in e-commerce without significant investments in computer security.