Action from Dallas Face to Face was to update Parts 3 and 5 to remove confusion and then review other parts for conflicting use of the two terms.
Proposed solution was to not use a term for the SourceNode of references by replacing all with a lower case ‘sourcenode’.
After reviewing other Parts and Companion Specs this solution seems to have been a bad idea as there are many references to the Part 3 defined term ‘SourceNode’.

Other Parts Referencing the Part3 term include:

• Part 4, One reference in AddReference Service.
• Part 9, References in HasTrueSubState, HasFalseSubState and HasCondition.
• Part 9, There are several instances that use the phrase SourceNode Property to reference the BaseEventType property SourceNode. This doesn’t seem to be consistently used.

Companion Specs Referencing the Part3 term include PLCopen, AutomationML, ISA-95 Common Object Model, ADI, etc.

New Proposal:
Since the Part3 use of SourceNode is defined as a term and is being used as such in several other specifications we leave it as is.
We will add the term "Property" to each reference of the BaseEventType’s SourceNode property to give the reader more context.

Cloned to Part 9 to make sure "Property" is added to SourceNode where necessary.

Fixed

Agreed to changes reviewed in Salzburg meeting.