[tdwg-tag] Where to put LSIDs on tdwg ontology objects

[Bob Morris]

On Mon, Oct 6, 2008 at 6:30 AM, Roger Hyam <rogerhyam at mac.com> wrote:
>
> I am not sure I understand the problem. In RDF any non-literal can be
> represented as a URI or a local id and can therefore be the subject of an
> assertion (triplet). How can there not be a place to hang something? You can
> hang anything anywhere!

Umm, I may be confused but (a)I think It is not the URI about which we
need to make assertions, but rather the triple which has that URI as
object of rdf:about in Ben's suggestion. (b)I thought you cannot reify
a triple by using rdf:about, but must use a relative URI defined by
rdf:id

Yes you can hang anything anywhere, but if you do,  it seems not that
hard to slip out of OWL, let alone OWL DL, or in our case, to slip out
of being a valid SPM instance, such as in our initial attempt to  use
a URI as the object of hasInformation.

>
> Are we talking here about XML Schema validated XML representation of RDF?

Terry and I are talking about triples.  We generate XML/RDF but we
test our results with RDF and OWL validators.

>
> Roger
>
>
> On 5 Oct 2008, at 17:10, Bob Morris wrote:
>
>> 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:hasInformation
>> rdf: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 at 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 at lists.tdwg.org
>> http://lists.tdwg.org/mailman/listinfo/tdwg-tag
>
> -------------------------------------------------------------
> Roger Hyam
> Roger at BiodiversityCollectionsIndex.org
> http://www.BiodiversityCollectionsIndex.org
> -------------------------------------------------------------
> Royal Botanic Garden Edinburgh
> 20A Inverleith Row, Edinburgh, EH3 5LR, UK
> Tel: +44 131 552 7171 ext 3015
> Fax: +44 131 248 2901
> http://www.rbge.org.uk/
> -------------------------------------------------------------
>
>
>
>
>



-- 
Robert A. Morris
Professor of Computer Science
UMASS-Boston
ram at 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