Access XMP Metadata outside of Acrobat

Is it possible to access the PDF metadata without using the full version of Acrobat?

An XML packet created with XMP tool kit, which conforms to XMP, can be added to the document level by attaching to the Catalog dictionary. It is also possible to add object level metadata to PDF component represented as a dictionary or stream. In either case, a reserved key Metadata associated with the dictionaries indirectly references the XMP metadata streams.<br /><br />However, in reality, writing XML packet into PDF without using Acrobat APIs, is complicated and requires a good understanding of PDF. The client must handle it cautiously:<br /> <br />·     construct an XMP conformant XML packet as the document metadata, which is in a writable XML Packet with enough padding provided for the in-place edits and expansion;<br />·     synchronize the information in the metadata stream with that in the document information dictionary;<br />·     write the XML packet to the right place in PDF; <br />·     interpret the multiple versions of XML packet correctly.<br /><br />As recommended in the XMP framework specification, applications should allocate 50% of the XML data size as padding, with a minimum of 4 KB. The purpose is to enable in-place edits and expansion of the embedded XML if the value of the end attribute is set as w in the packet trailer, <?xpacket end='w'?>.<br /><br />In addition, applications that create PDF 1.4 documents (such as Acrobat 5.0) should include the metadata for a document in the document information dictionary as well as in the documents metadata stream. Applications that support PDF 1.4 should check for the existence of a metadata stream and synchronize the information in it with that in the document information dictionary (see Implementation Note 104 on p. 804 of  PDF Reference: Third Edition, version 1.4).<br /><br />Moreover, in Acrobat 5.0 (PDF1.4), the document level metadata is constructed automatically from the document information dictionary. However, due to the incremental update mechanism of PDF, it is possible to end up with more than one copy of XML packet in PDF. Whenever the PDF is saved, a new copy of XMP metadata stream will be appended to the cross-reference section, although there may be only one or two properties are changed (i.e., ModDate and MetadataDate). <br /><br />The following PDF sample illustrates the complications. When the PDF was first created, the metadata stream is defined in the object 19 associating with the /Metadata key in the /Catalog dictionary. The value of <xap:MetadataDate> property is 2002-02-11T13:43:24-08:00. When the PDF was saved later, a new XMP metadata packet was appended to the cross-reference section, which associated with the updated entry (/Metadata 21 0 R) in the catalog dictionary. The value of <xap:MetadataDate> property is 2002-02-11T13:46:52-08:00.<br />   <br />%PDF-1.4<br /><br />7 0 obj<br /><< <br />/Type /Catalog <br />/Pages 3 0 R <br />/Metadata 19 0 R <br />/PageLabels 2 0 R <br />>> <br />endobj<br /><br />19 0 obj<br /><< /Type /Metadata /Subtype /XML /Length 1338 >> <br />stream<br /><br /><xap:MetadataDate>2002-02-11T13:43:24-08:00</xap:MetadataDate><br /><br />endstream<br />endobj<br /><br />startxref<br /><br />7 0 obj<br /><< <br />/Type /Catalog <br />/Pages 3 0 R <br />/Metadata 21 0 R <br />/PageLabels 2 0 R <br />>> <br />endobj<br /><br />21 0 obj<br /><< /Type /Metadata /Subtype /XML /Length 1338 >> <br />stream<br /><br /><xap:MetadataDate>2002-02-11T13:46:52-08:00</xap:MetadataDate><br /><br />endstream<br />endobj<br /><br />xref<br /><br />%%EOF<br /><br />Because of the above complications, Adobe can only support use of the PDF Library and Acrobat SDK plug-in for adding new XMP packets into PDF.

Similar Messages

  • Option to store xmp metadata outside of DNG file

    This would serve to improve differential backups, as the xmp file format is text based and easy to tell differences.

    Walt,
    No, you totally misunderstood what I meant. I'm not talking about LR catalog backups, I'm talking about backing up scores of dng files completely outside of LR, from the OS or some other external tool. With my suggestion, the xmp file would be right next to its dng file, and i would be backing up the whole directory hierarchy that hold my files. One of the benefits of LR over Aperture is that I can access, manipulate, and/or backup my files outside of the app rather than having them locked up in a vault which must be backed up in one huge blob.
    If I change the brightness of 500 dng files using LR, then back up all my dng files using rsync (for example), I will be copying 500 large binary files around. If my edits were saved in separate text files (xmp), then my backup program could only copy the DIFF of each of the text files (one line added to each file, so one line, or five in a normal unified diff format, is all that needs copied around). This would be exponentially faster.
    Embedded xmp edits is not a good practice, from an OS-level backup point of view. Since not everyone will agree on that, I'm asking for a checkbox option - I'm fine with it being embedded by default.
    With xmp data being stored inside the dng file, and LR changing the dng file every time I edit something, LR is hardly non-destructive from an OS-level point of view when dng files are used.
    No where in the spec does it state that xmp changes data MUST be stored in the dng file. I'm simply asking for the option to store that data outside of the DNG file, so that the dng file only needs backed up once or rarely, rather than every time I make an edit.

  • Solution to view XMP metadata in Adobe Reader ???

    Hello,
    I´m trying to find a solution to view the xmp metadata with the adobe reader.
    I know I´m able to view and edit the xmp metadata with adobe acrobat, but is it possible with the adobe reader?
    What version will I need?
    Moreover is it possible to realize two or more panels in one datafile?
    Up to now I need one file for one panel.
    Any suggestions?
    Thanks!

    I've put a PDF at http://nxg.me.uk/temp/part1.pdf This does display/print perfectly OK in both Reader and in OS X Preview.  I presume that the /Root object (254) is inside one of the ObjStm streams (yes?), as (presumably) are the /Page streams and the reference to the /Metadata object, 52.
    Regarding scanning, Part 3 of the XMP spec, Sect 1.2 says "It is always best to use format-aware file parsing when possible. Lacking this information, applications can find XMP packets by scanning the file."  Also, in Sect. 1.2.1, "A file should be scanned byte-by-byte until a valid header is found."   Finally, ISO-32000-1 Sect. 14.3.2, Note 3, says "[The XMP spec] includes a method to embed XML data within non-XML data files in a platform-independent format that can be easily located and accessed by simple scanning rather than requiring the document file to be parsed."  So it would appear that this metadata packet _should_ be found.

  • Acrobat X crashes when trying to Access XMP

    Whenever I try to access additional metadata from within the properties dialog acrobat hangs and then crashes. I tried removing my old XMP templates and restarting the app, but that has not helped. Any thoughts?
    Thanks in advance.

    Still looking for help on this one. I uninstalled acrobat 9 and X. then Re-installed X. Still no luck. Is anyone else having this problem?

  • XMP metadata access in Effect plugin

    Hi everyone,
    I was wondering if there is a way to access file's XMP metadata from the Effect plugin, like you can do in scripting using XMP scripting API?

    hi Bart Walczak! welcome to the forum!
    i don't know of a direct way using the C API. you can however get the source footage for your layer, get the path to the file and access it directly.
    you can also use AEGP_ExecuteScript() to access the data through the javascript API (i don't know how, but you say it can be done), and retrieve the result back to the C side.

  • How to get XMP MetaData as an XML String in a process?

    Hi there,
    I have a process where I would like to export a documents XMP MetaData, manipulate the XMP MetaData and then import the MetaData again to the document.
    I thougt first I will use the service Name "XMPUtilityService" with the Service Operation "Export XMP" to export the XMP MetaData as a document.
    Hoewer I am not sure how to manipulate the output document from the Export XMP service.
    When I print out the document.toString() in a execute Script Service I get the following:
    <document state="active" senderVersion="0" persistent="false" senderPersistent="false" passivated="false" senderPassivated="false" deserialized="false" senderHostId="null" callbackId="0" senderCallbackId="0" callbackRef="null" isLocalizable="true" isTransactionBound="false" defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="3440" contentType="null" length="-1"><cacheId/><localBackendId/><globalBackendId/><senderLocalBackendId/><senderGl obalBackendId/><inline><?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="A...</inline><senderPullServantJndiName/><attributes/></document>
    Actually I expected something like this:
    <?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.0-jc006 DEBUG-1.0, 2009 Jun 23 11:07:21-PDT">
       <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
          <rdf:Description rdf:about=""
                xmlns:pdf="http://ns.adobe.com/pdf/1.3/">
             <pdf:Producer>Adobe LiveCycle PDF Generator ES2</pdf:Producer>
          </rdf:Description>
          <rdf:Description rdf:about=""
                xmlns:xmp="http://ns.adobe.com/xap/1.0/">
             <xmp:ModifyDate>2010-04-20T20:43:59+02:00</xmp:ModifyDate>
             <xmp:MetadataDate>2010-04-20T20:43:59+02:00</xmp:MetadataDate>
          </rdf:Description>
          <rdf:Description rdf:about=""
                xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/">
             <xmpMM:DocumentID>uuid:0cf2c6c6-2fba-2b39-5fb6-33ad8ccf58aa</xmpMM:DocumentID>
             <xmpMM:InstanceID>uuid:187bc5a2-acb0-2fa9-711d-33ad8ccf58aa</xmpMM:InstanceID>
          </rdf:Description>
       </rdf:RDF>
    </x:xmpmeta>
    <?xpacket end="w"?>
    What do I need to do to get the XMPMeta data as an XML String from a document within a process?
    Thanks in advance!
    Paul

    Hi,
    thanks for the answer.
    I know that I can retrieve the XMPUtilityMetadata object, but this object provides only access to a few information suche as creator, subject, producer, etc.
    However I would like to retrieve the whole XML String of the XMP Metadata.
    How is this possible?
    Thanks.
    Paul

  • [CS3 JS] How To Access Custom Metadata?

    I have InCopy documents that contain custom XMP metadata in two namespaces, Dublin Core and PRISM, e.g.:<br /><br />    ...<br />    <rdf:Description<br />      rdf:about=""><br />      <dc:format<br />        xmlns:dc="http://purl.org/dc/elements/1.1/">application/x-incopy</dc:format><br />      <dc:title>Chickens and You</dc:title><br />    </rdf:Description><br />    <rdf:Description<br />      rdf:about=""><br />      <prism:publicationName<br />        xmlns:prism="http://prismstandard.org/namespaces/basic/1.2/"<br />        >Poultry Daily</prism:publicationName><br />    </rdf:Description><br />    ...<br /><br />In my JavaScript, I can access the Dublin core values but cannot access the PRISM values and I'm not sure why not.<br /><br />For example, I have this:<br /><br />doc = app.activeDocument;<br />metadata = doc.metadataPreferences;<br /><br />namespaces["dc"] = "http://purl.org/dc/elements/1.1/";<br />namespaces["prism"] = "http://prismstandard.org/namespaces/basic/1.2/";<br /><br />$.writeln("dc:title=" + <br />     metadata.getProperty(namespaces["dc"], <br />          "title/*[1]"))<br />// Returns expected result "Chickens and You"<br /><br />$.writeln("prism:publicationName=" + <br />     metadata.getProperty(namespaces["prism"], <br />          "publicationName/*[1]"))<br />// Returns unexpected empty result, should be "Poultry Daily".<br /><br />If I do metadata.save() I see the PRISM metadata in the saved result:<br /><br />     <rdf:Description rdf:about=""<br />            xmlns:prism="http://prismstandard.org/namespaces/basic/1.2/"><br />         <prism:publicationName>Poultry Daily</prism:publicationName><br />     </rdf:Description><br /><br />So I'm sort of at a loss but I suspect that I don't really understand what the path value should be--I haven't been able to find any clear documentation on what the path is addressing or how its actually interpreted.<br /><br />What am I missing or doing wrong?<br /><br />Thanks,<br /><br />Eliot

    [email protected] wrote:
    > Dude, I started that thread :-)
    Missed that. It's been a long week.
    The problem is this line (probably).
    metadata.getProperty(namespaces["prism"], "publicationName/*[1]")
    You apparently copied the syntax from dc:title in the previous line. dc:title is
    an 'Lang Alt' kind of property which is, effectively, an array. Your
    prism:publicationName is a simple value property. I suspect that the "[1]"
    syntax (and possible the "/*" before it) are what's causing problems.
    I don't recall seeing docs for this either.
    -X

  • XMP Metadata Error when creating PDF/A-1b

    Hello,
    I just started using Adobe Acrobat X for Mac to create PDF/A-1b documents from scanned TIFs.  I created a script in the Action Wizard to 1) Combine Files into a Single PDF; 2)Downsample image resolution to 150 ppi (bitmaps to 300 ppi); 3) Recognize Text;4) Pause to find all suspects and make corrections to incorrect OCR; 5) Convertto PDF/A-1b (sRGB); and 6) Verify compliance with PDF/A-1b.
    When I use the Action Wizard to to execute the script above I receive an error message stating "Metadata does not conform to XMP."  However, when I execute each of the actions manually I do not receive the XMP metadata error.  It takes a long time to execute each action manually, so I am hoping there is some way to make this full script work in the Action Wizard.
    I have an open case with Adobe regarding this issue, but so far no solutions.

    I do not receive an error when the "Verify compliance with PDF/A-1b" action is removed from the script.  Does this action have to be performed separately to avoid the XMP metadata error?

  • How can I get Adobe Bridge to show XMP metadata using Adobe Drive 4 CMIS Connector?

    I have successfully connected to an Alfresco Enterprise Edition 4.1.0 repository, using the Adobe Drive 4, created a test folder and uploaded a jpeg file containing XMP metadata into it.
    When I view the image's metadata (using Adobe Bridge), I observe that only part the standard file properties are displayed.
    When I view a local copy of the image using the same, I see all fields of the standard file properties plus available metadata.
    My question: what should I do in Adobe Bridge to be able to see all available XMP metadata?
    Kind Regards and Appreciation
    Don Greenwood
    Pixelboxx GmbH
    Dortmund

    How did you get through to customer service?  They've changed the website and I can't even find phone numbers or a chat button any more.
    Here's my story that I posted on discussion yesterday, but no one has replied:
    I am screaming and pulling my hair out right now!  The last six months with Adobe has been a nightmare.
    Once again I am completely locked out of Creative Cloud and cannot use the apps even though my automatic monthly deduction for payment was just made a couple of days ago.  Creative Cloud continues to reset itself to the trial version which runs out in 30 days and after that I am locked out once again.
    Now it looks like it is harder to access support than before.  Where are chat and the phone numbers now?  This was a nightmare with countless hours spent on chat and the phone over the last six months, and now I don't even know how to access support in order to spend even more time that does not solve the problem.  What am I to do?
    I cannot use the product I have paid for!
    Please help!

  • How do I view XMP metadata in Adobe Reader?

    How do I view XMP metadata in Adobe Reader?
    I've created a PDF which (I believe) includes XMP metadata, and I'd obviously like to check that it's been done correctly.  However it's not obvious how to view this within Adobe Reader (I'm using 11.0.04 on OS X).  Googling around, I've found an off-hand remark that Reader isn't able to do this, but this is obviously insane -- what's the point of licensing metadata if no-one can see it?  What is it I'm missing?
    Best wishes,
    Norman

    I've put a PDF at http://nxg.me.uk/temp/part1.pdf This does display/print perfectly OK in both Reader and in OS X Preview.  I presume that the /Root object (254) is inside one of the ObjStm streams (yes?), as (presumably) are the /Page streams and the reference to the /Metadata object, 52.
    Regarding scanning, Part 3 of the XMP spec, Sect 1.2 says "It is always best to use format-aware file parsing when possible. Lacking this information, applications can find XMP packets by scanning the file."  Also, in Sect. 1.2.1, "A file should be scanned byte-by-byte until a valid header is found."   Finally, ISO-32000-1 Sect. 14.3.2, Note 3, says "[The XMP spec] includes a method to embed XML data within non-XML data files in a platform-independent format that can be easily located and accessed by simple scanning rather than requiring the document file to be parsed."  So it would appear that this metadata packet _should_ be found.

  • Examples of web photo galleries that display xmp metadata

    Hello, I am wondering if anyone knows of an online image gallery that displays xmp metadata for the images displayed?
    Thanks,
    Bob

    Something you may want to consider is DBGallery (http://grrsystems.com/DBGallery). This product stores iptc/xmp data in a MySql database as well as in the image file (using Adobe's XMP Toolkit). Websites can access this data using any number of ways: PHP (google 'accessing mysql with php'), MS Access, and many others. Unfortunately right now there isn't an extremely easy means to access it directly from html like in the sample above: "< div class="content">DESCRIPTION: %FILEINFO% "; although finding someone to put together a little PHP to get close to this easy wouldn't be difficult (elance.com, etc).
    DBGallery itself allows that data to be extracted and placed in emails and pdf's (see a sample at http://grrsystems.com/DBGallery/DBGallery_Sample.pdf). It also generates websites with Title and Description, but the websites are fairly basic I'm afraid (see
    http://www.grrphotography.com/Collections/WorldPlaces/index.htm)
    Dropping any images with iptc/xmp data into DBGallery gets their data into the database because the metadata is automatically read and added to the database.
    If there are questions about this option reply here or email me at [email protected]
    Best Regards,
    Glenn Rogers
    Designer of DBGallery: Photo DATAbase System
    http://grrsystems.com/DBGallery

  • Ideas about viewing/displaying XMP metadata from Reader ?

    Hi,
    We are using Acrobat 9 to add XMP metadata to PDF documents.
    These documents are viewed by the others employees with Acrobat Reader.
    Since "File->Properties->Advanced Metadata" and "Custom Info Panels" are not available in Reader, how can we display XMP metadata ?
    Do you know some ways or plug-ins to do this ?
    Our custom XMP metadata schema have more than 20 fields, so I don't want to put all these informations in the "Keywords" field of the document properties.
    Any idea would be greatly appreciated !
    Thank you !

    Michael... what you are describing above is not accurate.  The iPod Classic does NOT have the capability of using the "Album Artist" field from iTunes to sort music.  This particular metadata field is not even available to the iPod Classic.  Only the "Artist" field is available.  (It is the other way around with the iPod Touch, iPhone, and Ipad -- for these iOS devices, the "Album Artist" field is the one that is available, and not the "Artist" field.)  There are numerous posts here in the discussion forums from other folks who are frustrated by the same issue.  The iPod Classic can only sort and group songs together by "Artist" -- that is, the track artist.  And the track artist is often quite different from the album artist.  For example...  I have 29 different Barbra Streisand albums in iTunes.  For all of them, the album artist is "Barbra Streisand."  There are several different track artists however.  Most of them are just Barbra Streisand.  But she also does a duet or two on several albums.  So there are track artists like...  "Barbra Streisand with Kim Carnes," and "Barbra Streisand with Barry Gibb," and many more like that.  After syncing to my iPod Classic, when I sort on the iPod's "Artist" field, I get about 25 different iterations of "Barbra Streisand and .... " as the artist.  Yes, "Barbra Streisand" does appear among them.  But the only songs that are listed under "Barbra Streisand" are those that she sang by herself, and where she is the only track artist.  Given the setup of the iPod Classic as it is now, using firmware version 2.0.4, it is NOT possible to use the Album Artist field to sort and group songs together. 

  • Defining Custom XMP Metadata Fields

    Is it possible (possibly through the export SDK?) to define a custom metadata field that Aperture can access?
    Specifically, Adobe allows Photoshop users to create custom metadata panels to define new XMP namespaces allowing new metadata standards to be entered. This information is saved with the image file, just like the IPTC XMP fields.
    However I am curious if there is any way Aperture can be customized to allow these custom fields to be read and set up as options in the metadata viewer.
    I'm currently involved with a NASA/ESA project to bring more complete metadata annotations to astronomy images, but so far Photoshop/Bridge seem to be the only packages with defined support for custom metadata. It would be fantastic if such fields could be accessed from Aperture too!
    PowerMac G5 2.3GHz   Mac OS X (10.4)  

    Hi Robert,
    Talk about timing! I just finished coding an export plugin for Aperture to do XMP metadata (beyond the built-in support that Aperture provides) that I'll be releasing as donation-ware in the next week and know all about this right now
    What you could do is add custom keys within Aperture, define your own XMP namespace, and then, in the plugin, map from your custom keys to the XMP namespace. If you want, drop me an email (joshanon at mac dot com), and I might be able to send you the source to my plugin as a starting point.
    Josh

  • After Effects - Warning: failed to write xmp metadata

    I have a couple of users who are saving a render job to a network share using After Effects. Towards the end of the render, they get a warning saying "failed to write xmp metadata" It does not ruin the render or anything. It just shows the warning. They have full access rights to the share. What is causing this error?

    They are successfully able to render to their local hard drive without any error and the error is only occuring with wmv output but not avi. Where exactly are the settings for XMP so that it can be configured properly?
    But since they can render to the local hard drive without any errors there must be something that AE doesnt like about rendering to a share. What could that be?

  • XMP metadata from Flashbuilder why not visible in Adobe Bridge?

    Hi there,
    I'm currently wondering around XMP metadata and swf files.
    A: Flash CS5: works
    When I use the XMP panel in Flash CS5 and export a swf, open Adobe Bridge CS5 and select the file, the XMP data are correctly displayed.
    B: Flash Builder(Flex 4.1): don't work
    When I use Flashbuilder and add my metadata to the compilation, then compile, open Adobe Bridge CS5 and select the file, nothing is included in metadata.
    Procedure based on the following (same problem if metadata are directly set through compiler arguments):
    http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_14.html
    ../src/config/ProductMetaData.xml
    <flex-config>
    <metadata>
        <title>My title</title>
        <description>My description</description>
        <publisher>The publisher</publisher>
        <creator>The creator</creator>
        <language>EN</language>
    </metadata>
    </flex-config>
    compiler argument
    -load-config+=config/ProductMetaData.xml
    As far as understood, on the background the following is added to the swf at compile time:
    <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
        <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
            <dc:format>application/x-shockwave-flash</dc:format>
            <dc:title>My title</dc:title>
            <dc:description>
                <rdf:Alt>
                    <rdf:li xml:lang='x-default'>My description</rdf:li>
                </rdf:Alt>
            </dc:description>
            <dc:publisher>The publisher</dc:publisher>
            <dc:creator>The creator</dc:creator>
            <dc:language>EN</dc:language>
        </rdf:Description>
    </rdf:RDF>
    I've checked that the medata is correctly added to the swf file using this small software polarswf:
    http://download.cnet.com/Polar-SWF-MetaData/3000-6676_4-10738623.html
    I do not know if it is safe to use it in a produciton context at least in trial mode it allows to check the metadata included in your swf.
    I wonder if this metadata coonot be read by Adobe Bridge because they are at a "lower level" than those put by flash CS5 XMP panel?
    Thank you in advance for your help.
    This is not a blocking situation, but I'm curious to understand what happend.
    Cedric Madelaine (aka maddec)

    I was following this post for a LONG time, since I noticed the same problem.
    This week I was getting in it into myself again and I noticed you use load-config. I used these compiler options :
    contributor name
    Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
    creator name
    Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
    date text
    Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
    But that resulted in this XML string where the dc namespace was missing a / on the end of the URI
    That caused the metadata which was added in flashbuilder was only visible in bridge in the rawXML panel, and not the specific fields
    changing the URI in http://purl.org/dc/elements/1.1/ did the trick ( did this in bridge by exporting the rawXML, changed the / , and imported it )
    <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
        <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
            <dc:format>application/x-shockwave-flash</dc:format>
        </rdf:Description>
    </rdf:RDF>
    Sadly there was no way I could add this / myself everytime.
    BUT then I discoverd this option :
    raw-metadata XML_string
    Defines the metadata for the resulting SWF file. The value of this option overrides any metadata.* compiler options (such as contributor,creator, date, and description).
    This is an advanced option.
    And you could give the exact RAW XML as you  described
    <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
        <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
            <dc:format>application/x-shockwave-flash</dc:format>
            <dc:title>My title</dc:title>
            <dc:description>
                <rdf:Alt>
                    <rdf:li xml:lang='x-default'>My description</rdf:li>
                </rdf:Alt>
            </dc:description>
            <dc:publisher>The publisher</dc:publisher>
            <dc:creator>The creator</dc:creator>
            <dc:language>EN</dc:language>
        </rdf:Description>
    </rdf:RDF>
    to the compiler. This could also be done in Flash with JSFL.
    In the end I wrote an ANT script which injects the exact XMLstring of metadata to Flash and Flex projects by using the raw-metadata parameter in FLEX and JSFL for flash.
    Hope this helps

Maybe you are looking for

  • Equium - HDD not recognized from Windows XP

    I have replaced the HDD in this laptop because the original had a catastrophic faulure. I have replaced the HDD correctly (as far as I can see) but when I come to re-install Windows XP the HDD cannot be recognised. Any ideas?

  • Additional field in material document list

    Dear Expert, In the T.code MB51 ( material document list)  in the ITEM DATA i need to add origin group field , is it possible ? kindly help the above issue,, Regards Akshaya

  • How can i get the password of Cisco router ?

    My Cisco router user name and password forgot. Can anyone help me to reset cisco router password ? Thanks.

  • Image Zone Send to Programs Error!

    Every time i select and image and try to use the send to program option i get an Error saying Please Select and Image. PLEASE HELP Yes i know Image Zone is no longer supported but there has got to be some way of fixing this. Restoring my PC is not an

  • Build Application, installer advanced settings

    Hi ! I build application with installer(LV70(W2K) and I like to run "example.bat" file after when user has run "setup.exe". So there is advanced installer settings, "run excutable after installation" how i should fill those lines (look attachment) So