Remove wrong PlaceName property from HeadingSign

[Robbendebiene]

While working at #944 I noticed that in order to add any HeadingSign specific property (like LineName or TransportSubmode) I had to define a PlaceName first. This is probably a copy paste error from PlaceSign. At least to me it doesn't make sense why there should be a mandatory PlaceName property that must exist in order to define any properties from the HeadingSignGroup.

It is probably to late but since this would be a braking change perhaps it could be included in 2.0. Otherwise I could also deprecate the property and set it to minOccurs="0". Let me know what you think @Aurige @skinkie

[skinkie]

@nick-knowles has added it.

[Aurige]

To me it should not be mandatory, but I would still keep (that's often that a HEADSIGN is the name of the destination place).

[Robbendebiene]

but I would still keep (that's often that a HEADSIGN is the name of the destination place).

@Aurige Isn't the name of the destination described via the DirectionName (from HeadingSignGroup) or is there a difference?

[Aurige]

Direction is more something like south/west/inbound/outbound/clockwise/left/right, etc.
Destination is the end station
Place would be a city, a POI, etc.

But I agree that additional comments would help

[Robbendebiene]

@Aurige Okay thanks for the clarification. I re-introduced the PlaceName property, but made it optional. I also moved it to the HeadingSignGroup and slightly altered its documentation.

[Aurige]

26/08 : need Check with example

[skinkie]

If it validates, continue.

[skinkie]

(and it is currently not checked within github!)

[skinkie]

@Aurige I checked it. Examples validate, may be approved (and merged)