Greg -
The metadata sample demonstrates how metadata can be placed on an IMediaResource, and used to give the framework more information about the resource. The MediaFactory uses this information to determine which type of media a given resource points to. One of the intial problems we encountered when creating a media factory that created MediaElements from URLResources, was the inability to distinguish between image, video, and audio urls, since the extension isn't a guaranteed way.
The Metadata framework, that was developed last sprint was provided to enable metadata such as XMP, Namevalue, and Cuepoints. Not all specific classes that hold this data haven't been created yet however. The logic to add metadata automatically hasn't been placed in the framework yet.
It's currenty possible to retrieve onPlaystatus, onMetadata, onXMPData, onImagedata, and onCuepoint callbacks:
var videoElement:VideoElement
....
[After videoElement loads]
videoElement.client.addHandler(NetStreamCodes.ON_XMP_DATA, onXMPData);
function onXMPData(info:Object):void
{
//Process XMP here.
}
Hope this helps.
