Skip to content
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

Open
VladimirAlexiev opened this issue Aug 19, 2022 · 4 comments
Open

why use dbp props? #3

VladimirAlexiev opened this issue Aug 19, 2022 · 4 comments

Comments

@VladimirAlexiev
Copy link

In ISO10383.tarql you have this:

<MIC exchange/market>
		dbp:formerLabel	?NAME_INSTITUTION_DESCRIPTION ;
		dbp:formerName	?NAME_INSTITUTION_DESCRIPTION ;
		fibo-fbc-fct-mkt:hasExchangeName	?NAME_INSTITUTION_DESCRIPTION ;
		rdfs:label	?NAME_INSTITUTION_DESCRIPTION ;

<MIC code>
		rdfs:label	?_miclbl ;
		dbp:formerLabel	?_miclbl ;
  • Why emit the same label as both current and "former"? Or is the idea that at some point "DELETED" entries will be left only with "former"?
  • @ElisaKendall doesn't FIBO or LEI have a term for "former name"?
  • dbp is not a very good namespace because it applies only to English dbpedia and signified a "raw" (unmapped) prop.
@hroptatyr
Copy link
Contributor

Hi Vladimir,
the idea is to collect all former names/labels (as long as LEI doesn't change) while the current one is visible as per foaf:name/rdfs:label. Similar to how Bloomberg does it (e.g. bbdp:priorMnemonics).

GLEIF does have a previousLegalName or something, but specifically for labels I couldn't find anything other than dbp:.

@VladimirAlexiev
Copy link
Author

  • So the idea is to keep loading MarketsIndividuals.ttl without replacing the old content?
    But if some bigger changes happen in MIC, won't this "accumulation" approach lead to disaster?
    Eg an exchange having status both "ACTIVE" and "DELETED"?
  • there is dbo:formerName; and you don't need both formerName and formerLabel

@hroptatyr
Copy link
Contributor

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.

@hroptatyr
Copy link
Contributor

oh, I was going to mention MarketIndividuals-hist.ttl where "historic" records are collected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants