This is a HUGE issue when working with DAMs. To be able to export and maintain the xmp data across different file formats and apply those metafields is a must.

Amen ! Illustrator should AUTOMATICALLY (by default) AT LEAST, fill in (and update) the colors and fonts used in each element of a design in it's metadata interface file as soon as those choices are made by the designer, rather than make the designer INPUT those descriptions manually. If the designer wants to change those automatic identifiers then he/she should have to go into the metadata file interface and "uncheck" the "lock" and then manually adjust the "description". But the default identification of colors and fonts should be AUTOMATIC. This should also be true whenever an .ai file is OPENED in Illustrator, not just when one is originally creating the .ai file.

Too often, LAZY designers don't bother to enter that information before sending the .ai files to the client. Then, when the client wants to use the EXACT same colors and fonts at a printer, those colors and fonts are NOWHERE to be found (for the purpose of matching) and the "color matching" and "font hunting" games begin. This is INCREDIBLY irritating. I realize that the information MAY still be contained in the final RAW data file (but I don't know that for sure) ... but WHO has a "raw data file translator" to be able to FIND that information and understand what it means in ENGLISH so it can be successfully used ?? This should be the DEFAULT behavior in the native .ai file as well as EVERY OTHER export file type (.png,.jpg,.jpeg, etc. ) JUST FIX THIS !!!

A related problem is that Illustrator does not embed the ICC profile that is used when exporting as PNG.
When placing a PNG, Illustrator ignores the profile (when there is one) and uses the current document RGB profile.
https://illustrator.uservoice.com/forums/333657-illustrator-desktop-feature-requests/suggestions/39521494-png-export-embeds-the-wrong-icc-profile

Dan, if the issue is big enough it's still worth trying; they broke the way PNGs displayed in Bridge which was huge for my workflow and with 6 months of nagging I (we) managed to get them to (a) acknowledge they were at fault, and (b) fix it. The XMP metadata issue has only just come to light for me and it's more inconvenient than deal-breaking. I'm with you though, it's hard to get through these days - last millennium I used to chat on the phone almost daily with the Acrobat developers when I was developing an e-publishing workflow. Those were the days...

Andrew, we had to give up and just code around the bug; we cache the XMP values from the AI file and inject them in the PNG post export. Never wait for Adobe to fix critical bugs - has never happened for us and we have been Adobe developers/partners since V5 (before CS).

Wow, this is SUCH a pain, I went looking for an answer only to find it's broken. A year later too, with 5 votes. Foget that then eh?