| HARD | Hard Replacement Semantics Apply. Client should use "hard" replacement semantics (see definition in the specification section for Notify Transactions, subsection Replacement Transactions) when replacing data in client-side records with the content contained in the location identified by the <ReplacementPath>. Essentially this means that the data being sent in the current message constitutes a complete replacement for the corresponding data in client-side records |
| SOFT | Soft Replacement Semantics Apply. Client should use "soft" replacement semantics (see definition in the specification section for Notify Transactions, subsection Replacement Transactions) when replacing data in client-side records with the content contained in the location identified by the <ReplacementPath>. Essentially this means that the client should retain existing records when they are not explicitly overwritten by either a normal data tag or an empty tag in the data being sent in the current message. |
|