A prototype execution platform was implemented. This used the Java Jena API to instantiate the ontology classes. This occurred as VSV-G tag result of a string comparison between the value read from the data-store and a class in the FVB or OBD application ontologies (via the respective mappings). Instantiation occurred in two steps, first using information specific to the data-store (Fig. 6, step 1a or 1b) and then using generally accepted knowledge (Fig. 6, step 2a or 2b or 2c). Step 1b occurred in the case of AM data-store records of species of known flower-visiting groups that had an observation date but no observer name (in step 1b the FV:PlantAssociationEvent class is always instantiated). In Fig. 6 the class that is instantiated is the most generalized class that can be instantiated using the mapping (FVB mapping) or ontology (FV, KFG or RBH ontology) that is shown. For example, after step 1a more-detailed behavioral information may result in the instantiation of the FV:FlowerPollenCollectingEvent class.
↧