1.
Making a taxonomy work for the organisation Liddy Nevile Sunrise Research Laboratory/La Trobe University

2.
Making a functional taxonomy <ul><li>The role of a taxonomy is not limited to discovery within the realm of the creator of the digital library. </li></ul><ul><li>What is necessary for a good taxonomy to work inside and outside the organisation, for the organisation? </li></ul>

3.
<ul><li>How interoperable are the organisation’s resources? </li></ul><ul><li>How do outsiders access and contribute to the organisation’s knowledge base? </li></ul><ul><li>Does the individual user get access to what they need to use the resource? </li></ul>Three interoperability problems

4.
<ul><li>Opening the silos across the organisation </li></ul><ul><li>Integrating external and internal resources for external and internal use </li></ul><ul><li>Considering the individual so that everyone gets access to the resources </li></ul>Three dimensions to the problem

5.
Three case studies <ul><li>Victorian government ‘silos’ </li></ul><ul><li>Quinkan Rock Art </li></ul><ul><li>AccessforAll considerations - TILE </li></ul>

6.
Interoperability <ul><li>Structure </li></ul><ul><li>Syntax </li></ul><ul><li>Semantics </li></ul><ul><li>(system conformance) </li></ul>

7.
1. Working across the silos <ul><li>Making Inter-operability Visible </li></ul><ul><ul><li>Visualising Interoperability: ARH, Aggregation, Rationalisation and Harmonisation </li></ul></ul><ul><ul><li>With Michael Currie, Meigan Geileskey, Richard Woodman </li></ul></ul><ul><li>Project of Victorian Department of Premier & Cabinet </li></ul><ul><li>http://www.bncf.net/dc2002/program/ft/paper21.pdf </li></ul>

8.
1. Working across the silos <ul><li>3 government departments all using the same AGLS schema </li></ul><ul><li>Differences in purpose - one makes brochure-ware, one records critical info, one does broad-based research, …. </li></ul><ul><li>All have document m’ment systems </li></ul><ul><li>All docs must be discoverable </li></ul>

9.
Process <ul><li>Aggregate - </li></ul><ul><ul><li>List all elements and values currently used - is there a significant difference? </li></ul></ul>

11.
Process <ul><li>Aggregate </li></ul><ul><li>Harmonise </li></ul><ul><ul><li>Look at the list of elements and decide which have material differences </li></ul></ul><ul><li>**Remembering that each agency values all its metadata content </li></ul>

12.
Harmonise trivial differences <ul><li>Mis-use of available elements, qualifiers etc </li></ul><ul><li>Different expression of the same type of information </li></ul><ul><li>Different granularity </li></ul><ul><li>Different element name for the same information, … </li></ul><ul><li>-> need to rationalise </li></ul>

13.
<ul><li>Element names </li></ul><ul><ul><li>Inconsistent case eg. DC.Title/TITLE/title EDNA.Userlevel/UserLevel </li></ul></ul><ul><ul><li>Non-standard names eg. DC.Keywords </li></ul></ul><ul><ul><li>Non-standard qualifiers eg. DC.Description.Abstract </li></ul></ul><ul><ul><li>Non-standard abbreviations eg. DC.Lang </li></ul></ul><ul><li>Fields </li></ul><ul><ul><li>Standard and non-standard element names </li></ul></ul><ul><ul><ul><li>eg. 'description' and DC.Description and Custodian </li></ul></ul></ul>Rationalise

14.
<ul><li>Values </li></ul><ul><li>(Despite DCMES recommendations …) </li></ul><ul><ul><li>DC.Identifier: </li></ul></ul><ul><ul><ul><li>other id numbers without qualifiers. </li></ul></ul></ul><ul><ul><li>DC.Date: </li></ul></ul><ul><ul><ul><li>also used yyyy, yyyy/m/d, yyyy-dd-mm </li></ul></ul></ul><ul><ul><li>DC.Format: </li></ul></ul><ul><ul><ul><li>Non-standard terms eg. VHS (PAL) </li></ul></ul></ul><ul><ul><ul><li>Incorrect case eg. text/HTML </li></ul></ul></ul>Rationalise

15.
<ul><li>DC.Language: also used en, en-au, en-AU </li></ul><ul><li>Qualifiers embedded in values: </li></ul><ul><ul><li>DC.Publisher CONTENT=&quot;corporateName=State...&quot; </li></ul></ul><ul><li>Non-standard proper names </li></ul><ul><ul><li>DPC for Department of Premier and Cabinet </li></ul></ul><ul><li>->Generally inconsistent use of capitalisation and punctuation </li></ul>Rationalise

16.
Discoveries <ul><li>Main problems were to do with incompatibility of syntax and semantics although both were well described in documentation and looked very simple. </li></ul>

17.
Outcomes <ul><li>Minimal interference </li></ul><ul><li>Visualisation of differences/incompatibility </li></ul><ul><li>Support for local specification and global interoperability </li></ul><ul><li>Base for a single system to satisfy many purposes using ARH approach </li></ul>

