I'm not sure we are talking about the same thing either, but I think so, or at least almost.
WRT you example, the scenario that I have in mind is this: suppose that elsewhere in the same document, you want insure a reference to the same tn:TaxonName \data/ from the inner TaxonName that you have as object of tn:hasBasionym. In that reference I suppose one would use rdf:resource="urn:lsid:....20354". Certainly that would imply that you are talking about the same name, but I don't see how a client would be able to get all data from the elements inside your tn:TaxonName. If absolute URI were not the issue here, you would enable that using rdf:ID in the tn:TaxonName....
If I am right that this scenario isn't dealt with by rdf:about, then Terry and I have to think about whether we really care about this scenario.
Bob
On Mon, Oct 6, 2008 at 3:29 AM, Richardson, Ben Ben.Richardson@dec.wa.gov.au wrote:
Bob
I've been trying to figure out how I would represent our census data in the TaxonName ontology, and had come up with, e.g.:
<tn:TaxonName rdf:about="urn:lsid:dec.wa.gov.au:wacensus:32219"> <tn:rank rdf:resource="http://rs.tdwg.org/ontology/voc/TaxonRank#Subspecies%22/%3E tn:hasBasionym <tn:TaxonName rdf:about="urn:lsid:dec.wa.gov.au:wacensus:20354"> dcterms:createdThu Jun 12 00:00:00 WST 2003</dcterms:created> <tn:nomenclaturalCode rdf:resource="http://rs.tdwg.org/ontology/voc/TaxonName#ICBN%22/%3E tn:genusPartDryandra</tn:genusPart> <tn:rank rdf:resource="http://rs.tdwg.org/ontology/voc/TaxonRank#Subspecies%22/%3E tn:rankStringsubsp.</tn:rankString> tn:infraspecificEpithetchrysophoenix</tn:infraspecificEpithet> <tn:basionymFor rdf:resource="urn:lsid:dec.wa.gov.au:wacensus:32219"/> tn:specificEpithetionthocarpa</tn:specificEpithet> dcterms:modifiedMon Mar 17 00:00:00 WST 2008</dcterms:modified> tn:nameCompleteDryandra ionthocarpa subsp. chrysophoenix</tn:nameComplete> tn:authorshipA.S.George</tn:authorship> tcom:publishedInNuytsia 15:341-342, Fig 1d (2005)</tcom:publishedIn> dc:titleDryandra ionthocarpa subsp. chrysophoenix A.S.George</dc:title> </tn:TaxonName> </tn:hasBasionym> tn:authorship(A.S.George) A.R.Mast & K.R.Thiele</tn:authorship> tn:genusPartBanksia</tn:genusPart> tn:infraspecificEpithetchrysophoenix</tn:infraspecificEpithet> tn:rankStringsubsp.</tn:rankString> tcom:publishedInNuytsia 16:475 (2007)</tcom:publishedIn> dc:titleBanksia ionthocarpa subsp. chrysophoenix (A.S.George) A.R.Mast & K.R.Thiele</dc:title> tn:nameCompleteBanksia ionthocarpa subsp. chrysophoenix</tn:nameComplete> dcterms:createdMon Mar 17 00:00:00 WST 2008</dcterms:created> <tn:nomenclaturalCode rdf:resource="http://rs.tdwg.org/ontology/voc/TaxonName#ICBN%22/%3E dcterms:modifiedWed Mar 26 00:00:00 WST 2008</dcterms:modified> tn:specificEpithetionthocarpa</tn:specificEpithet> </tn:TaxonName>
Jena writes out the hasBasionym as a child of the main TaxonName if I am able to find a basionym for a name, which surprised me, as I didn't have to do anything special to get this representation. I'm not completely sure that we're talking about the same thing -- we both seem to be talking about intra-document references -- Jena does at least one kind of reference by default.
Cheers, Ben
-----Original Message----- From: Bob Morris [mailto:morris.bob@gmail.com] Sent: Monday, 6 October 2008 13:05 To: Richardson, Ben Cc: Technical Architecture Group mailing list; Terry Catapano; Patrick Leary Subject: Re: [tdwg-tag] Where to put LSIDs on tdwg ontology objects
I believe any node allows rdf:about without interference with the OWL version. But we need (I think) to refer in the document to various GUIDable objects elsewhere in the documents. Since reification requires (I think) rdf:ID, I am not sure rdf:about can be used....
On Sun, Oct 5, 2008 at 10:10 PM, Richardson, Ben Ben.Richardson@dec.wa.gov.au wrote:
Doesn't TaxonConcept allow:
<tc:TaxonConcept
rdf:about="urn:lsid:biocsi.ohio-state.edu:osuc_concepts:143647">
..</tc:TaxonConcept>
?
Cheers, Ben
-----Original Message----- From: tdwg-tag-bounces@lists.tdwg.org [mailto:tdwg-tag-bounces@lists.tdwg.org]On Behalf Of Bob Morris Sent: Monday, 6 October 2008 0:11 To: Technical Architecture Group mailing list Cc: Terry Catapano; Patrick Leary Subject: [tdwg-tag] Where to put LSIDs on tdwg ontology objects
In our GBIF/EOL/Plazi SPM project, Terry Catapano and I have formed the conclusion (I hope wrong...) that there is not any place on several lsidvoc objects to hang an lsid (or any other
GUID) asserted
to identify that object. For example, we don't see any place to put one on a TaxonConcept or on a PublicationCitation. In the October 1 example at http://wiki.tdwg.org/twiki/bin/view/SPM/PlaziEOLProject we have a placeholder hack using
<tc:TaxonConcept rdf:ID="_tc2"> <tc:nameString xml:lang="en">Dodous
bispinosus</tc:nameString>
<tc:hasInformationrdf:resource="urn:lsid:biosci.ohio-state.edu:osuc_concepts:143647"/>
...</tc:TaxonConcept>
but this is not valid in the tdwg ontology because hasInformation requires an InfoItem as its object.
We use other objects that face this problem, e.g. TaxonName, and I guess it is quite a broad issue (or not an issue at all if we are wrong).
Can someone recommend a valid way to address this, either for these three objects, or preferably, in general? If so, thanks
in advance.
If we are right, how about adding an InfoItem class named
GUID, that
includes an enumeration of the usual suspects, suitably typed.
Bob
Robert A. Morris Professor of Computer Science UMASS-Boston ram@cs.umb.edu http://bdei.cs.umb.edu/ http://www.cs.umb.edu/~ram http://www.cs.umb.edu/~ram/calendar.html phone (+1)617 287 6466 _______________________________________________ tdwg-tag mailing list tdwg-tag@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tag
This email, together with any attachments, is intended for the addressee only. It may contain confidential or privileged
information.
If you are not the intended recipient of this email, please notify the sender, delete the email and attachments from your system and destroy any copies you may have taken of the email and its
attachments.
Duplication or further distribution by hardcopy, by electronic means or verbally is not permitted without permission.
-- Robert A. Morris Professor of Computer Science UMASS-Boston ram@cs.umb.edu http://bdei.cs.umb.edu/ http://www.cs.umb.edu/~ram http://www.cs.umb.edu/~ram/calendar.html phone (+1)617 287 6466
This email, together with any attachments, is intended for the addressee only. It may contain confidential or privileged information. If you are not the intended recipient of this email, please notify the sender, delete the email and attachments from your system and destroy any copies you may have taken of the email and its attachments. Duplication or further distribution by hardcopy, by electronic means or verbally is not permitted without permission.