Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeographicalName: sourceOfName #84

Open
bfrichet3 opened this issue Dec 22, 2022 · 3 comments
Open

GeographicalName: sourceOfName #84

bfrichet3 opened this issue Dec 22, 2022 · 3 comments
Labels
further info required Further info is required to the change proposal. impact on IR The change proposal has an impact on the IR. impact on schemas The change proposal has an impact on the INSPIRE XML .Schemas impact on UML The change proposal has an impact on the UML diagram.

Comments

@bfrichet3
Copy link

bfrichet3 commented Dec 22, 2022

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 fabiovinci added the for Sub-group The change proposal is to be assessed by the Sub-group label Dec 22, 2022
@fabiovinci fabiovinci added impact on IR The change proposal has an impact on the IR. impact on schemas The change proposal has an impact on the INSPIRE XML .Schemas impact on UML The change proposal has an impact on the UML diagram. labels Apr 14, 2023
@fabiovinci
Copy link
Collaborator

fabiovinci commented Apr 17, 2023

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 fabiovinci added for INSPIRE MIG-T The change proposal is to be assessed by the INSPIRE MIG-T. and removed for Sub-group The change proposal is to be assessed by the Sub-group labels Apr 17, 2023
@fabiovinci fabiovinci added the for Sub-group The change proposal is to be assessed by the Sub-group label Apr 26, 2023
@fabiovinci fabiovinci changed the title GeographcialName: sourceOfName GeographicalName: sourceOfName Apr 27, 2023
@fabiovinci
Copy link
Collaborator

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

@fabiovinci fabiovinci removed the for INSPIRE MIG-T The change proposal is to be assessed by the INSPIRE MIG-T. label Nov 10, 2023
@fabiovinci
Copy link
Collaborator

fabiovinci commented Nov 13, 2023

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

  • is a breaking change
  • is not easy to implement
  • requires an IR change
  • is needed only for one MS

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

@fabiovinci fabiovinci added further info required Further info is required to the change proposal. and removed for Sub-group The change proposal is to be assessed by the Sub-group labels Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
further info required Further info is required to the change proposal. impact on IR The change proposal has an impact on the IR. impact on schemas The change proposal has an impact on the INSPIRE XML .Schemas impact on UML The change proposal has an impact on the UML diagram.
Projects
None yet
Development

No branches or pull requests

2 participants