Received: by 10.66.86.102 with SMTP id o6mr3485285paz.41.1352115663275;
        Mon, 05 Nov 2012 03:41:03 -0800 (PST)
X-BeenThere: gbif-ipt-contributors@googlegroups.com
Received: by 10.68.216.6 with SMTP id om6ls7433446pbc.7.gmail; Mon, 05 Nov
 2012 03:41:02 -0800 (PST)
Received: by 10.66.80.228 with SMTP id u4mr3482098pax.39.1352115662872;
        Mon, 05 Nov 2012 03:41:02 -0800 (PST)
Received: by 10.66.80.228 with SMTP id u4mr3482097pax.39.1352115662863;
        Mon, 05 Nov 2012 03:41:02 -0800 (PST)
Return-Path: <3zqWXUBQOAAMjeli-surylghuwrronlwjrrjohfrgh....@codesite.bounces.google.com>
Received: from mail-pa0-f75.google.com (mail-pa0-f75.google.com [209.85.220.75])
        by gmr-mx.google.com with ESMTPS id js4si3946995pbb.2.2012.11.05.03.41.02
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 05 Nov 2012 03:41:02 -0800 (PST)
Received-SPF: pass (google.com: domain of 3zqWXUBQOAAMjeli-surylghuwrronlwjrrjohfrgh....@codesite.bounces.google.com designates 209.85.220.75 as permitted sender) client-ip=209.85.220.75;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3zqWXUBQOAAMjeli-surylghuwrronlwjrrjohfrgh....@codesite.bounces.google.com designates 209.85.220.75 as permitted sender) smtp.mail=3zqWXUBQOAAMjeli-surylghuwrronlwjrrjohfrgh....@codesite.bounces.google.com
Received: by mail-pa0-f75.google.com with SMTP id fb11so628979pad.2
        for <gbif-ipt-contributors@googlegroups.com>; Mon, 05 Nov 2012 03:41:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.81.170 with SMTP id b10mr3199293pay.31.1352115662803; Mon,
 05 Nov 2012 03:41:02 -0800 (PST)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: gbif-providertoolkit
X-GoogleCode-Issue-Id: 935
References: <1-3044593288779476410-943020163114781177-gbif-providertoolkit=googlecode.com@googlecode.com>
 <0-3044593288779476410-943020163114781177-gbif-providertoolkit=googlecode.com@googlecode.com>
In-Reply-To: <1-3044593288779476410-943020163114781177-gbif-providertoolkit=googlecode.com@googlecode.com>
Message-ID: <2-3044593288779476410-943020163114781177-gbif-providertoolkit=googlecode....@googlecode.com>
Date: Mon, 05 Nov 2012 11:41:02 +0000
Subject: Re: Issue 935 in gbif-providertoolkit: Resource Relationship
 Extension invalid element (scientificName)
From: gbif-providertool...@googlecode.com
To: gbif-ipt-contributors@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Updates:
	Status: Accepted
	Cc: wix...@gmail.com

Comment #2 on issue 935 by kyle.br...@gmail.com: Resource Relationship  
Extension invalid element (scientificName)
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=935

I would have thought you could put the resourceID in:  
http://rs.tdwg.org/dwc/terms/index.htm#relationshipOfResource According to  
its definition: The relationship of the resource identified by  
relatedResourceID to the subject (optionally identified by the resourceID).

Can you please elaborate why you feel term scientificName should't be  
included in the extension please?