18.
2. Repatriation of Quinkan Culture <ul><li>with Eric Wainwright (Team Leader), Sophie Lissonnet (metadata) and others </li></ul><ul><li>An ARC funded LINK Project </li></ul><ul><li>Full report - http://eprints.jcu.edu.au/1135/ </li></ul><ul><li>Int. J. of Metadata, Semantics and Ontologies (IJMSO) ISSN Vol 1 No 3. (Online): 1744-263X - ISSN (Print): 1744-2621 </li></ul>

19.
Quinkan Country Images from the Laura Booklet published by the Ang-gnarra Corporation

20.
Quinkan Culture <ul><li>People were here 36,000 years ago </li></ul><ul><li>The community has been ravaged in the last 200 years and so has the culture </li></ul><ul><li>60 people remain </li></ul><ul><li>290 km from the nearest city </li></ul><ul><li>with 100,000 Rock Art paintings in excellent condition. </li></ul>

21.
Repatriation of resources <ul><li>The problem - seamless import and export of descriptions to offer a single portal </li></ul><ul><li>People moving out of country stay connected and those in country can learn from those out of country </li></ul><ul><li>Multiple voices for multiple audiences </li></ul>

22.
Dublin Core - qualified <ul><li>A standard form of description with rule-based extensions </li></ul><ul><ul><li>Locally specific - globally interoperable </li></ul></ul><ul><li>Standard mappings from other standards </li></ul><ul><li>Enabling functions on the classifications for better discovery </li></ul><ul><ul><li>Annotations </li></ul></ul><ul><ul><li>Semantic Web applications </li></ul></ul>

23.
Semantic Web applications Tommy George inspecting red rock ochre. &quot;A lot of paintings are made in red.&quot;

24.
Annotation Services <ul><li>W3C annotation server (Annotea) </li></ul><ul><li>Uses W3C standards and technologies </li></ul><ul><li>Uses RDF metadata framework </li></ul><ul><li>User accessible </li></ul><ul><li>Create, store, edit and delete annotations </li></ul>server Annotea

25.
Annotation Servers text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text Annotates Original Resource User/Author text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text

26.
3. Access For All <ul><li>By law in Australia, all public resources to be available to all equally ie do not discriminate against those who cannot access text, or sounds, or visuals. </li></ul>

27.
How do we know what he needs?

28.
Accessibility (M’soft) <ul><li>60% working adults in the US - esp. many who are not self-identifying </li></ul><ul><li>?% people using alternative devices, eg phones? </li></ul>

29.
Accessibility metadata <ul><li>Even if resources are accessibility standards conformant, those that suit an individual user are: </li></ul><ul><ul><li>not necessarily accessible to her </li></ul></ul><ul><ul><li>not discoverable if they are accessible </li></ul></ul>

30.
Accessibility accommodations <ul><li>By lowest common denominator? </li></ul><ul><ul><li>W3C WAI standards </li></ul></ul><ul><li>By presumed audience? </li></ul><ul><ul><li>Guess work by site developer </li></ul></ul><ul><li>By individual user? </li></ul><ul><ul><li>AccessForAll ISO standards </li></ul></ul>

31.
TILE <ul><li>E-learning environment that enables learner-centric transformation of learning content and delivery </li></ul><ul><ul><ul><li>Authoring support for transformable content and Metadata </li></ul></ul></ul><ul><ul><ul><li>Browser </li></ul></ul></ul><ul><ul><ul><li>Learning Object Repository </li></ul></ul></ul><ul><ul><ul><li>Learner Preference System </li></ul></ul></ul>

40.
Accessibility metadata <ul><li>Metadata to describe needs and preferences of user </li></ul><ul><li>Metadata to describe accessibility characteristics of resources </li></ul><ul><li>Accessibility service to match resources to needs and preferences </li></ul>

41.
Problems for interoperability <ul><li>Syntax </li></ul><ul><li>Semantics </li></ul><ul><li>Structure </li></ul>

42.
Structural incompatibilities user achievements aspirations VCE medicine opportunities engineering UNI TAFE Apprentice <ul><li>identity </li></ul><ul><li>achievements </li></ul><ul><li>aspirations </li></ul><ul><li>opportunities </li></ul><ul><li>… </li></ul>Hierarchical vs ‘flat’ Five : Three

43.
Compatible structures

44.
Compatible grammars Compatible grammars ( http://www. dlib .org/dlib/october00/baker/10baker.html )

45.
Standards conformance <ul><li>Clearly defined requirements for local specificity, global interoperability </li></ul><ul><li>Clearly stated standards for structure, syntax and semantics (functional abstract model) </li></ul><ul><li>Process-integrated metadata creation and editing </li></ul><ul><li>Organisational conformance evaluation </li></ul>

46.
Thank you.

47.
title