Re: [Treebase-devel] Dryad API, advice on cyberinfastructure

[Rutger V. <R....@re...>]

> On the other hand, I'd rather not do a schema change. But we have a field
> called "URL", which we could pre-populate with
> "http://dx.doi.org/10.5061/dryad.8661". This field is usually used for
> publications that don't have a doi, and instead have a particular url -- and
> it's rarely used.  So one kluge (short of a schema change) is to
> pre-populate the url field with "http://dx.doi.org/10.5061/dryad.8661" and
> then expose that under the "prism:url" element.  What would be a good
> element to use other than "prism:url" or "prism:doi"?

Citation.url is a string so we can put whatever we like there in order
to store it. As for the element to store it under, maybe:

- dcterms:source, defined as "A related resource from which the
described resource is derived. The described resource may be derived
from the related resource in whole or in part. Recommended best
practice is to identify the related resource by means of a string
conforming to a formal identification system." (or a subclass thereof,
e.g. tb.source.study.dryad)

- dcterms:isReferencedBy, defined as "A related resource that
references, cites, or otherwise points to the described resource.", or
dcterms:references, depending on how you would qualify the
relationship between the two. Or prism:isReferencedBy

- dcterms:identifier, defined as "An unambiguous reference to the
resource within a given context."
 (or a subclass thereof, e.g. tb.identifier.study.dryad)

- prism:isVersionOf, defined as "The described resource is a version,
edition, or adaptation of the referenced resource."

To me, dcterms:source sounds like a sensible candidate.

-- 
Dr. Rutger A. Vos
School of Biological Sciences
Philip Lyle Building, Level 4
University of Reading
Reading, RG6 6BX, United Kingdom
Tel: +44 (0) 118 378 7535
http://rutgervos.blogspot.com