use the LEI ontology

[VladimirAlexiev]

A LEI ontology has been published maybe 6m ago by @rivettp, @bryon, @dallemang: https://www.gleif.org/ontology/v1.0/L1/index-en.html. Please use it in the $linkedData mapping of 6 schemas in https://github.com/w3c-ccg/traceability-vocab/tree/main/docs/openapi/components/schemas/common: LEI* and LegalEntityIdentifier*, as much as reasonable.

Here's a representation of some GLEI L1 data of Fannie Mae so you can see the prop names:

Specific notes:

• if possible, use GLEI prefixes as shown
• hasValidationSources and hasRegistrationStatus are currently not mapped ok

Maybe related to #232, though I don't know what "LEI prefixing" means. I'll write there.

[OR13]

I think we have not defined anything regarding LEI correctly. And we should, but I am not sure we have the attendance or expertise needed to fix this.

[BenjaminMoe]

@VladimirAlexiev I made a draft pull request to start using LEI ontology with our Entity schema. Can you provide suggestions for which terms could use $linkedData mapping from LEI?

[VladimirAlexiev]

Hi @BenjaminMoe! You've mapped to class gleif-L1:LegalEntity: that's a start but it's not enough.

• Can you make a list of all classes and props of these 6 schemas? As a comment below. Then I'll try to map them to LEI terms.
• There are also some semantic decisions to make, eg
  • should we use gleif-L1:legalName or schema:name?
  • if the former, should we declare gleif-L1:legalName a subproperty of schema:name?

[BenjaminMoe]

Can you make a list of all classes and props of these 6 schemas? As a comment below. Then I'll try to map them to LEI terms.

I'm guessing you mean the six schemas with the LEI prefix. Here they are, with their properties listed as bullets.

1. LEIaddress.yml
   • language
   • addressLines
   • addressNumber
   • addressNumberWithinBuilding
   • mailRouting
   • city
   • region
   • country
   • postalCode
2. LEIauthority.yml
   • validationAuthorityID
   • otherValidationAuthorityID
   • validationAuthorityEntityID
3. LEIentity.yml
   • legalName
   • legalNameLanguage
   • otherNames
   • transliteratedOtherNames
   • legalAddress
   • headquartersAddress
   • registrationAuthority
   • legalJurisdiction
   • entityCategory
   • legalForm
   • associatedEntity
   • status
   • expirationDate
   • expirationReason
   • successorEntity
   • otherAddresses
4. LEIevidenceDocument.yml
   • lei
   • entity
   • registration
   • bic
5. LEIregistration.yml
   • initialRegistrationDate
   • lastUpdateDate
   • status
   • nextRenewalDate
   • managingLou
   • validationSources
   • validationAuthority
6. LegalEntityIdentifierCredential.yml
   • leiCode
   • certificateName

[mkhraisha]

@VladimirAlexiev pinging you to resurface this.

[nissimsan]

LegalEntityIdentifierCredential.yml seems like it should be a credential. Looks like a bug.

[nissimsan]

Labelling this pending close due to lack of clear requirements and direction .

[nissimsan]

Closing due to inactivity.

[VladimirAlexiev]

@nissimsan I'll work on this issue. The latest ontologies are listed in https://www.gleif.org/en/about-lei/semantic-representation-of-the-lei/lei-model-in-rdf-resource-description-framework eg https://www.gleif.org/ontology/v1.0/Base/index-en.html#PhysicalAddress