search

INSPIRE-MIF / technical-guidelines

Community for the discussion of change proposals to the INSPIRE Technical Guidance documents.
https://inspire-mif.github.io/technical-guidelines
29 stars 15 forks source link

GeographicalName: sourceOfName #84

Open bfrichet3 opened 1 year ago

bfrichet3 commented 1 year ago

Dear

I hope you are all right.

As discussed in another ticket, I think we should change the value type of sourceOfName attribute (from GeographicalName featuretype). As you may know that attribute aims to describe in a human readable way the source of a GeographicalName object.

Regulation 1089/2010 states that field has to be filled with a CharacterString object. That kind of objects aims to express some human readable in one language. As you may know in Belgium we do have three national languages. Even for a Dutch name (for instance "Antwerpen") I do have to express the sourceOfName attribute in both Dutch and French to comply with belgian legislation: the language of the GeographicalName itself does not matter.

That's why I think that LocalisedCharacterString is by far more relevant than CharacterString. With such a value type, one can express in many languages the origin of a specific GeographicalName in a give language. Therefore, the cardinality of sourceOfName should become 1-...

Regards

fabiovinci commented 1 year ago

Sub-group meeting on 17.04.2023: the sub-group decided to bring this change proposal directly to the attention of the MIG-T to ask for feedback.

fabiovinci commented 1 year ago

MIG-T members were asked to provide feedback on this change proposal during the 74th MIG-T meeting.

fabiovinci commented 1 year ago

Sub-group meeting on 10.11.2023: the Sub-group does not recommend the implementation of this proposal because it:

Any other alternative solution that is not a breaking-change is more than welcome.