ACES Metadata Spec Draft

Discussions - ACESNext VWG – ACES Metadata File (AMF)
47

Hi all,

Thank you for your comments and feedback thus far. We have been working on changes to the spec based on feedback and have a new draft ready for review below:

S_2019_00x_AMF_DRAFT_2019.12.19.pdf (978.5 KB)

Summary of changes:

  • Updated Introduction section
    - added context of what problems AMF is trying to solve before going into what AMF is
    - introduce basic XML element names in line when describing said problems
  • Added <author> element
    - supports multiple authors, each with name and email fields
  • Removed <lookTransformStackPosition> attribute
    - added language to state that order of operations shall simply be the order in which they appear
  • Changed to individual <lookTransform> (singular) elements rather than <lookTransforms> (plural) with sub-elements
  • Changed <aces:file> type to xs:anyURI within <clidID>
  • Remove restriction of 10 occurrences of certain elements (LMTs, archived pipelines)
  • Updated hash algorithm attribute to use standard URIs
  • Updated regex of Transform ID’s to conform to new version of ACES Versioning System spec
  • Updated URN to conform better with CLF’s new URN
  • Updated examples and diagrams
  • Minor editorial fixes

The XML schema and examples have been updated here (thanks to @Alexander_Forsythe):
https://github.com/aforsythe/amf

Please have a look and let us know if you have any comments or suggestions.

@walter.arrighetti you raise good points about the potential uses and misuses of <clidID>, but I think that is largely an implementation question. We feel covered with the current <clidID> in the spec for the use cases you describe. Please join the AMF implementation calls if you can!

Thanks,
Chris

2 Likes