Support simple addresses for eCatalogues

[idolum]

The current model of an address in the ePO looks like this:

which is much in line with the model of an address in the UBL.

In the context of eCatalogues, such an address model is considered as too complex and gives implementers of eCatalogue systems, in particular smaller ones like SMEs.

Usually, some basic data (street, city etc.) combined with three generic address lines is enough in these use cases. As an example, Peppol it implemented as follows:

• Address line 1
• Address line 2
• Address line 3
• City name
• Postal code
• Country code
• Coundtry subentity code

See https://docs.peppol.eu/poacc/upgrade-3/syntax/Catalogue/cac-ProviderParty/cac-PostalAddress/

As the full address is also used in other uses cases, the ontology might be extended as follows:

Two address, a simple and a complex one. In the context of eCatalogue these might get restricted via an Application Profile, as proposed in #316.

[jpmckinney]

I would have expected the ISA Core Location Vocabulary to be used.

[muricna]

The plan is to use the Core Location Vocabulary - we are currently working on it.

[costezki]

A Catalogue is provided by a CatalogueProvider, which is playedBy an Organisation, which has an Address.