WG3.1 Object Model and Metadata Session 1
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

WG3.1 Object Model and Metadata Session 1

on

  • 453 views

WG3.1 Object Model and Metadata Session 1

WG3.1 Object Model and Metadata Session 1

Statistics

Views

Total Views
453
Views on SlideShare
453
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

WG3.1 Object Model and Metadata Session 1 Presentation Transcript

  • 1. WG3.1 Object Model and Metadata Work Group Session 1, 2 April 2009
  • 2. Types of objects
    • Real-world physical objects that need to be taken into account include:
      • 3D, printed music, streams, changing objects
      • What about events? Opinions differ
    • NUMERIC project has defined useful list of object types
    • Surrogates for both physical and digital objects (either born-digital or representations of physical objects)
      • in this phase only physical objects that have digital representation
      • in future also physical objects that are not/cannot be digitised
      • but: no library catalogues without links to full text!
    • EAD finding aids may be considered digital objects
  • 3. Granularity, complex objects
    • Statement “Whatever the provider considers appropriate” is not enough for description level
      • Content providers could use guidelines to make overall service more consistent from user perspective
      • But: may be domain-specific and depend on available budget so provider decides in the end; role for domain aggregators?
      • Europeana needs to be flexible in what it accepts
    • Possible approach (DRIVER):
      • Basic level: complex object handled as a single entity
      • Handling as compound entity only if provider provides description according to specific guidelines
      • To be further investigated for specific cases