AlternativeName not marked as deprecated in the XSD

[skinkie]

AlternativeName should be explicity be marked as deprecated for 2.0, because we prefer MultilingualString with translations. I don't see anything in the XML Schema reflecting that.

[TuThoThai]

@skinkie Actually, I do not see it as a bug. I believe what we have agreed on is:

• AlternativeName should not be used anymore for translations, we prefer MultilingualString
• AlternativeName should not be deprecated, as it can be used for some public transport stops that have several public names in the same language.

For example, this metro station that connects to a bigger trains station : It would be represented as:

<StopPlace id="0123456789987654321:LOC" version="any" >
	<Name>Montparnasse Bienvenüe</Name>
	<alternativeNames>
		<AlternativeName>
			<NameType>alias</NameType>
			<Name>Gare Montparnasse</Name>
		</AlternativeName>
	</alternativeNames>
	...
</StopPlace>

What could be done in the XSD documentation is add a mention that it should not be used for translation since v2.0. That I can do!