156 lines
7.5 KiB
Plaintext
156 lines
7.5 KiB
Plaintext
head 1.4;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.4
|
|
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2005.03.15.05.52.50; author RebeccaShapley; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2005.03.12.09.25.15; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2005.03.09.09.53.10; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@Added topic name via script
|
|
@
|
|
text
|
|
@---+!! %TOPIC%
|
|
|
|
%META:TOPICINFO{author="RebeccaShapley" date="1110865970" format="1.0" version="1.3"}%
|
|
%META:TOPICPARENT{name="WebHome"}%
|
|
At the TDWG meeting 2004 in Christchurch we had presentations of
|
|
* simple "core" standards: <nop>DarwinCore (S. Blum & al.), <nop>LinneanCore (Jerry Cooper), AlexandriaCore (Hagedorn & Cooper), and
|
|
* complex and detailed standards: TCS (J. Kennedy & al.), ABCD (W. Berendsohn & al.), SDD (Hagedorn & al.)
|
|
* UBIF as a framework for a biological object type model (G. Hagedorn & al.), proposing an ID system, simple text labels as lowest possible level of detail, plus core level and detail level. However, the UBIF proposal assumed that always one knowledge domain would be represented in detail (e.g. SDD) and the others would be present only in the form of "proxy objects" or "data interfaces" on the base or core level.
|
|
|
|
It emerged, that a framework and an ontology of biological object types was necessary, and that object types had to be defined at various level of detail. Thus <nop>DarwinCore and ABCD are not different solutions to the same problem, but complementary solutions that are needed in coexistence.
|
|
|
|
At the end of TDWG, Rebecca Shapley presented a vision of how future data sets may be a mosaic of object types and detail of representation (see http://www.tdwg.org/2004meet/EV/TDWG_2004_Papers_Shapley_1.zip). I have slightly reworked her slides and present them below as a background to the discussion of how the future object ontology and data framework might look:
|
|
|
|
<div align="center">
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix01.PNG" alt="DataMatrix01.PNG" width="720" height="540" />
|
|
|
|
Proposal for different level of detail for object representations. To those displayed, additional types should be added intended for markup of existing unstructured text (or low structured mixed content such as xhtml), similar to the <nop>NaturalLanguageDescription markup type in SDD.
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix02.PNG" alt="DataMatrix02.PNG" width="720" height="540" />
|
|
|
|
Matrix formed by level of detail x different object types used in biodiversity informatics (= classes).
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix03.PNG" alt="DataMatrix03.PNG" width="720" height="540" />
|
|
|
|
Examples how the focus of accepted or proposed TDWG standards maps unto the matrix. (##The title of the slide should be renamed from "Identity" to "Inventory" or "Focus of existing work")
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix04.PNG" alt="DataMatrix04.PNG" width="720" height="540" />
|
|
|
|
Examples how the entire <nop>DarwinCore and ABCD might related to the matrix once reformulated as object types.
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix05.PNG" alt="DataMatrix05.PNG" width="720" height="540" />
|
|
|
|
Examples how SDD relates to the matrix (SDD is already formulated through object types).
|
|
|
|
<img src="%ATTACHURLPATH%/DataMatrix06.PNG" alt="DataMatrix06.PNG" width="720" height="540" />
|
|
|
|
Levels of detail should have compatibility so that consumers may prefer to consumer data on a lower level.
|
|
---
|
|
|
|
Related to the above, especially the topic of reformulating complex and core standards as a composition of objects types, four slides from the UBIF talk held in Christchurch 2004. These contain an outline of how existing standards might be modularized by reusing the same object types in various compositions:
|
|
|
|
<img src="%ATTACHURLPATH%/Composition01.PNG" alt="Composition01.PNG" width="720" height="540" />
|
|
|
|
<img src="%ATTACHURLPATH%/Composition02.PNG" alt="Composition02.PNG" width="720" height="540" />
|
|
|
|
<img src="%ATTACHURLPATH%/Composition03.PNG" alt="Composition03.PNG" width="720" height="540" />
|
|
|
|
<img src="%ATTACHURLPATH%/Composition04.PNG" alt="Composition04.PNG" width="720" height="540" />
|
|
|
|
The last image shows the object types proposed in UBIF and how linking mechanism (bottom), a base representation as an unstructured text label in multiple languages (middle) and specialized interfaces (equivalent to the "core" style) might build on each other. For the matrix framework, this vision need to be extended to also layer complex object types on top.
|
|
|
|
</div>
|
|
|
|
An interesting aspect of viewing objects not as a singular reality, but as having multiple representations of different detail, is that the conventional distinction between the object and a reference to an object is blurred. See ObjectTypePattern for further discussion of this.
|
|
|
|
-- Main.GregorHagedorn & Rebecca Shapley - 09 Mar 2005
|
|
|
|
Please add your discussion below. Related topics: ObjectOntology and ObjectIdentifierPattern.
|
|
|
|
---
|
|
|
|
In email, Rebecca Shapley noted on 9 Nov 2004:
|
|
|
|
Perhaps then the columns in the framework are "Conceptual Elements", the cells (at the intersection of a column and a level) are "Concept Object Models", some of which will have colorful names (like <nop>AlexandriaCOM, <nop>LinneanCOM), and the combination of Concept Object Models into TDWG Standards for Data Exchange are Concept Object Compositions (<nop>DwC being an example). The framework/grid itself is a Data Exchange Interface. Interface in the sense that one programs against them.
|
|
|
|
---
|
|
|
|
%META:FILEATTACHMENT{name="DataMatrix01.PNG" attr="h" comment="" date="1110361878" path="C:\Data\Temp\DataMatrix01.PNG" size="18367" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="DataMatrix02.PNG" attr="h" comment="" date="1110361896" path="C:\Data\Temp\DataMatrix02.PNG" size="7215" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="DataMatrix03.PNG" attr="h" comment="" date="1110361912" path="C:\Data\Temp\DataMatrix03.PNG" size="10601" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="DataMatrix04.PNG" attr="h" comment="" date="1110361925" path="C:\Data\Temp\DataMatrix04.PNG" size="32495" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="DataMatrix05.PNG" attr="h" comment="" date="1110361939" path="C:\Data\Temp\DataMatrix05.PNG" size="17752" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="DataMatrix06.PNG" attr="h" comment="" date="1110361953" path="C:\Data\Temp\DataMatrix06.PNG" size="25049" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="Composition01.PNG" attr="h" comment="" date="1110361971" path="C:\Data\Temp\Composition01.PNG" size="11345" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="Composition02.PNG" attr="h" comment="" date="1110361984" path="C:\Data\Temp\Composition02.PNG" size="10755" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="Composition03.PNG" attr="h" comment="" date="1110361998" path="C:\Data\Temp\Composition03.PNG" size="61963" user="GregorHagedorn" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="Composition04.PNG" attr="h" comment="" date="1110362011" path="C:\Data\Temp\Composition04.PNG" size="22950" user="GregorHagedorn" version="1.1"}%
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1110619515" format="1.0" version="1.2"}%
|
|
d55 1
|
|
a55 1
|
|
-- Main.GregorHagedorn - 09 Mar 2005
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1110361990" format="1.0" version="1.1"}%
|
|
d24 1
|
|
a24 1
|
|
Examples how the focus of accepted or proposed TDWG standards maps unto the matrix.
|
|
d53 2
|
|
@
|