<Country> is used in several examples and it is problematic

[ue71603]

					<Country id="uk" principality="iso3166-2:GB-EWN" version="nptg:v2.1">
						<Name>England and Wales and norther ireland</Name>
					</Country>
					<Country id="uk" principality="iso3166-2:GB-ENG" version="nptg:v2.1">
						<Name>England</Name>
					</Country>
					<Country id="uk" principality="iso3166-2:GB-NIR" version="nptg:v2.1">
						<Name>Norther Ireland</Name>
					</Country>
					<Country id="uk" principality="iso3166-2:GB-SCT" version="nptg:v2.1">
						<Name>Scotland</Name>
					</Country>
					<Country id="uk" principality="iso3166-2:GB-WLS" version="nptg:v2.1">
						<Name>Wales</Name>
					</Country>

It uses the same id and has a different pricnipality. this can't be done anymore in the future, when we have hard checking of id+version uniqueness.

[nick-knowles]

Then constraint should be altered to include principality as part of the key. for countries If one want to use formal ISO codes for counties, lander, cantons, then one needs it.

[skinkie]

Then the elemente name does not make sense...

[ue71603]

I think this should not be modeled that way. NeTEx is now id/version only. We have TopographicPlace and that's how it should be done.