Proposal for embedding XMP in IFF and RIFF files... (where to submit?)

Question

Since Adobe does not seem to have created any proposal
for embedding XMP packets into IFF and RIFF files, I
propose the following (Is it possible to submit it
to Adobe so they can include it somewhere, do they
accept propositions?):
This is a draft proposal for embedding XMP packets into
IFF and RIFF files. Comments and suggestions are welcome.
Thanks!
Carl Eric Codere
http://www.optimasc.com
Embedding XMP data into EA IFF'85 file formats
===============================================
This proposal permits adding XMP compatible metadata to standard
IFF files. An IFF file is composed of chunks of data; each of
the chunks precedeed by a header giving the type of data that
follows, as well as the length of the data in the chunk. For
more information on the IFF file format, consult the specification
"EA IFF 85 Standard for Interchange Format Files".
Including XMP data in an IFF compatible file is a matter
of using a chunk type that will contain the XMP packet. The chunk
ID for this type of date shall be "XMP ".
Guidelines for IFF writers
If the XMP packet is to be used, the software can optionally
write out the following chunks
(defined in the original standard):
"NAME", which represents the dc:title property in XMP.
"AUTH", which represents the dc:creator property in XMP.
"(c) ", which represents the dc:rights property in XMP.
In the case where they are written, for better validation by reader
software, the XMP packet should also contain the xmp:MetadataDate
property.
For better portability, and to easily modify the embedded
XMP data, the following guidelines should be followed by
the IFF writer:
- The XMP packet should contain the full packet signature;
this permits easier searching for tools that do not
understand the IFF file format.
- The XMP packet should be encoded in UTF-8.
- As specified in the XMP specification, an XMP packet
should be filled with blank spaces for easier updating of
the XMP packet without rewriting the entire file.
A suggested size of an XMP chunk is 4096 or 8192 bytes.
- Only one "XMP " chunk should be present in the file
(Even in "CAT " files).
Guidelines for IFF readers
If an XMP packet is present in an IFF file, then one of
the following options can be used to retrieve the
metadata from the file:
If the "NAME", or "(c) " or "AUTH" chunks are also present,
then, one of the following solutions can be used:
a) Compare the xmp:MetadataDate property with the
file modification date to determine which chunk to use
for the dc:title, dc:righrs and dc:creator field. (If the
file modification date is greater than xmp:MetadataDate,
it is probably
safe to assume that the "NAME", "(c) " and "AUTH" chunks
might have been updated by software that does not
understand XMP packets.
b) Simply ignore these chunks and use the XMP
packet for the metadata.
c) Simply ignore the XMP chunk , and use the
other chunks for getting the metadata of the file.
Embedding XMP data into IBM-Microsoft RIFF file formats
=======================================================
This proposal permits adding XMP compatible metadata to standard
RIFF files. A RIFF file is composed of chunks of data; each of
the chunks precedeed by a header giving the type of data that
follows, as well as the length of the data in the chunk. For
more information on the RIFF file format, consult the specification
"Multimedia Programming Interface and Data Specifications 1.0"
Including XMP data in an RIFF compatible file is a matter
of adding a subchunk to the INFO LIST chunk. The subchunk
ID for this type of date shall be "IXMP".
Guidelines for RIFF writers
If the XMP packet is to be used, the software can optionally
write out all other INFO LIST registered (from the standard),
assuming the following ma

Answer 1

Thanks for the info Paul. You (or anyone else) wouldn't happen to know if and when a Photoshop version likely to address this issue will be available (ie embedding XMP packets into GIF and PNG files according to the guidelines presented in XMPEmbedding.pdf)?
Also, I like to point out the discrepancy for embedding an xmp packet into the PNG format (as listed in XMPEmbedding.pdf) and the sample provided in the SDK (BlueSquare57.png). XMPEmbedding.pdf state that an XMP packet is to be placed in an 'iTXt' chunk. However BlueSquare57.png has the packet in a 'tXMP' chunk. Which is the correct one? Or are they both correct and an XMP packet can be found in either an 'iTXt' or 'tXMP' chunks?
dave