- From: Andy Powell <andy.powell@eduserv.org.uk>
- Date: Fri, 7 Jan 2011 14:30:03 +0000
- To: Christopher Gutteridge <cjg@ecs.soton.ac.uk>, Hugh Glaser <hg@ecs.soton.ac.uk>
- CC: Peter DeVries <pete.devries@gmail.com>, "<public-lod@w3.org>" <public-lod@w3.org>
- Message-ID: <051279DC42F84849A64DA04141E1F9556813CE081C@edu-vmw-eml-l01.edu2000.com>
I suspect you might already be in FRBR hell with your use of dcterms:hasPart (at least in the case of linking to the PDF)... you just don't know it yet! :-) In response to the original question about linking to the PDF file, I would have thought that dcterms:hasVersion would do the job? Andy -- Andy Powell Research Programme Director Eduserv t: 01225 474319 m: 07989 476710 twitter: @andypowe11 blog: efoundations.typepad.com www.eduserv.org.uk<http://www.eduserv.org.uk> From: public-lod-request@w3.org [mailto:public-lod-request@w3.org] On Behalf Of Christopher Gutteridge Sent: 06 January 2011 21:02 To: Hugh Glaser Cc: Peter DeVries; <public-lod@w3.org> Subject: {Disarmed} Re: Is it best practices to use a rdfs:seeAlso link to a potentially multimegabyte PDF?, existing predicate for linking to PDF? But that's me making a reasonable guess and getting on with it. The EPrints document is a URI which represents a conceptual document which consists of a number of actual files, eg. HTML+JPG+CSS, so the dct:hasPart makes sense there. The main issue is how to relate the document to the metadata record, and you rapidly decend into FRBR hell. Until a few people have consumed my data I consider it very much a work in progress! Hugh Glaser wrote: I see that Chris Gutteridge uses dc:hasPart for the ePrints RDF (eprints.org). Eg: <http://eprints.ecs.soton.ac.uk/21681/><http://eprints.ecs.soton.ac.uk/21681/> dc:format "text/html"; dc:title "HTML Summary of #21681 Consuming multiple linked data sources: Challenges and Experiences"; foaf:primaryTopic <http://eprints.ecs.soton.ac.uk/id/eprint/21681><http://eprints.ecs.soton.ac.uk/id/eprint/21681> . .... <http://eprints.ecs.soton.ac.uk/id/eprint/21681><http://eprints.ecs.soton.ac.uk/id/eprint/21681> ep:hasDocument <http://eprints.ecs.soton.ac.uk/id/document/36430><http://eprints.ecs.soton.ac.uk/id/document/36430>, .... <http://eprints.ecs.soton.ac.uk/id/document/36430><http://eprints.ecs.soton.ac.uk/id/document/36430> dct:hasPart <http://eprints.ecs.soton.ac.uk/21681/1/cold2010%2Dpaper16%2Dcamera%2Dready.pdf><http://eprints.ecs.soton.ac.uk/21681/1/cold2010%2Dpaper16%2Dcamera%2Dready.pdf>; .... Cheers Hugh On 6 Jan 2011, at 19:40, Peter DeVries wrote: I was wondering if there is an existing predicate for linking to a PDF file? I would like to incorporate a link between bibliographic reference description and a URL to the location of a PDF of that document. I had minted a predicate txn:hasPDFVersion, as demonstrated in this RDF snippet. (Part of http://lod.taxonconcept.org/ses/v6n7p.rdf ) <txn:SpeciesOriginalDescription rdf:about=MailScanner has detected a possible fraud attempt from "lod.taxonconcept.org" claiming to be "http://lod.taxonconcept.org/ses/v6n7p#OriginalDescription"<http://lod.taxonconcept.org/ses/v6n7p#OriginalDescription>> <!-- Ideally, this should link to a resource in the Biodiversity Heritage Library --> <dcterms:title>Original Published Description relating to Species Concept Puma concolor se:v6n7p</dcterms:title> <dcterms:identifier>http://lod.taxonconcept.org/ses/v6n7p#OriginalDescription</dcterms:identifier> <dcterms:description>LOD metadata about the original species description relating to Species Concept Puma concolor se:v6n7p</dcterms:description> <dcterms:isPartOf rdf:resource=MailScanner has detected a possible fraud attempt from "lod.taxonconcept.org" claiming to be "http://lod.taxonconcept.org/ses/v6n7p#Species"<http://lod.taxonconcept.org/ses/v6n7p#Species>/> <txn:hasAuthorURI rdf:resource=MailScanner has detected a possible fraud attempt from "dbpedia.org" claiming to be "http://dbpedia.org/resource/Carl_Linnaeus"<http://dbpedia.org/resource/Carl_Linnaeus>/> <txn:hasBasionymName>Felis concolor Linnaeus 1771</txn:hasBasionymName> <txn:year>1771</txn:year> <txn:hasPDFVersion rdf:resource=MailScanner has detected a possible fraud attempt from "assets.geospecies.org" claiming to be "http://assets.geospecies.org/spec_concept_uuid/603bebac-cc44-4168-bbf7-b11b976f9d79/Felis_concolor_Linnaeus_1771.pdf"<http://assets.geospecies.org/spec_concept_uuid/603bebac-cc44-4168-bbf7-b11b976f9d79/Felis_concolor_Linnaeus_1771.pdf>/> <txn:speciesOriginalDescriptionHasSpeciesConcept rdf:resource=MailScanner has detected a possible fraud attempt from "lod.taxonconcept.org" claiming to be "http://lod.taxonconcept.org/ses/v6n7p#Species"<http://lod.taxonconcept.org/ses/v6n7p#Species>/> <!-- There should be a type specimen. Add link to GBIF via 'txn:sodHasTypeSpecimen' if they know about it. --> <wdrs:describedBy rdf:resource=MailScanner has detected a possible fraud attempt from "lod.taxonconcept.org" claiming to be "http://lod.taxonconcept.org/ses/v6n7p.rdf"<http://lod.taxonconcept.org/ses/v6n7p.rdf>/> </txn:SpeciesOriginalDescription> Some have suggested using rdfs:seeAlso to link to what could be a multimegabyte PDF, but I think this would cause problems for a number of RDF crawlers like Elmo. In summary, I think it would be useful to have a predicate that can be used for linking specifically to a PDF document. Is there an existing predicate for this? What do people think about the suggestion to use rdfs:seeAlso to link to a PDF? I would also like to know of others thoughts or suggestions regarding this issue, Respectfully, - Pete --------------------------------------------------------------- Pete DeVries Department of Entomology University of Wisconsin - Madison 445 Russell Laboratories 1630 Linden Drive Madison, WI 53706 TaxonConcept Knowledge Base / GeoSpecies Knowledge Base About the GeoSpecies Knowledge Base ------------------------------------------------------------ -- Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248 You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/
Received on Friday, 7 January 2011 14:30:43 UTC