Inheritance from the Organization ontology not existing

SEMICeu / Core-Business-Vocabulary

This is the issue tracker for the maintenance of Core Business Vocabulary

17 stars 4 forks source link

Inheritance from the Organization ontology not existing #30

Open GeertThijs opened 2 years ago

GeertThijs commented 2 years ago

LegalEntity is a subclass of ORG:FormalOrganization. As FormalOrganisation is a subclass of ORG:Organisation, a LegalEntity is also a subclass of Organization. With that in mind, it is unckear for me why certain attributes of LegalEntity were redefined in stead of inherited from Organization. These attributes are: identifier and orgActivity.

EmidioStani commented 1 year ago

Hello @GeertThijs ,

Concerning identifier, the Core Business uses, different URI (http://purl.org/dc/terms/identifier vs http://www.w3.org/ns/org#identifier) and different values for the property (adms:Identifier vs rdfs:Literal), thus conveying a different meaning and actually the adms:Identifier allows to provided much more metadata than just a Literal.

Users can still take the one from Organization ontology by specifying the Literal value, and, if they can, they could provide more information about the Identifier.

Concerning orgActivity, in the Organization ontology I don't find trace of orgActivity or activity, except for ChangeEvent, please let me know to exactly you are referring to.

GeertThijs commented 1 year ago

Especially in cases where some object (here an Organisation) is officially being registered, it does not hurt to allow for adms:Identifier rather than just a Literal. It enables the user to distinguish better if there are several registrations eg by selecting on the issuer of the identifier (adms:schemaAgency), rather than just rely on the @type of the Lietral.
The attribute orgActivity is indeed defined in regOrg and not in Org. However, as it has no domain, we decided at OSLO to promote it to a higher level as not only RegisteredOrganisations have activities. But this has no consequence then for your ontology, so you can ignore this further.