Change Part 5 to indicate StateNumber is optional.

Changed StateType StateNumber property to Optional rather than mandatory.

This does not solve the issue.
At least all well-known state machines described in NodeSet2 XML should have unique numbers assigned.
Some do have such numbers (e.g. ProgramStateMachineType), but others still miss the numbers (e.g. FileTransferStateMachineType).

But I think that is not affecting part 5, but more nodeset XML...

We agreed to back out the change to make the numbers optional and clone this to Nodeset and A&C to assign numbers to all transitions and states.

Will be fixed in NodeSet file - see related issue - and no changes in Part 16. I did undo all changes in Part 16

Agreed to changes backed out of 1.05 draft.

Assigned StateNumbers need to be added to FileTransfer and Alarms.

FileTransferStateMachine needs state numbers added to document.
See attached spreadsheet.

Alarm state machines need state numbers added to document.

Updated all of the statemachine table to the formats specified the new template (since need a place to add the statenumber)

Updated statemachine definition to follow new template and to include the state number (and transition numbers)

Agreed to changes in Virtual F2F.