-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why use dbp props? #3
Comments
Hi Vladimir, GLEIF does have a previousLegalName or something, but specifically for labels I couldn't find anything other than |
|
Yes, all entries are kept and historical entries are already replayed. Whenever something becomes repurposed or reused, as opposed to a simple rename, the (prior) resource is suffixed. So you have a chance to refer to both the old and the new exchange or MIC. You're right about dbp:formerName/Label. |
oh, I was going to mention |
In ISO10383.tarql you have this:
dbp
is not a very good namespace because it applies only to English dbpedia and signified a "raw" (unmapped) prop.dbo:formerName
(see http://mappings.dbpedia.org/index.php/OntologyProperty:FormerName)The text was updated successfully, but these errors were encountered: