Reference algorithm
This is a simplified version of the reference algorithm to convert transaction data from e.g. PROLIST NE 100 to ECLASS 9.
The complete document can be found here.
Simplified example
- Create a transaction structure T1 from the source data
- Create an empty transaction structure T2 for the same device code taking the target structure data (e.g. ECLASS 9).
- In case a new polymorphism has been created the application needs to use a default value (can be found in the TUF) when creating the specialization
- Traverse all nodes in T1 (depth search)
- For each node in T1
Search a node with identical path and code (without version) in T2
- Found:
Copy the value from the source property to the target property
- Not found:
Check if the node can be found in the transaction update file (TUF)
- Found:
Copy the value from the source property to the target property
- Not found:
Log an error or do an application specific conversion (like asking the user how to continue)
And some more logic for values and units ...