Use of URIs for AddressRepresentation

[yarondassonneville]

Based on the discussions we had around the URIs of the data type ‘AddressRepresentation’ we have a few possible solutions.

Currently OSLO Address is used for the implementation of this class, including the URIs of data.vlaanderen.be where no other existing URIs were possible. We proceeded via this way as both INSPIRE and BeST don’t publish URIs.

Based on the discussions we had, these are the possible solutions:

• We stick with using OSLO Address and keep reusing the existing data.vlaanderen.be uris
• We suggest the creation of a new application profile, ICEG Address with its own URIs (in a next iteration)

Could you let us know what should be the preferred approach?

[Bert-NGI]

Might a possible solution be to construct an URI based on the BeST namespace and the BeST objectidentifier, available in the published BeST data? Some more info on slide 8 of this presentation: https://dtservices.bosa.be/sites/default/files/content/best_overview_1.pdf

For Flanders, this will be similar to the OSLO Address as the BeST namespace for Flanders is https://data.vlaanderen.be/id/adres

[bahimc]

This issue will be considered closed as we will construct an URI based on the BeST namespace and the BeST objectIdentifier.

[hlorent]

The URIs is a concept specifically used for linking purpose and is not specific to INSPIRE. In INSPIRE, the Uris structure is just recommended. Currently there is a common statement among the MSs to apply it. The use of ICEG specific URIs, other than those proposed by the INSPIRE documentation, should not be a problem regarding the INSPIRE compliance of the future dataset.