[Taxacom] Showing the importance of natural
history collections and the networks they are building
Roderic Page
Roderic.Page at glasgow.ac.uk
Mon Apr 28 03:17:45 CDT 2014
2014
Hi Rich,
The distinction between data and metadata in LSIDs had little or nothing to do with the distinction between digital and conceptual objects IMHO. It was a way to transport both data (e.g., a gigabyte worth of genomic data) and metadata about that data (e.g., accession numbers, sequencing protocol, associated publications). Somehow this got muddled with a distinction between digital and conceptual objects.
In the wider RDF world people are very aware of the distinction between digital records and concepts/physical things, so much so that there has been a horrendously convoluted debate about it (the dreaded HTTPRange-14 question https://en.wikipedia.org/wiki/HTTPRange-14 ). It?s pretty much the ?what?s a species?? question for the Semantic Web (run away, run away).
One of the many things CrossRef did well was to regard DOIs as identifying an article in the abstract sense, not any particular representation of that article (e.g., paper, PDF, HTML, ePub all have same DOI). This makes it easy to say things like ?this article cites that article?, ?I am the author of this article?, etc. Hence we can talk about citation and authorship, relationships that are at the core of bibliographic data. Had they chosen to identify database records, it would be much less useful.
In the same way, if we have identifiers for specimens, we can talk about citations, sequencing, determinations, etc. I suspect a lot of this discussion would be simpler if we focus on where we?d want to be in terms of our science. I want a ?biodiversity knowledge graph? (http://iphylo.blogspot.co.uk/2014/01/what-i-be-working-on-in-2014-knowledge.html ), so I want identifiers on things that are in that graph.
Regards
Rod
On 26 Apr 2014, at 03:17, Richard Pyle <deepreef at bishopmuseum.org> wrote:
> Hi Quentin,
>
>> do the DOIs (or other identifiers) allocated to specimens refer to the
> physical
>> object or the database entry describing them?
>
> This is exactly the issue I was trying to get at. I think it depends on who
> is in charge of issuing the identifiers. If it's a collections person who
> is used to dealing with catalog numbers, and who is thrust into the role of
> informatician (e.g., due to lack of funds to hire an informatician), then
> the identifiers are intended to represent the physical (really conceptual --
> but that's another discussion) specimens. However, if the person in charge
> of issuing identifiers is from the informatics world (without a background
> in natural history collections), then often the intention is to assign the
> identifier to the data record.
>
> The real problem is that this fundamental dichotomy exists, but only a very
> few people on the front lines even realize the dichotomy exists. And even
> fewer people take the time to make it clear to the outside world what their
> identifiers actually represent. It's fashionable to bash LSIDs these days
> (perhaps justifiably), but one thing the LSID exercise forced our community
> to confront (besides the world of RDF) is this distinction between digital
> objects and conceptual/abstract/physical (i.e., non-digital) objects;
> particularly in terms of the distinction between "data" and "metadata"
> (sensu LSID spec). Other than media files (images, videos, audio files,
> PDFs, etc. -- and *possibly* gene sequences...), almost all of the stuff we
> care about in biodiversity informatics is in the realm of
> conceptual/abstract/physical. Thus, the trend has been towards minting
> identifiers for such.
>
> I'm not saying that identifiers for data records isn't important (it *is*
> important -- especially in the iDigBio space). I'm just saying that our
> community hasn't been particularly diligent about being up-front and clear
> about what our identifiers are intended to represent.
>
>> I would have thought it was the former, in which case versions are rather
>> irrelevent. I tend to agree with Rod, that versioning is not that
> important.
>
> No, it's not so much about record versions, as it is about *dataset*
> versions. It's less about what metadata was associated with each record
> than it is about what records were there.
>
> Aloha,
> Rich
>
>
> _______________________________________________
> Taxacom Mailing List
> Taxacom at mailman.nhm.ku.edu
> http://mailman.nhm.ku.edu/mailman/listinfo/taxacom
> The Taxacom Archive back to 1992 may be searched at: http://taxacom.markmail.org
>
> Celebrating 27 years of Taxacom in 2014.
---------------------------------------------------------
Roderic Page
Professor of Taxonomy
Institute of Biodiversity, Animal Health and Comparative Medicine
College of Medical, Veterinary and Life Sciences
Graham Kerr Building
University of Glasgow
Glasgow G12 8QQ, UK
Email: r.page at bio.gla.ac.uk
Tel: +44 141 330 4778
Fax: +44 141 330 2792
Skype: rdmpage
Facebook: http://www.facebook.com/rdmpage
LinkedIn: http://uk.linkedin.com/in/rdmpage
Twitter: http://twitter.com/rdmpage
Blog: http://en.wikipedia.org/wiki/Roderic_D._M._Page
Citations: http://scholar.google.co.uk/citations?hl=en&user=4Z5WABAAAAAJ
ORCID: http://orcid.org/0000-0002-7101-9767
More information about the Taxacom
mailing list