|
1
|
- Access to Biological Collection Data
- Content Definition
TDWG Annual Meeting 2004, Walter G. Berendsohn, ABCD subgroup
convenor, 10 Nov. 2004
|
|
2
|
- Introduction (design principles)
- What happened since Oeiras?
- Structure of ABCD
- Mandatory/Recommended elements
- Datasets – Dataset – Unit
- Metadata, IDs
- Standard process, publication, revisions
|
|
3
|
- www.bgbm.org/TDWG/CODATA/Schema/
- Purpose of ABCD
- Origin and Evolution of ABCD
- Design principles
- Mapping existing data definitions and standards (e.g. Darwin Core,
HISPID, OECDE-MDS, EURISCO)
|
|
4
|
- A common data specification for biological collection units
- primary occurrence data
- living and preserved specimens
as well as field observations
- Intended to provide semantic definitions
- Intended to support the exchange and integration of detailed primary
data
|
|
5
|
- Support multiple special interest networks within a single architecture
- Current research questions go beyond simple taxonomic / geographic
priorities
- Applied research: interactions, pathogens,
- Research stipulated by data access: unknown questions
|
|
6
|
- Unit-level collection standard is community effort since 1990
- Based on Standards, Information models, Implemented databases, .....
- CODATA (Committee on Data for Science and Technology) support since 2001
- Recent contributors on Website
|
|
7
|
- Full coverage for unit-level collection data; generalise what’s in
common
- not for full taxonomic or nomenclatural data
- not for structured descriptive data
- not for collection-level “meta”data
- Polymorphism (variable atomisation)
- be inclusive, allow to connect less structured data sources
|
|
8
|
- Extendibility
- slots for standardised community-specific data items
- slot for interim extensions
- Flexible containers
- element-element or element-attribute couples for category-value pairs
allow freely defined and repeatable data fields (e.g., higher taxa,
measurements, morphological features)
|
|
9
|
- Typing
- building blocks for community standards
- Avoid referencing
- single hierarchy (current protocols)
- future version must support multiple object types and referencing
- No recursive structures
- programmers need some sleep, too
|
|
10
|
- Machine-readable annotations
- provide documentation of the schema
- can be used in the mapping process
(semantic search by configuration assistant)
- Language support
- language attribute where appropriate
- script identification needed?
|
|
11
|
- Support of IPR statements
- provider rights (IPR, ownership, etc.)
- disclaimers
- restrictions for use
- licensing
- Low tech
- biologists must be able to join discussion
|
|
12
|
- ABCD v. 1.2, continued reference implementation using BioCASe Protocol
- Inclusion in GBIF Portal
- Further discussion of content ->v. 1.49e
- Plant genetic resources
- Culture collections
- Metadata
- Documentation
- Standard mappings
- Semantic objects library for biological collections
|
|
13
|
- Driven by European projects (BioCASE, ENBI, SYNTHESYS) and Belgian and
German GBIF National Node projects
- Uses v. 1.2 and 1.48 (culture collections)
- > 4 Mio. records on-line and accessible through GBIF and BioCASE
portals
|
|
14
|
- Datasets
- Dataset
- Set-level metadata
- UDDI, derivation history, IPR, ...
- Unit-data
- Unit-level metadata
- Taxonomic determination and classification
- Collection event and site
|
|
15
|
|
|
16
|
|
|
17
|
- Dataset-level
- ContentContact/Name (UDDI administrative contact)
- TechnicalContact/Name (UDDI)
- Title (DC, short concise title for dataset)
- DateModified (DC, date of creation or last change)
- Unit-level (equivalent to DwC IDs)
- SourceInstitutionID
- SourceID
- UnitID
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
|
|
23
|
|
|
24
|
|
|
25
|
|
|
26
|
|
|
27
|
|
|
28
|
|
|
29
|
|
|
30
|
- Incorporation of further comments
- Consolidation of metadata definitions
- Consolidation of types
- Publication of ABCD version 2 as a proposed standard
- Reference implementations of v. 2
- Vote at St. Petersburg?
|