240 likes | 358 Views
Main aspects of SPM & TDGW Architecture. Species Profile Model - SPM. Aims of SPM Retrieval, integration and harvesting of species data (e.g. mash up website) General model; as simple as possible extendible Based on RDF
E N D
Species Profile Model - SPM Aims of SPM • Retrieval, integration and harvesting of species data (e.g. mash up website) • General model; as simple as possible • extendible • Based on RDF • Use existing TDWG standards wherever possible ( e.g. TCS for taxon concepts ) Devised in April 2007 at GBIF Workshop in Copenhagen
spm:SpeciesProfileModel tc:TaxonConcept spm:InfoItem SPM – Basic Structure Core Structure of the SPM spm:aboutTaxon spm:hasInformation • aboutTaxon: TCS based • hasInformation -> InfoItem (multiple occurrences) • InfoItems contain the data on the Species
SPM v0.1 InfoItem Properties • More than one category Properties per InfoItem possible • “free tagging” of category with terms provided by controlled vocabularies.
SPM v0.1 – Free Tagging A basic Vocabulary: SPMTerms: Evolution, Behaviour, Habitat, … hasInformation InfoItem category SPM Behaviour hasContent “Some stuff about behaviour”
SPM v0.1 – Free Tagging • Allows naive implementations • Avoid long term process of finding consensus on categories A basic Vocabulary: SPMTerms: Evolution, Behaviour, Habitat, … hasInformation InfoItem category SPM Behaviour hasContent “Some stuff about evolution of behaviour” Evolution
TDWG Architecture TAPIR is a core technology of the TDWG Architecture
TAPIR Concept Mapping • TAPIR needs to map schema concepts to configure • Output Models for TAPIR search requests • Database mapping for TAPIR data source configuration • Concepts are defined as XPaths to instance elements
Mapping SMP v.0.1 Concepts XML serialization of a SPM RDF instance <spm:SpeciesProfileModel> <spm:hasInformation> <spm:InfoItem> <spm:category rdf:resource=“..”>...</spm:category> <spm:hasContent>...</spm:hasContent> </spm:InfoItem> </ ... 2 concepts to map to: spm:SpeciesProfileModel/spm:hasInformation/\ spm:InfoItem/spm:hasContent spm:SpeciesProfileModel/spm:hasInformation/\ spm:InfoItem/spm:category@rdf:resource
Consequences of Free Tagging for TAPIR Clients • Capability responses would only list 2 concepts InfoItems: category & hasContent => Additional inventory or search request needed to inspect the categories of data available. • Only very limited output models
Consequences of Free Tagging for TAPIR Data Providers Most data providers have relational databases as source. spm:category spm:hasContent ‘Super’ View Relational DB Structure TAPIR Concepts
Solution in SPM v0.2 category property removed & InfoItem
Solution in SPM v0.2 category property removed & sub classing of InfoItems: Biology Evolution InfoItem Behavior Habitat => All elements can be mapped by their individual names spm:SpeciesProfileModel/spm:hasInformation/spm:Behaviour spm:SpeciesProfileModel/spm:hasInformation/spm:Habitat
Subclassing in SPM v0.2 Biology Evolution NutritionalBehaviour InfoItem ReproductionalBehaviour Behavior BehaviouralEvolution Habitat • Semantic hierarchy • stronger semantics • semantics can easily be inferred
Examples hasInformation BehaviouralEvolution SPM hasContent “Some stuff about evolution of behaviour”
The contextValue Property contextValue: Terms defined by a controlled vocabulary
Examples hasInformation Behaviour SPM contextValue Evolution hasContent “Some stuff about evolution of behaviour”
Examples hasInformation Evolution SPM contextValue Behaviour hasContent “Some stuff about evolution of behaviour”
Examples hasInformation InfoItem SPM contextValue Behaviour hasContent “Some stuff about evolution of behaviour” Evolution SPM v0.1 like notation still possible
Multiple ways to express the same thing! • Consequences for TDWG Architecture? • Best practices ?
Ambiguous Expressions hasInformation Behaviour SPM contextValue Winter hasContent “Sleeps” LowTemperature