non-standard xml-fields

[Winfried]

Besides the software made by Adobe there are other programs that write valid .xmp-data, either to the file or to a .xmp-file.
One example I have in mind is PhotoNinja:
<rdf:Description rdf:about=''
  xmlns:pn='http://ns.picturecode.com/photoninja/1.0/'>
  <pn:Crop>True</pn:Crop>
  <pn:CropMode>2</pn:CropMode>
  <pn:CropModeHeight>5</pn:CropModeHeight>
  <pn:CropModeWidth>4</pn:CropModeWidth>
  <pn:CropRect>1303 168 3787 3272</pn:CropRect>

These fields describe the cropping.
Any idea if and how such situations can be handled with IMatch?
I am not shure whether it is worth to bother about this.  But since nearly all the rubbish of Adobe's xmp-fields are shown,
why not the rubbish from other programs :-)

Winfried

[Mario]

IMatch shows all XMP fields extracted by ExifTool, and as far as I know, ExifTool always extracts and delivers all XMP fields.
If the XMP fields do not show up in the Metadata Panel in Browser mode, I would need a sample file to run some tests.

[Winfried]

I did another test:
If I set up PhotoNinja to write .xmp-files for *.dng-files then these specific data are not read from the file and not shown in the metadata-browser.
If I set up PhotoNinja to write .xmp-data into the *.dng-files then these fields are read and shown in teh metadata-browser.
Other setting, i.e. ratings or labels, that are set by PhotoNinja, are read in both cases by IMatch.

Winfried


[attachment deleted by admin]

[Mario]

Adobe and the Metadata Working expect XMP data to be embedded in the DNG file.

If you work against that rule, make sure you tell IMatch to use the XMP file and not the embedded XMP record in the DNG file under Edit > Preferences > Metadata 2: File Formats.

Change the options for the DNG format and then do a <Shift>+<Ctrl>+<F5> : Reload Metadata.

Note: Keeping XMP data for DNG files in separate sidecar files may cause problems with other applications, now or in the future. DNG has been explicitly designed to contain XMP data in embedded form. Make sure you understand the consequences when you work against Adobe's and the MWG's recommendation.