Hi Sebastian, Am 06.05.2013 12:54 schrieb Sebastian Hellmann :
> I merged your links into the repo. Very good, we will include them in > the data base soon. :) > I changed the readme to adjust for your requirements. I've adjusted[1] a misunderstanding resulting from my incorrectly first post , where I wrongly stated that: <dbpedia:...> <http://rdvocab.info/RDARelationshipsWEMI/workManifested> <lobid:...> To be correct, it should be "http://rdvocab.info/RDARelationshipsWEMI/manifestationOfWork";, thus implying that the dbpedia entries are frbr:Works (not frbr:Manifestations). (Our provided links, however, were correctly predicated). [...] > Additionally, you can include types, which result from inference of > the usage of the domain-specific linking property, e.g. the rdfs:domain > of the property. E.g. rdrel:workManifested is rdfs:domain > rdafrbr:Manifestation, which entails that DBpedia entries should be of > rdf:type rdafrbr:Manifestation. my fault, see above, it should be: "DBpedia entries should be of rdf:type rdafrbr:Work" > 3. Note that we also count links to other classes as links, so if you > want to add an external classification using rdf:type as linking > property, that is fine as well. hm, we at hbz are hesitant with that. While we don't want to discuss this here and now we want to make you aware of arising problems: While we think an encyclopedia generally describes a kind of abstract "work" rather than a concrete "manifestation" (e. g. a concrete edition of a book), we find that others classify dbpedia resources in a different way. E .g, if I understand correctly, the "bookmashup" dataset seems , like lobid, to describe *manifestations* of books, not *works*. But the bookmashup links with predicate "owl:sameAs" to dbpedia resources. These different approaches might result in a contradictionary assumptions. This is another example why the "owl:sameAs" predicate should be used with great care. > Thanks again Pascal, > Sebastian thank you Sebastian - looking forward to see links from dbpedia to our lod service :) pascal [1]https://github.com/dbpedia/dbpedia-links/pull/11/commits > > > Am 03.05.2013 16:15, schrieb Pascal Christoph: >> Hi *, >> >> we[1] want to provide links between lobid and dbpedia. We would like to use >> an >> other predicate as the recommended ones[2]. >> >> lobid describes manifestations of library resources, e. g. books. We find >> that >> predicates like "owl:sameAs" do not fit , because the dbpedia resources often >> don't only describe books but also other forms of manifestations (e .g. a >> play >> or a movie). Thus we use the predicate rdrel:workManifested[3] to link our >> manifestations to dbpedia resources, e. g.: >> >> <http://lobid.org/resource/HT014469321> >> <http://rdvocab.info/RDARelationshipsWEMI/workManifested> >> <http://dbpedia.org/resource/The_Last_Man> . >> >> This "means" : >> the lobid-resource is a "physical embodiment of an expression of a work", and >> that work is the dbpedia-resource (while work is defined as "A distinct >> intellectual or artistic creation"). >> >> As for the dbpedia_links we would like to use the inverse predicate - that >> would be rdrel:manifestationOfWork[4] . This would imply that these >> dbpedia-resources are rdf:type rdrel:Work[5] (we find that quite fitting, >> although not every wikipedia entry is actually a "work" (e .g. [6] is rather >> a >> "manifestation" - sure someday someone will correct this entry ). >> >> What do you think - should rdrel:manifestationOfWork be recommended in our >> case? >> >> -o >> >> [1]http://lobid.org/ >> [2]https://github.com/dbpedia/dbpedia-links >> [3]http://rdvocab.info/RDARelationshipsWEMI/workManifested >> [4]http://rdvocab.info/RDARelationshipsWEMI/manifestationOfWork >> [5]http://rdvocab.info/uri/schema/FRBRentitiesRDA/Work >> [6]http://dbpedia.org/resource/Five_Go_Off_to_Camp >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite >> It's a free troubleshooting tool designed for production >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://p.sf.net/sfu/appdyn_d2d_ap2 >> _______________________________________________ >> Dbpedia-discussion mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion >> > > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
