We had a good first call this morning (reminder that meeting times, agendas, and notes will be posted on the ACESclip Workspace), and one of the questions that came up was related to modifying ACESclip metadata, and how a user would expect that to be handled.
The example brought up was that on-set DIT might create ACESclip files to pass along to the dailies facility, and a dailies colorist may re-balance (or get DP notes to modify) CDLs or LMTs that are contained or referenced.
Proposal #1: modify ACESclip and time stamp modification date using
<modificationDateTime>, so an ACESclip will always assumed to be ‘current’ when receiving one. Would we want other identifiers like hostname or software name that modified it?
Proposal #2: append new values or even entire new
<ACESclip> instances within a master ACESclip file, becoming larger as more modifications are made, and ‘current’ values would be flagged somehow. Is the history of changes important? What is the use case?
Of course we are open to other proposals but these are the first that come to mind.
Please chime in if you have any thoughts on this topic.