Except that the relationship meant by isReferencedBy is in the opposite direction. It would mean that "this record is referenced by some other resource." What we need is "this record references some other resource" which would be dcterms:references.<div>
<br></div><div>I could be convinced that dcterms:references is the general solution for what Markus has requested. Could Markus?<br><br><div class="gmail_quote">On Thu, Jul 7, 2011 at 12:23 PM, Gregor Hagedorn <span dir="ltr"><<a href="mailto:g.m.hagedorn@gmail.com">g.m.hagedorn@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I think the original scope of occurrenceDetails is contained in dcterms<br>
<br>
<a href="http://purl.org/dc/terms/isReferencedBy" target="_blank">http://purl.org/dc/terms/isReferencedBy</a><br>
<br>
or more general perhaps<br>
<br>
<a href="http://purl.org/dc/terms/relation" target="_blank">http://purl.org/dc/terms/relation</a><br>
<br>
??<br>
<br>
Gregor<br>
<div><div></div><div class="h5"><br>
On 7 July 2011 18:27, John Wieczorek <<a href="mailto:tuco@berkeley.edu" title="[GMCP] Compose a new mail to tuco@berkeley.edu" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tuco@berkeley.edu','Compose new message','width=640,height=480');return false" rel="noreferrer">tuco@berkeley.edu</a>> wrote:<br>
> @Gregor - I didn't intend to remove dcterms:source from consideration, I<br>
> just intended to keep dwc:occurrenceDetails.<br>
> It sounds like there is still support for dcterms:source independent of<br>
> issues surrounding occurrenceDetails.<br>
> I like Markus' suggestion to generalize the term we have to something like<br>
> the following, deprecating occurrenceDetails in favor of:<br>
> Term Name: recordUri<br>
> Identifier: <a href="http://rs.tdwg.org/dwc/terms/recordUri" target="_blank">http://rs.tdwg.org/dwc/terms/recordUri</a><br>
> Namespace: <a href="http://rs.tdwg.org/dwc/terms/" target="_blank">http://rs.tdwg.org/dwc/terms/</a><br>
> Label: recordUri<br>
> Definition: A reference (publication, URI) to detailed information about<br>
> the record.<br>
> Comment: Example:<br>
> "<a href="http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861" target="_blank">http://mvzarctos.berkeley.edu/guid/MVZ:Mamm:165861</a>". For discussion<br>
> see <a href="http://code.google.com/p/darwincore/wiki/RecordLevelTerms" target="_blank">http://code.google.com/p/darwincore/wiki/RecordLevelTerms</a>.<br>
> Type of Term: <a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property" target="_blank">http://www.w3.org/1999/02/22-rdf-syntax-ns#Property</a><br>
> Refines:<br>
> Status: recommended<br>
> Date Issued: 2011-07-07<br>
> Date Modified: 2011-07-07<br>
> Has Domain:<br>
> Has Range:<br>
> Version: recordUri-2011-07-07<br>
> Replaces: occurrenceDetails-2009-04-24<br>
> Is Replaced By:<br>
> Class: all<br>
> ABCD 2.06: DataSets/DataSet/Units/Unit/RecordURI<br>
> On Thu, Jul 7, 2011 at 9:08 AM, Markus Döring <<a href="mailto:m.doering@mac.com" title="[GMCP] Compose a new mail to m.doering@mac.com" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=m.doering@mac.com','Compose new message','width=640,height=480');return false" rel="noreferrer">m.doering@mac.com</a>> wrote:<br>
>><br>
>> the original intent of the dc:source issue was "A URI link or reference to<br>
>> the source of this record. A link to a webpage or RESTful webservice is<br>
>> recommended. URI is mandatory format. Allows to link to richer source data."<br>
>> When writing this I had taxonomic dwc records in mind and I needed a way<br>
>> to capture a link to a webpage or service that potentially contains richer<br>
>> data. So originally the intent was exactly the same as occurrenceDetails -<br>
>> just not limited to occurrences.<br>
>><br>
>> how about a generic dwc:details(Uri) instead?<br>
>><br>
>> Markus<br>
>><br>
>><br>
>><br>
>><br>
>> On Jul 6, 2011, at 19:47, John Wieczorek wrote:<br>
>><br>
>> > I see and agree with what you are saying. I retract the proposal to<br>
>> > remove occurrenceDetails.<br>
>> ><br>
>> > On Wed, Jul 6, 2011 at 10:42 AM, Paul J. Morris <<a href="mailto:mole@morris.net" title="[GMCP] Compose a new mail to mole@morris.net" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=mole@morris.net','Compose new message','width=640,height=480');return false" rel="noreferrer">mole@morris.net</a>> wrote:<br>
>> > I'd concur with John except for that pesky little word in the<br>
>> > definition of dcterms:source, "derived"<br>
>> ><br>
>> > "A related resource from which the described resource is derived."<br>
>> ><br>
>> > The history of recordURL, relatedInformation, and occurrenceDetails all<br>
>> > have exactly the opposite meaning in my mind. All three of those were<br>
>> > places to find additional information that was derived from some set of<br>
>> > primary objects (specimen, field notes, map, etc). A publication that<br>
>> > synthesises the most detailed information about an occurrence is derived<br>
>> > from these primary sources of information. Carrying such a publication as a<br>
>> > dcterms:source seems exactly backwards.<br>
>> ><br>
>> > I wouldn't mind using dcterms:source to indicate that a specimen label<br>
>> > is derived from field notes or that a specimen label is derived from a<br>
>> > ledger entry. However I would object to dcterms:source being used to<br>
>> > indicate that a publication is the source of a specimen record, when the<br>
>> > reality is almost certainly the other way around.<br>
>> ><br>
>> > I don't concur that the intent of dcterms:source is similar in<br>
>> > definition or intent to occurrenceDetails.<br>
>> ><br>
>> > -Paul<br>
>> ><br>
>> > On Wed, 6 Jul 2011 10:09:02 -0700<br>
>> > John Wieczorek <<a href="mailto:tuco@berkeley.edu" title="[GMCP] Compose a new mail to tuco@berkeley.edu" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tuco@berkeley.edu','Compose new message','width=640,height=480');return false" rel="noreferrer">tuco@berkeley.edu</a>> wrote:<br>
>> ><br>
>> > > I agree that the meaning of dcterms:source is different from the<br>
>> > > stated meaning of dwc:occurrenceDetails. The latter term originated<br>
>> > > with OBIS as<br>
>> > ><br>
>> > > recordURL - Gives the web address of the page where more information<br>
>> > > on this particular record (not on the whole dataset) can be found.<br>
>> > ><br>
>> > > and was re-cast in Darwin Core 1.4 as<br>
>> > ><br>
>> > > relatedInformation - Free text references to information not<br>
>> > > delivered via the conceptual schema, including URLs to specimen<br>
>> > > details, publications, bibliographic references, etc.<br>
>> > ><br>
>> > > and is currently defined as<br>
>> > ><br>
>> > > occurrenceDetails - A reference (publication, URI) to the most<br>
>> > > detailed information<br>
>> > > available about the Occurrence.<br>
>> > ><br>
>> > > So, one could argue that the dcterms:source is not necessarily the<br>
>> > > most detailed information available, and it would certainly not be<br>
>> > > only about Occurrences.<br>
>> > ><br>
>> > > So, occurrenceDetails certainly is no substitute for dcterms:source,<br>
>> > > and dcterms:source doesn't exactly circumscribe occurrenceDetails as<br>
>> > > defined. Nevertheless, the concepts are so nearly the same in<br>
>> > > definition, and certainly in intent, that I propose that adding<br>
>> > > dcterms:source obviates the need for occurrenceDetails as it will<br>
>> > > sufficiently cover the intended use of occurrenceDetails while<br>
>> > > allowing the same for all record types.<br>
>> > ><br>
>> > > On Tue, Jul 5, 2011 at 1:12 AM, Gregor Hagedorn<br>
>> > > <<a href="mailto:g.m.hagedorn@gmail.com" title="[GMCP] Compose a new mail to g.m.hagedorn@gmail.com" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=g.m.hagedorn@gmail.com','Compose new message','width=640,height=480');return false" rel="noreferrer">g.m.hagedorn@gmail.com</a>>wrote:<br>
>> > ><br>
>> > > > I think the two terms are different.<br>
>> > > ><br>
>> > > > my understanding is that dcterms source expresses a relation<br>
>> > > > between a (usually digital) record and another record, that is<br>
>> > > > derived from the first.<br>
>> > > ><br>
>> > > > I think this is very useful in DwC in cases, where records are taken<br>
>> > > > directly from a publication.<br>
>> > > ><br>
>> > > > However, it does not replace the fact that the source of the record<br>
>> > > > is the digitization project of collection X and that the record is<br>
>> > > > also cited in a recent publication.<br>
>> > > ><br>
>> > > > I have doubts whether occurrenceDetail is a good label for the<br>
>> > > > latter concept, however.<br>
>> > > ><br>
>> > > > Gregor<br>
>> > > ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Paul J. Morris<br>
>> > Biodiversity Informatics Manager<br>
>> > Harvard University Herbaria/Museum of Comparative Zoölogy<br>
>> > <a href="mailto:mole@morris.net" title="[GMCP] Compose a new mail to mole@morris.net" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=mole@morris.net','Compose new message','width=640,height=480');return false" rel="noreferrer">mole@morris.net</a> AA3SD PGP public key available<br>
>> ><br>
>> > _______________________________________________<br>
>> > tdwg-content mailing list<br>
>> > <a href="mailto:tdwg-content@lists.tdwg.org" title="[GMCP] Compose a new mail to tdwg-content@lists.tdwg.org" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tdwg-content@lists.tdwg.org','Compose new message','width=640,height=480');return false" rel="noreferrer">tdwg-content@lists.tdwg.org</a><br>
>> > <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="mailto:tdwg-content@lists.tdwg.org" title="[GMCP] Compose a new mail to tdwg-content@lists.tdwg.org" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tdwg-content@lists.tdwg.org','Compose new message','width=640,height=480');return false" rel="noreferrer">tdwg-content@lists.tdwg.org</a><br>
> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
---------------------------------<br>
Dr. G. Hagedorn<br>
<a href="tel:%2B49-%280%2930-8304%202220" value="+493083042220">+49-(0)30-8304 2220</a> (work)<br>
<a href="tel:%2B49-%280%2930-831%205785" value="+49308315785">+49-(0)30-831 5785</a> (private)<br>
<a href="http://www.linkedin.com/in/gregorhagedorn" target="_blank">http://www.linkedin.com/in/gregorhagedorn</a><br>
<br>
This communication (including all attachments) is sent on a personal<br>
basis. It is intended only for the person(s) to whom it is addressed.<br>
Redistributing or publishing it without permission is a violation of<br>
privacy rights and copyright.<br>
</blockquote></div><br></div>