biscicol / triplifier

The triplifier converts Spreadsheets, databases, and Darwin Core Archives into RDF/N3 files suitable for use on the Semantic Web.
1 stars 0 forks source link

Handling Inferred Occurrences in DwC Files #63

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
 The classNoInferredOccurrencesTest method in the dwcValidatorTest file Testw the expression of relationships between classes by looking for "expected" output from the classMeasuringStick model against a model that is created by reading output from the triplifier user interface.  The classMeasuringStick model contains "inferred" occurrences, designated by an uppercase "O" (see the classMeasuringStickOutput.n3 file in the sampledata directory) that indicate no Occurrence was expressed in the model but some other class was that indicates some implied occurrence.  This is a tricky concept.  In some cases occurrences certainly be implied (such as data expressing only an Identification & a Taxon) and in other cases may not be suitable at all (such as data expressing only a Taxon).  In any case, for the purposes of the  tests run in the class, we ignore any supposed "inferred" Occurrence relationships.

The purpose of this issue to raise this issue for tracking and discussion 
regarding how to handle these cases.  Approaching this issue should be done 
first by determining how many darwin core archives fall under these categories. 
 Are these "fringe" issues or "central"?

Original issue reported on code.google.com by jdec...@gmail.com on 3 Mar 2014 at 5:21