You might also consider http://umbel.org/umbel#isLike. Here's the definition:
The property umbel:isLike is used to assert an associative link between similar individuals who may or may not be identical, but are believed to be so. This property is not intended as a general expression of similarity, but rather the likely but uncertain same identity of the two resources being related.
This property can and should be changed if the certainty of the sameness of identity is subsequently determined.
In general, we may not be able to assert that two individuals are the same based solely on current information on hand. However, there may be quite reasonable bases or methods that the two individuals are likely the same without being one hundred percent sure.
umbel:isLike has the semantics of likely identity, but where there is some uncertainty that the two resources indeed refer to the exact same individual with the same identity. Such uncertainty can arise when, for example, common names may be used for different individuals (e.g., John Smith).
It is appropriate to use this property when there is strong belief the two resources refer to the same individual with the same identity, but that association can not be asserted at the present time with certitude.
Jeff
> -----Original Message-----
> From: SÃ¸ren Roug [mailto:Soren.Roug@eea.europa.eu]
> Sent: Thursday, January 17, 2013 7:23 AM
> To: 'Sebastian Hellmann'; Dbpedia-developers; DBpedia discussion;
> public-lod
> Subject: RE: [Dbpedia-discussion] [ANN] Add your links to DBpedia
> workflow version 0.1 (this is also an RFC)
>
> Hi,
>
> I see that you have also added EUNIS links for species. I can provide
> you with a much better quality, and I have forked the repo. But I am
> concerned about the use of owl:sameAs as the predicate. The community
> doesn't have consensus on the species names and we can't even agree on
> many species - e.g. is the goat in the Pyrenees the same species as the
> one in southern Spain or a subspecies? I don't want some OWL-aware
> query tool to be utterly confused.
>
> What I'm asking is: Can I use skos:exactMatch and skos:closeMatch
> instead of owl:sameAs?
>
> --
> Sincerely yours / Med venlig hilsen, SÃ¸ren Roug
> <soren.roug@eea.europa.eu> European Environment Agency, Kongens Nytorv
> 6, DK-1050 Copenhagen K
> Tel: +45 2368 3660Â Jabber: roug@jabber.eea.europa.eu This email was
> delivered using 100% recycled electrons. Please try to keep it that
> way.
>
>
> || -----Original Message-----
> || From: Sebastian Hellmann [mailto:hellmann@informatik.uni-leipzig.de]
> || Sent: 17 January 2013 10:18
> || To: Dbpedia-developers; DBpedia discussion; public-lod
> || Subject: Re: [Dbpedia-discussion] [ANN] Add your links to DBpedia
> || workflow version 0.1 (this is also an RFC)
> ||
> || Nice, we received links to 2 data sets yesterday, already, thanks to
> || Sarven: http://270a.info
> || It is a good start and we are really hoping for more. Note that most
> || of the links in http://richard.cyganiak.de/2007/10/lod/imagemap.html
> || only point to DBpedia and not outwards.
> ||
> || In case you are not a Git expert, GitHub allows you to upload links
> || with their GUI:
> || 1. create an account
> || 2. fork this repo https://github.com/dbpedia/dbpedia-links
> || 3. click on the "create a file button" and upload your links 4. send
> || a "pull request"
> ||
> || We might simplify the way to contribute later. Right now, Git seems
> || to be the easiest way. Any ideas are welcome.
> || all the best,
> || Sebastian
> ||
> ||
> ||
> || Am 16.01.2013 15:06, schrieb Sebastian Hellmann:
> || > Dear all,
> || >
> || > we thought that it might be a nice idea to simplify the workflow
> || > for creating outgoing links from DBpedia to your data sets. This
> is
> || > why we created the following GitHub repository:
> || > https://github.com/dbpedia/dbpedia-links
> || >
> || > Please feel free to add new files and change the links and then
> send us
> || > a *pull request*. This message is an announcement as well as a
> request
> || > for comments.
> || >
> || > Here is a (non-exhaustive) list of open issue:
> || >
> || > - it is yet unclear, when the links will be loaded into
> || > http://dbpedia.org/sparql (maybe with version 3.9? )
> || > - we plan weekly updates to http://live.dbpedia.org
> || > - yago, freebase and flickrwrappr have been excluded due to their
> size (
> || > > 0.5GB )
> || > - there will be some quality control; not everybody will be able
> to
> || > include any links he wants to include. We are open to ideas how to
> || > manage this. Consider "pull requests" as "application for
> inclusion"
> || > - folder/file structure is still very simple, we will adapt upon
> || > uptake
> || >
> || > All the best,
> || > Sebastian
> || >
> || >
> || >
> ||
> ||
> || --
> || Dipl. Inf. Sebastian Hellmann
> || Department of Computer Science, University of Leipzig
> || Projects: http://nlp2rdf.org , http://dbpedia.org
> || Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann
> || Research Group: http://aksw.org
>
>