-
Notifications
You must be signed in to change notification settings - Fork 24
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
Proposition: Definition of property type of Agent (Issue #299) #320
Comments
Please be informed of the SEMIC proposition related to issue #299. SEMIC proposition: Change the recommended controlled vocabulary to legal entity type based on GLEIF maintained by Publication Office. We invite you to comment your approval of, or engage in discussions regarding this proposition. This issue has two parts, the proposition concerning the editorial part can be found under issue #299. |
See more information about the corresponding property in Core Business Vocabulary: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.1.0/#LegalEntity%3AlegalFormType |
If we are talking about the ISO 20275: Entity Legal Forms Code List there is one issue - the legal forms from various countries are not comparable. E.g. a "limited liability" company in Czechia is something different than a "limited liability" company in the UK or in Germany. Therefore, this adds precision to the information about the nature of the agent in their home country (e.g. there are more than 100 legal forms in Czechia), but this information will not be easily understood by people and machines outside of the country. Also the names of the types are only in the national language. Example from the codelist:
So I am wondering if this codelist makes sense for DCAT-AP, where we aim at Europe-wide interoperability. |
Agree with @jakubklimek if this is the Entity Legal Forms published by the Publications Office, https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/entity-legal-form. In addition, what we need here is a type classification at a "generic level", e.g. |
The text was updated successfully, but these errors were encountered: