229 lines
12 KiB
Plaintext
229 lines
12 KiB
Plaintext
head 1.8;
|
||
access;
|
||
symbols;
|
||
locks; strict;
|
||
comment @# @;
|
||
|
||
|
||
1.8
|
||
date 2009.11.20.02.02.04; author LeeBelbin; state Exp;
|
||
branches;
|
||
next 1.7;
|
||
|
||
1.7
|
||
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
|
||
branches;
|
||
next 1.6;
|
||
|
||
1.6
|
||
date 2006.05.08.10.22.38; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next 1.5;
|
||
|
||
1.5
|
||
date 2004.07.15.18.22.00; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next 1.4;
|
||
|
||
1.4
|
||
date 2004.06.10.06.25.41; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next 1.3;
|
||
|
||
1.3
|
||
date 2004.06.03.17.58.58; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next 1.2;
|
||
|
||
1.2
|
||
date 2004.05.25.20.53.00; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next 1.1;
|
||
|
||
1.1
|
||
date 2004.05.25.11.58.00; author GregorHagedorn; state Exp;
|
||
branches;
|
||
next ;
|
||
|
||
|
||
desc
|
||
@none
|
||
@
|
||
|
||
|
||
1.8
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@%META:TOPICINFO{author="LeeBelbin" date="1258682524" format="1.1" version="1.8"}%
|
||
%META:TOPICPARENT{name="ObsoleteTopicObsoleteTopicProxyDataModel"}%
|
||
---+!! %TOPIC%
|
||
|
||
This refers to the structure proposed by Jerry Cooper in his first draft of <nop>LinneanCore (a proposed standard for nomenclatorial data). For the sake of the discussion I first reproduce the <nop>SimpleCitation xml schema from Jerry's proposal. Being a first draft and call for discussion the comments below should not be misconstrued as criticism. Instead, I like to reproduce it here to capture the basic approach Jerry is taking, which is slightly different from my modified proposal in UBIF.ProxyDataPublication,
|
||
|
||
<img src="%ATTACHURLPATH%/PublicationProxy_LC1.png" alt="PublicationProxy_LC1.png" />
|
||
|
||
Some minor comments on the proposed structure:
|
||
* <nop>BookTitleEnglish should be a collection of translations, with language indicated as attribute on each translation. I think there is no such thing as a natural "English" book title of a Chinese Book. <nop>RomanTransliteration seems to be inconsistently provided.
|
||
* The title/language/translation would benefit from typifying it. For example, in the series title the language is not expressed, but it is in the other elements.
|
||
* <nop>BookPublicationYear and <nop>ArticlePublicationYear seem to be redundant. I can not imagine how this can differ. A single <nop>PublicationYear/Date should be enough.
|
||
* Also, it is unclear to me why only Articles may have a digital obj. id (= DOI).
|
||
* Edition of book was missing.
|
||
* Journal may better be named periodical, including newspapers and magazines as well as scientific journals. "Periodical" is used e.g. by reference manager.)
|
||
* There is no way yet to express Reprint data, which is especially important for the old taxonomic literature.
|
||
* Technically, the article type enumeration should better be a named enumerated simple type (currently anonymous type). In principle, I wonder however whether it is needed at all. I believe the type can be inferred from the combination of book/series/chapter/periodical/article blocks. Infering a type may be easier than mapping type concepts on each other. In my observation applications like <nop>ReferenceManager(TM), <nop>EndNote(TM) or <nop>ProCite(TM) all have different reference type concepts.
|
||
|
||
To me the flat structure is a case where flat is more confusing than structured. I have tried to moderately restructure Jerry's proposal, take the comments above into account, and compared it with our own <nop>DiversityReferences structure. Please see UBIF.ProxyDataPublication for the modified proposal! Please do critizise the details as well as discuss the fundamental difference of it being slightly more structured - would that already reduce acceptance?
|
||
|
||
* _Note on <nop>DiversityReferences_: This is a relational database model designed to provide simple mapping to <nop>ReferenceManager(TM). An overview over available html and sql documentation can be found at [[http://160.45.63.11/Workbench/References/Model/InformationModels.html][InformationModels]]. A (flat database!) xml schema is also available, see [[http://160.45.63.11/Workbench/References/Model/2003-09-24/DiversityReferencesModel.xsd][DiversityReferencesModel.xsd]]
|
||
|
||
---
|
||
|
||
In his notes for <nop>LinneanCore Jerry says: "Finally, I will make a prediction ... In two years time we will decide that we urgently need a standard for describing literature because that is where all the names come from, and name-uses in the literature form the basis of taxon concepts, and therefore we need a mechanism for sharing <20>literature objects<74>. The data structures for storing literature references in many databases are inadequate and people will have a lot of future work in order to standardise them. However, a standard already exists, MARC, and, although it is based on flat data, at least it atomizes and tags the components logically (and is actually quite easy to re-model into a hierarchical structure). We really do need to think about this now and be encouraging digitizers to treat literature data with respect and not dump it into a string! The <20>SimpleCitation<6F> object in this schema is a MARC subset."
|
||
|
||
I can only endorse this! We should get together now. That means in the coming weeks, before three TDWG standards all including various versions of publication references are submitted to TDWG in beginning August in time for standard endorsement!
|
||
|
||
-- [[Main.GregorHagedorn][Gregor Hagedorn]] - 25 May 2004
|
||
|
||
---
|
||
|
||
%META:FILEATTACHMENT{name="PublicationProxy_LC1.png" attr="h" comment="" date="1085518060" path="C:\Data\Desktop\DESCR\TDWG-SDD\Schema\091\PublicationProxy_LC1.png" size="11472" user="GregorHagedorn" version="1.1"}%
|
||
%META:TOPICMOVED{by="GregorHagedorn" date="1089916034" from="SDD.ProxyDataPublicationNotesOnLinnCoreSimpleCitation" to="UBIF.ProxyDataPublicationNotesOnLinnCoreSimpleCitation"}%
|
||
@
|
||
|
||
|
||
1.7
|
||
log
|
||
@Added topic name via script
|
||
@
|
||
text
|
||
@d1 2
|
||
a4 2
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1147083758" format="1.1" version="1.6"}%
|
||
%META:TOPICPARENT{name="ObsoleteTopicObsoleteTopicProxyDataModel"}%
|
||
@
|
||
|
||
|
||
1.6
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 2
|
||
@
|
||
|
||
|
||
1.5
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 2
|
||
a2 2
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1089915720" format="1.0" version="1.5"}%
|
||
%META:TOPICPARENT{name="UBIF.ProxyDataModel"}%
|
||
d8 8
|
||
a15 8
|
||
* <nop>BookTitleEnglish should be a collection of translations, with language indicated as attribute on each translation. I think there is no such thing as a natural "English" book title of a Chinese Book. <nop>RomanTransliteration seems to be inconsistently provided.
|
||
* The title/language/translation would benefit from typifying it. For example, in the series title the language is not expressed, but it is in the other elements.
|
||
* <nop>BookPublicationYear and <nop>ArticlePublicationYear seem to be redundant. I can not imagine how this can differ. A single <nop>PublicationYear/Date should be enough.
|
||
* Also, it is unclear to me why only Articles may have a digital obj. id (= DOI).
|
||
* Edition of book was missing.
|
||
* Journal may better be named periodical, including newspapers and magazines as well as scientific journals. "Periodical" is used e.g. by reference manager.)
|
||
* There is no way yet to express Reprint data, which is especially important for the old taxonomic literature.
|
||
* Technically, the article type enumeration should better be a named enumerated simple type (currently anonymous type). In principle, I wonder however whether it is needed at all. I believe the type can be inferred from the combination of book/series/chapter/periodical/article blocks. Infering a type may be easier than mapping type concepts on each other. In my observation applications like <nop>ReferenceManager(TM), <nop>EndNote(TM) or <nop>ProCite(TM) all have different reference type concepts.
|
||
d19 1
|
||
a19 1
|
||
* _Note on <nop>DiversityReferences_: This is a relational database model designed to provide simple mapping to <nop>ReferenceManager(TM). An overview over available html and sql documentation can be found at [[http://160.45.63.11/Workbench/References/Model/InformationModels.html][InformationModels]]. A (flat database!) xml schema is also available, see [[http://160.45.63.11/Workbench/References/Model/2003-09-24/DiversityReferencesModel.xsd][DiversityReferencesModel.xsd]]
|
||
@
|
||
|
||
|
||
1.4
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 3
|
||
a3 3
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1086848741" format="1.0" version="1.4"}%
|
||
%META:TOPICPARENT{name="ProxyDataModel"}%
|
||
This refers to the structure proposed by Jerry Cooper in his first draft of <nop>LinneanCore (a proposed standard for nomenclatorial data). For the sake of the discussion I first reproduce the <nop>SimpleCitation xml schema from Jerry's proposal. Being a first draft and call for discussion the comments below should not be misconstrued as criticism. Instead, I like to reproduce it here to capture the basic approach Jerry is taking, which is slightly different from my modified proposal in ProxyDataPublication,
|
||
d17 1
|
||
a17 1
|
||
To me the flat structure is a case where flat is more confusing than structured. I have tried to moderately restructure Jerry's proposal, take the comments above into account, and compared it with our own <nop>DiversityReferences structure. Please see ProxyDataPublication for the modified proposal! Please do critizise the details as well as discuss the fundamental difference of it being slightly more structured - would that already reduce acceptance?
|
||
d32 1
|
||
a32 1
|
||
%META:TOPICMOVED{by="GregorHagedorn" date="1085486367" from="SDD.NotesOnPublicationStructureInLinneanCore" to="SDD.ProxyDataPublicationNotesOnLinnCoreSimpleCitation"}%
|
||
@
|
||
|
||
|
||
1.3
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 1
|
||
a1 1
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1086285538" format="1.0" version="1.3"}%
|
||
d3 1
|
||
a3 1
|
||
This refers to the structure proposed by Jerry Cooper in his first draft of <nop>LinneanCore (a proposed standard for nomenclatorial data). For the sake of the discussion I first reproduce the <nop>SimpleCitation xml schema from Jerry's proposal. Being a first draft and call for discussion the comments below should not be misconstrued as criticism. Instead, I like to reproduce it here to capture the basic approach Jerry is taking, which is slightly different from my modified proposal in ProxyDataPublicationProxy,
|
||
d17 1
|
||
a17 1
|
||
To me the flat structure is a case where flat is more confusing than structured. I have tried to moderately restructure Jerry's proposal, take the comments above into account, and compared it with our own <nop>DiversityReferences structure. Please see ProxyDataPublicationProxy for the modified proposal! Please do critizise the details as well as discuss the fundamental difference of it being slightly more structured - would that already reduce acceptance?
|
||
@
|
||
|
||
|
||
1.2
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 1
|
||
a1 1
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1085518380" format="1.0" version="1.2"}%
|
||
d3 1
|
||
a3 2
|
||
This refers to the structure proposed by Jerry Cooper in his first draft of <nop>LinneanCore (a proposed standard for nomenclatorial data).
|
||
For the sake of the discussion I first reproduce the <nop>SimpleCitation xml schema from Jerry's proposal. Being a first draft and call for discussion the comments below should not be misconstrued as criticism. Instead, I like to reproduce it here to capture the basic approach Jerry is taking, which is slightly different from my modified proposal in ProxyDataPublicationProxy,
|
||
d17 1
|
||
a17 1
|
||
To me the flat structure is a case where flat is more confusing than structured. I have tried to moderately restructure Jerry's proposal, take the comments above into account, and compared it with our own <nop>DiversityReferences structure. Please see also ProxyDataModel as a template to discuss my modified proposal! Please do critizise the details as well as discuss the fundamental difference of it being slightly more structured - would that already reduce acceptance?
|
||
d27 1
|
||
a27 1
|
||
-- Gregor Hagedorn - 25 May 2004
|
||
@
|
||
|
||
|
||
1.1
|
||
log
|
||
@none
|
||
@
|
||
text
|
||
@d1 1
|
||
a1 1
|
||
%META:TOPICINFO{author="GregorHagedorn" date="1085486280" format="1.0" version="1.1"}%
|
||
d3 4
|
||
a6 1
|
||
This refers to the structure proposed by Jerry Cooper in his first draft of <nop>LinneanCore (a proposed standard for nomenclatorial data).
|
||
a8 2
|
||
|
||
* Article type should better be a named enumerated simple type (currently anonymous type).
|
||
d10 1
|
||
d16 1
|
||
d18 1
|
||
a18 1
|
||
In general I find that the super-flat structure to me is a case where flat is significantly more confusing than structured. I have tried to moderately restructure Jerries proposal, take the comments above into account, and compared it with our own <nop>DiversityReferences structure.
|
||
d22 2
|
||
d26 1
|
||
a26 1
|
||
I can only endorse this! We should get together now (that means in the coming weeks, before three TDWG standards all including various versions of publication references are submitted to TDWG in August!)
|
||
d28 1
|
||
a28 1
|
||
Please see also ProxyDataModel!
|
||
d30 3
|
||
a32 1
|
||
-- Gregor Hagedorn - 25 May 2004
|
||
@
|