APB and BOD sentences not decoded according to SignalK spec

[tvr256]

I've noticed a number of areas where the APB and BOD parsers don't follow the SignalK spec:

The APB parser incorrectly stores "bearing to next waypoint" to navigation.courseRhumbline.bearingToDestinationTrue which is not defined in the SignalK spec. Instead, it should be stored to navigation.courseRhumbline.nextPoint.bearingTrue. (Note, the RMB sentence also contains the same value and already stores it to the correct SignalK field).

Both the APB and BOD parsers incorrectly store "bearing from previous waypoint to next waypoint" to navigation.courseRhumbline.bearingOriginToDestinationTrue which is not defined in the SignalK spec. Instead, it should be stored to navigation.courseRhumbline.bearingTrackTrue.

The APB sentence stores the next waypoint ID to navigation.courseRhumbline.nextPoint.ID. This field isn't mentioned in the SignalK spec, should it be added?

The confusion is probably due to the NMEA spec mentioning "origin waypoint" and "destination waypoint". They actually mean previous and next waypoint, but it could easily be misinterpreted as the route starting point and final destination.