Open bartbink opened 3 months ago
string
for registeredAddress is just a copyAndPaste-Failure. I will correct this. It should reuse registeredAddress
from business core vocabulary as shown in the example of the Legal Person Credential .
For a natural person there are 2 attributes related to the location.
postalAddress
: The full postal address. I would prefer to reuse the common terms defined by schema.org - https://schema.org/PostalAddress - because these terms are much more descriptive. But we can also use Address
from the EU Core location vocabulary - https://www.w3.org/ns/legacy_locn#Address.
domicile
: This is not the Address of the natural person. It just holds postal code, location (city) and country. Therefore, we have decided to model Domicile as a separate class. But again we can use the class Address
for an expected value of domicile
, it is just somewhat misleading.
I think it is good to use class Address, you can just ad an association called domicile next to registeredAddress. In NSG&B we added association postalAddress, some nordic countries have a registered address and a postal address at the company registration offices.
https://github.com/spherity/oid-public/blob/main/docs/contexts/eucc/vocabulary.md#4-information-model
I see that some entities/classes/attributes are stated more than once using an other name. An example is found in the information model of the EUCC. For the class NaturalPerson the attribute domicile links to the class Domicile. For the class LegalPerson the attibute registeredAddress is a string.
If we adhere to the EU vocabularies I propose the following: