-
Notifications
You must be signed in to change notification settings - Fork 68
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
LEI record described using FIBO #1240
Comments
@sdml Hi Dominik, This is really close. For EntityLegalForm, the identifier should point to the individual legal form, using 'identifies', rather than the other way around. Also, the relationships between the LEI Registry Entry, the Registry, and the LEI are not quite right. isRegisteredIn is the correct property from the LEI to the Registry. Rather than use isPartOf (which is transitive), we've used 'isIncludedIn' for the relationship from the registry entry to the registry. The other thing is that the registration identifier on the upper left, identifies the legal entity rather than the LEI. Best regards, Elisa |
Some further issues... Your original representation from lei.info is a bit incomplete for representing all GLEIF info: for example it misses:
There is now an official ontology representation from GLEIF, which is available via data.world https://data.world/gleif/lei-data (see also the Getting Started project linked to on the right). You may need a free account. The primary L1 ontology is also documented here https://www.gleif.org/ontology/v1.0/L1/index-en.html This data.world project includes a complete data set refreshed weekly and is also available via follow your nose and via a SPARQL SERVICE endpoint or REST interface. One technique worth pointing out at the data level is the use of multiple classification so that the RegistryEntry is also an instance of Identifier for LEI and ELF: separate classes, one individual sicne they're always one-to-one. Feel free to ping me for further info or comments. |
Thank you for all your insight. I managed to fix most of mentioned issues. |
The property is fibo-be-le-cb:isIncorporatedIn or, fully, https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/CorporateBodies/isIncorporatedIn |
FYI – makes no sense to me!
John
Jfgemski@gmail.com <mailto:Jfgemski@gmail.com> | M: (516) 353-0004
From: Pete Rivett <notifications@github.com>
Sent: Thursday, December 17, 2020 2:25 PM
To: edmcouncil/fibo <fibo@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [edmcouncil/fibo] LEI record described using FIBO (#1240)
The property is fibo-be-le-cb:isIncorporatedIn or, fully, https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/CorporateBodies/isIncorporatedIn
That has range of fibo-fnd-law-jur:Jurisdiction so if you use that property with a country or state it will be inferred to be a Jurisdiction too, which is fine for most uses IMO but if you want to be a purist you'd have a separate individual for the Jurisdiction such as fibo-be-ge-usj:StateOfCaliforniaJurisdiction, which is in FIBO with property linking it to the state fibo-fnd-law-jur:hasReach rdf:resource="&lcc-3166-2-us;California
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNGJ27YP5CKBXC4NUGC3ETSVJLG7ANCNFSM4UNYEGAA> . <https://github.com/notifications/beacon/ACNGJ265QMAXWRCBGVIBTJDSVJLG7A5CNFSM4UNYEGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFSIDHNI.gif>
|
John, @jfgemski , could you be more precise, please :-) What exactly makes no sense to you? |
Dominik, @sdml, it seems that Pete, @rivettp , gave you some hints considering modelling LegalJurisdiction. Could you share the final FIBO model for https://lei.info/J3WHBG0MTS7O8ZVMDC91.xml, please? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I've created this RDF graph of LEI record based on data from GLEIF to use as one of export formats on lei.info site. (source xml: https://lei.info/J3WHBG0MTS7O8ZVMDC91.xml). It looks like this:
Is it done correctly?
Below is entity diagram of the same data:
The text was updated successfully, but these errors were encountered: