You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, can you elaborate more on LCI Updates? I need help understanding the aim of it.
Is it the development of a data format that could log the information about updates in XML files so a software could automatically perform it?
You mention an CSV file format. Is it available? Are the difficulties relative to the CSV file (like to "tidy up" nested data)? Is it affordable to use other formats such as a JSON?
I saw that one of the problems was related to nested information. I think considering UUID paths would be of some help (like a modification on a flow property be: {'UUID process_UUID flow_UUID property': some_change}. Fields that don't use UUIDs are generally unique in LCI formats, so they can be stored using their path inside the XML.
The text was updated successfully, but these errors were encountered:
Hi, can you elaborate more on LCI Updates? I need help understanding the aim of it.
Is it the development of a data format that could log the information about updates in XML files so a software could automatically perform it?
You mention an CSV file format. Is it available? Are the difficulties relative to the CSV file (like to "tidy up" nested data)? Is it affordable to use other formats such as a JSON?
I saw that one of the problems was related to nested information. I think considering UUID paths would be of some help (like a modification on a flow property be: {'UUID process_UUID flow_UUID property': some_change}. Fields that don't use UUIDs are generally unique in LCI formats, so they can be stored using their path inside the XML.
The text was updated successfully, but these errors were encountered: