XMP definition in XMP

Hello everyone,
the development for XMP could be much easier if we had XMP definition in XMP
For example one could create GUI for XMP editing even without reading XMP ducumentation.
All we need is to parse XMP tree and translate metadata to appropriate programming language.
Moreover such authomated processing would minimize bugs in programms.
My english is not the best, but I hope everybody understand my idea.
For example definition of arrays could look like:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
 <rdf:Description rdf:about=""
 xmlns:xmpDef="http://ns.adobe.com/xmpDef/1.0/">
 <xmpDef:Array>
 <rdf:Bag>
 <rdf:li>Bag</rdf:li>
 <rdf:li>Seq</rdf:li>
 <rdf:li>Alt</rdf:li>
 </rdf:Bag>
 </xmpDef:Array>
 </rdf:Description>
</rdf:RDF>

Screen shot was not posted. Here is a portion of the XMP packet
generated.
 <rdf:Description rdf:about=""
 xmlns:pdfaExtension="http://www.aiim.org/pdfa/ns/
extension/"
 xmlns:pdfaSchema="http://www.aiim.org/pdfa/ns/schema#"
 xmlns:pdfaProperty="http://www.aiim.org/pdfa/ns/property#">
 <pdfaExtension:schemas>
 <rdf:Bag>
 <rdf:li rdf:parseType="Resource">
 <pdfaSchema:prefix>dc</pdfaSchema:prefix>
 <pdfaSchema:namespaceURI>http://purl.org/dc/elements/1.1/
</pdfaSchema:namespaceURI>
 <pdfaSchema:schema>Dublin Core Schema</
pdfaSchema:schema>
 <pdfaSchema:property>
 <rdf:Seq>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>contributor</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Contributors to
the resource (other than the authors).</pdfaProperty:description>
 <pdfaProperty:valueType>bag ProperName</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>coverage</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>The extent or
scope of the resource.</pdfaProperty:description>
 <pdfaProperty:valueType>Text</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>creator</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>The authors of
the resource (listed in order of precedence, if significant).</
pdfaProperty:description>
 <pdfaProperty:valueType>seq ProperName</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>date</pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Date(s) that
something interesting happened to the resource.</
pdfaProperty:description>
 <pdfaProperty:valueType>seq Date</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>description</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>A textual
description of the content of the resource. Multiple values may be
present for different languages.</pdfaProperty:description>
 <pdfaProperty:valueType>Lang Alt</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>format</
pdfaProperty:name>
 <pdfaProperty:category>internal</
pdfaProperty:category>
 <pdfaProperty:description>The file format
used when saving the resource. Tools and applications should set this
property to the save format of the data. It may include appropriate
qualifiers. </pdfaProperty:description>
 <pdfaProperty:valueType>MIMEType</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>identifier</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Unique
identifier of the resource.</pdfaProperty:description>
 <pdfaProperty:valueType>Text</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>language</
pdfaProperty:name>
 <pdfaProperty:category>internal</
pdfaProperty:category>
 <pdfaProperty:description>An unordered
array specifying the languages used in the resource.</
pdfaProperty:description>
 <pdfaProperty:valueType>bag Locale</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>publisher</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Publisher(s).</
pdfaProperty:description>
 <pdfaProperty:valueType>bag ProperName</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>relation</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Relationships to
other documents.</pdfaProperty:description>
 <pdfaProperty:valueType>bag Text</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>rights</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Informal rights
statement, selected by language.</pdfaProperty:description>
 <pdfaProperty:valueType>Lang Alt</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>source</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>Unique
identifier of the work from which this resource was derived.</
pdfaProperty:description>
 <pdfaProperty:valueType>Text</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>subject</
pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>An unordered
array of descriptive phrases or keywords that specify the topic of the
content of the resource.</pdfaProperty:description>
 <pdfaProperty:valueType>bag Text</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>title</pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>The title of the
document, or the name given to the resource. Typically, it will be a
name by which the resource is formally known.</pdfaProperty:description>
 <pdfaProperty:valueType>Lang Alt</
pdfaProperty:valueType>
 </rdf:li>
 <rdf:li rdf:parseType="Resource">
 <pdfaProperty:name>type</pdfaProperty:name>
 <pdfaProperty:category>external</
pdfaProperty:category>
 <pdfaProperty:description>A document type;
for example, novel, poem, or working paper.</pdfaProperty:description>
 <pdfaProperty:valueType>bag Text</
pdfaProperty:valueType>
 </rdf:li>
 </rdf:Seq>
 </pdfaSchema:property>
 </rdf:li>
 </rdf:Bag>
 </pdfaExtension:schemas>
 </rdf:Description

Similar Messages

No XMP syntax definition? Looking for XMP DTD...

Hi,
I am trying to solve an incompatibility between two software products. One product writes images with an embedded XMP in an way that some other programs (including Photoshop) complain about beeing unable to read all information when opening these image files.
I've tracked the problem down to the xmpRights:UsageTerms attribute, but was unable to find a hint wether the file is incorrect (and a writer problem) or correct (and a reader problem).
interestingly, there are Documents describing the meaning of XMP entries, such as Iptc4xmpCore_1.0-spec-XMPSchema_8.pdf or IPTC-PhotoMetadata(200907)_1.pdf , which describe the meaning of 'field names', e.g. they describe a UsageTerms as something containing free text describing how the news object can be legally used. But I did not find any precise description about wether this should be an XML attribute or element, and where it is syntactically allowed.
It does not make sense to describe the meaning of a field name without declaring what sort of field it is and where it is allowed.
Where would I find a DTD or similar precise syntax description?

Thanks for that link. Have to read it.
I tracked the current problem down to the fact, that Adobe Lightroom puts the usageTerms into an element, looking like
<xapRights:UsageTerms>
<rdf:Alt>
<rdf:li xml:lang="x-default">
...some text...</rdf:li>
</rdf:Alt>
</xapRights:UsageTerms>
while bibble Pro 5 puts it into an attribute like
<rdf:Description ... xmpRights:UsageTerms="..." ...>
Based on the descriptions about XMP I found so far it is impossible to tell which of both is correct (and where the element or attribute is allowed). Hope to find some answers in that document.

How can I make metadata saved to xmp file stay saved?

When a raw file badge shows that the file has been changed, I use Metadata Save to File & for the large majority of my images, the badge goes away and Metadata Status Changed does not show the file. For some of my files, however, the Save to File command doesn't work properly. If I am only displaying files with changes, the file briefly disappears, then returns. Even if I go to Windows Explorer and delete the xmp file, then again Save metadata to file, it pops up again with the badge saying it needs to be saved. Can anyone tell me what I might be doing wrong, or is there a bug? I'm using Lightroom 4.3 64 bit on Windows 7.

I have determined one definite cause for this problem, documented (see 2nd post) here:
http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_4rc_metadata_needs_to_be _saved_status_not_cleared_by_saving_metadata
As has been mentioned, following metadata save with metadata read is a work-around.
Note: you can see exactly, everything, the difference between metadata in catalog and metadata in xmp on disk, using ChangeManager's "Compare Catalog to Disk" feature; hint: choose 'No Exclusions' to see the "inconsequential" differences too. Reminder: this does a bunch of stuff involving xmp file copying and saving xmp / reading metadata / restoring afterward... - which presents lots of hoops to jump through, at first, in Windows, and forever, on Mac, but if you tough it out, you will get the pot of result gold at the end of the hoop rainbow...
Cheers,
Rob

FotoStation wipes ACR settings from .xmp

My employer has recently decided we need to use FotoStation (mostly because we work over a network, and FS is good for that... anyway) to organise, and apply metadata to, our photographs and videos. I do still use Bridge for previewing, ratings and making adjustments via ACR.
I have noticed that when I have updated the metadata via Fotostaion, it removed ratings and ACR information from the .xmp file in Bridge (not the file itself, just the specific ACR/ratings data within). I made sure that, when I made the changes in FotoStation I selected to "Append new text to existing text" (the other option is to "Replace the existing text"). It definitely removes the ACR information because I tested it out by opening an image in ACR, editing it, clicking done (definitely clicked done not cancel, changes seen in Bridge) then updated the metadata via FotoStation, went back to Bridge and the ACR changes were gone. I opened the "File Info" and read the "Raw Data" before and after the FS edit and the info was there before and gone after.
SO is there a way to not allow this to happen? FYI I will be posting this to the FotoStation forum as well, I just want to cover both bases. FotoStation doesn't feel it is necessary to have a forum apparently. I'll provide camera and application information below.
Windows 7 x64
Working over a network
Adobe Bridge CS6 (v5.0.2.4)
Camera Raw 8.4
FotoStation 7.0 (Build 459)
Canon EOS 5D (.CR2 files)
No I cannot work off the network, or get newer versions of applications (at this current time); what I have there is all I have to work with at this point in time.
I will, for now, simply add the metadata using Bridge but I would still like to see this issue resolved if possible as it is the preferred method utilised by my employer and not my decision to change. My input is not required

I don't have FotoStation b459 only b60*. I can confirm that you need to rebuild the thumbnails in FotoStation to see metadata changes done in Adobe Bridge. This forces FotoSation to re-index the image.
There should be no unintentional metadata lost when going back and forth between FS and Bridge. However, you should check that your FotoStation metadata configuration includes the Adobe and IPTC name spaces and fields you need. If not you can create them manually or import from an image. The FotoStation documentation shows that this is easy to do.
As an aside I find that Adobe CS5 deletes metadata information in fields that are deprecated or no longer belong to the Adobe name space. This is a potential serious problem for digital images generated using legacy software and hardware.
As a FotoStation user for the last 4 years, in my opinion, your employer is correct. FotoStation is one of the best software for metadata and digital asset management. Good luck!

Checkboxes in custom panels/boolean XMP properties

I have a large and expanding collection of photos, the majority of which are either (a) gig photos or (b) photos of railway signalling. The latter include a 'legacy' collection of some 2,000 35mm slides which I am slowly but steadily digitising using a film scanner. I make a lot of use of Adobe Photoshop CS2.
To assist in cataloguing my collections, I have created two custom XMP metadata panels, one for the gig photos and the other for the railway ones. I have installed both of these in the appropriate directory on my PC and they work very well, with the exception of the one small issue described below. Can anyone help me with that?
As I built up my railway slide collection, I adopted a system of numbering and categorising the slides which I have now incorporated into my custom panel and its underlying XMP extension schema. One of the properties within my system is a boolean setting, so I incorporated this as a check_box control within the custom panel for the railway photos.
What I am now finding, however, is that whenever I update the metadata of
any image on my PC, the default value of false is inserted for this property regardless of whether or not I have set any of the other properties defined in the custom railway photo metadata panel. I would prefer for this property to remain unset unless I specifically set it via the dialogue box. Is there anything I can do to achieve this?
For reference, the check box definition from my railway photo custom panel is:
check_box(name: '$$$/RailwayPhotos/item=Substitution ',
hotizontal: align_right, xmp_ns_prefix: 'RailPhoto',
xmp_namespace: 'http://www.roscalen.com/RailwayPhotos/1.0/',
xmp_path: 'substituted');
TIA
Adie

OK, this is what I have done.
The swf file is named generic.swf
I made a text doc and put this path in the text
C:\Users\Chyron\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\Athletes (US)\bin\
then saved it and renamed the .txt to .cfg and then created folders like you said above because they did not exist.
and put the file there.
C:\Users\chyron\AppData\Roaming\Macromedia\Flash Player\#Security\FlashPlayerTrust
and still does not work

Delete XMP meta *including* xmpMM:history

Hi all,
a quick question, maybe you as experts are so kind to give a hint:
i need to delete the xmpMM:history of an Adobe Illustrator (Mac OSX 10.6) file – neither AI CS 4 nor BRIDGE CS 4 let me do it. hitting the trash can button in the file information dialogue clears all meta data – but after a reload of the file it appears again.
what might a be a quick workaround for the mac?
i was searching for 45min on the net and only found crappy exif file viewers..
thats why I turn to you - the professionals – now.
thank you so much.
i appreciate your answers.
m

xmpMM:History is an "Internal" property that is specifically "owned" by the application.
In the definition of an Internal Property: "Must be maintained by an application. ... Users should not be allowed to change the values of such properties. ... If an application does not set the value of an internal property, it should discard any value that may have existed previously."
Use of Delete in File Info->Advanced is surely considered a "User" change, and thus, not supported for xmpMM:History. Since File Info is often silent on a command failure, it is prudent to reload the file to see if changes really took effect.
I expect that Illustrator may handle "internal" metadata differently for different file "Save" scenarios:
- "Save As" especially to another file format
- "Save a Copy"
- "Save for Web & Devices" (typically minimizes the metadata size)
You may need to experiment to characterize the behaviors relative to xmpMM:History.
Although it may not apply to your situation, the three versions of save listed above should always result in a single XMP packet in the file. On the other hand, an Illustrator "Save" or a Bridge "Update XMP" can result in a new "current" XMP packet appended to the file, leaving the first, now obsolete, packet still in the file. Reload the file in Illustrator or Bridge should only report metadata from the "current" XMP packet. Other applications, such as Mac OS-X Spotlight, may report tags and content from obsolete XMP packet(s) as well as from current packets.
What is your purpose for deleteing this metadata?
Carl

LR 1.3.1 waiting for non-existing xmp and thm files

I am experiencing a problem where Lightroom 1.3.1 stalls while I am scrolling through larger folders/collections. This happens on some (specific) folders only, but can get to a point where LR becomes unusable.
Trying to nail that down, I used a file monitor (filemon from sysinternals) and spotted that LR is looking for xmp and thm files that do not exist. The reason this is slow for me probably relates to the fact, that this search happens over my local network (because my original photos are on a different computer). Estimating numbers, LR waits approx 500 ms per photo (looking for .xmp, .XMP, .thm and .THM in that time), but only for some photos in that folder.
I upgraded from 1.2 to 1.3.1 and am quite certain, that this was smooth with 1.2.
My catalog definitely doesn't write to xmp automatically. I do in fact not have a single xmp file in any of my directories. In catalog settings I also have the 'Include develop settings in metadata in jpg...' deactivated (what does that btw?).
Anyone experiencing similar issues? Any ideas what I am doing wrong here? Why is LR looking for those files in the first place?
Stefan

I am actually a bit surprised I am the only one hitting that problem.
Does anyone else have a setup where the original photos are on a networked machine, and the working catalog is on the local machine where Lightroom is running? I assume this is why I am experiencing long delays whereas 'normal' users just don't notice that problem...

Custom command for custom XMP metadata

Hi
I'm trying to create a custom command for setting and getting custom XMP metadata using InDesign CS3 SDK with Xcode.
I think I got the step 1) to 3) ok. But not so sure about step 4).
Please take a look and tell me if I have got anything wrong.
1) Create 2 classes and 1 interface
MyCustomMetadata
MyCustomMetadataSetCmd
IMyCustomMetadata
2) Define class definitions in the resource file
/** Boss class for kMyCustomMetadataBoss */
Class
kMyCustomMetadataBoss,
kInvalidClass,
IID_IMYCUSTOMMETADATA, kMyCustomMetadataImpl,
/** Boss class for kMyCustomMetadataSetCmdBoss */
Class
kMyCustomMetadataSetCmdBoss,
kInvalidClass,
IID_ICOMMAND, kIQAdTicketMetaDataSetCmdImpl,
IID_IMYCUSTOMMETADATA, kMyCustomMetadataImpl,
3) Define functions for setting and getting values in MyCustomMetadata
GetMyTitle()
SetMyTitle()
Within these functions, use IMetadataAccess interface to set/get values.
4) Create Do() function in MyCustomMetadataSetCmd
??? I'm not sure what I'm supposed to do here ???
Any help would be really appreciated.
Thanks,
JP

m41miller42 wrote:
I am attempting to create a custom RSS file (.mrss) that references XMP metadata from Premiere.
I was basing the move on this statement. This was posted in the Adobe Connect forums.

Filters not importing with xmp files

I have an editor do my culling and color correction with Lightroom. She sends me the xmp files and she uses the stars and color filters to show which images she has picked but sometimes the stars and filters don't show up.
Her color correction is there, as I can see which images have been worked on, but I can't filter out the ones she hasn't chosen as the stars don't show up.
This is so frustrating, what is the issue?
She uses a Mac and I use a PC, but sometimes we have no trouble at all.

What version of Lightroom are both of you using? Because there is a better way to handle this if you are both using LR5. You send her the catalog and Smart Previews file, she could just send you the catalog back, and then you do an Import from catalog. That will pull in all her edits and metadata changes. If she perhaps did not Save metadata after she had made her ratings that could possibly explain it. Its the older way of doing remote editing and its definitely prone to error or mistakes.

What happened to .xmp files?

I have noticed recently that my Bridge program (cs4) has not been automatically exporting .xmp files into the folder where I store my images. I have been doing a lot of reading, but still can't seem to find a solid answer as far as what to do.
I have figured out how to export .xmp files into another folder, but what's the point of that? I want the metadata for my images to stay with my images. When I move them from folder to folder using Bridge, the xmp files used to move also, so I never lost my metadata.
I also empty my cache fairly often. I noticed that Bridge was no longer exporting xmp files when I emptied my cache and ALL my metadata that I had added to my images was gone, just like that.
I am a photographer and need that information to go somewhere permanent automatically, not in the cache which is supposed to store temporary file information.
Anyone have any idea?
Thanks so much!

Tai Lao wrote:
Your post #29 is completely blank
Strange, I responded using email and this normally functions well, maybe the chance in formatting and quoting did not get through?
I don't want you to think I'm ignoring you.
How could you think of that...
here is a copy of the mail, hope the formatting keeps clear!
>> Omke Oudeman wrote:
>>
>> As far as I understood the producing of magenta colorcast is a fault by
>> Pentax and the recovery utility does only work on original Pentax DNG, the
>> PEF files already have some compression and don't display all the sensor
>> data, Right?
>
> Wrong, very wrong. But that is definitely off topic.
It is what I understood (after briefly scanning through page) from this post that advices to shoot in K20 generated DNG instead of the PEF format.
http://www.pentaxforums.com/forums/pentax-dslr-discussion/67532-how-use-k20s-black-pixels- hidden-dngs.html
>> Omke Oudeman wrote:
>>
>> …I did something else, I opened 2 files in ACR, one the original CR2 and the
>> other the DNG conversion of it. ............ I could not find one single >>difference between both files…
>
> That is irrelevant. The issue is that there is some information inside the
> raw files that is not currently used either by the Pentax software or by
> Adobe, but that a third party (Gordon B. Good in this case) was able to
> utilize in order to improve the quality of certain converted raw files.
For your files in certain conditions at high iso this seems to be the case, the DNG files converted by Adobe DNG converter do miss the border pixels needed for the script from GordonBGood.
I tried to download that application but it seems only for Windows, how do you manage to use it?? Thought you have given up on Windows long time ago??
Nevertheless I also tried the apply image method you quoted from Bruce Fraser in an other post, using subtract with offset 128 and both perfectly the same.
I do agree that Raw converters from nowadays can get more out of the Raw data then they did 8 years ago, trying an 8 year old raw file gives a much better result (but then you also have to keep in mind that our knowledge and skills in Digital imaging have grown in combination with better color management understanding and good calibration soft and hardware is also due to this!)
Also I'm not afraid my benefit from the future Raw converters will differ if I use DNG instead of the original Raw, but that is my personal believe. The result I get nowadays for combination of DNG and PS are already more then satisfying, and sure it will be better in the future but for that I have also faith in DNG :-)
> Yes, I use PSDs exclusively. However, if you don't think TIFF will be around
> in 15 years, why do you think DNG will? After all, *+Adobe owns the TIFF
> format+* as well as the PSD format.
>
> If you trust Adobe to keep the DNG alive for 15 more years, why don't you
> trust that same corporation to keep supporting TIFF, a format for which they
> paid darned good money to acquire?
That is just a question of the market, as you could see that our young friend that started this post never uses it and I do hear more voices saying they don't use it or don't see the use for it. Eventually there will be no need for letting seldom used formats taking space in menu's and applications.
DNG however is still talk of the town, whether you like it or not. And therefore more likely to be around in 15 years time. But you are right, If I was to know about what was going on in 15 years from now I would not be a photographer but a fortuneteller and in my free time bathing in countless money :-) :-)
> Another one of the reasons why I don't like DNGs is, number one, that they
> take an awful lot longer to open than the raw files.
That I still can't understand unless you have chosen to use the original raw file included and created a double size for the file. But as stated in earlier post, not the case on my system.
> Not that any of this—or anything else in the world for that matter—should be
> an issue for me then.
Statistically you have lived the greatest part of your life and knowing your health is not something to be jealous of (to put it mildly) your statement about this also is something only time will learn.
Let's wish we still can have a long period for our little chats, agreed or not.
I will give up on getting you to DNG (for now as it is...) :-) :-)
Vriendelijke groet,
Con cordiales saludos
感谢你和亲切的问候

Machine readable XMP schema specification

I am working on a XMP custom schema creation and embedding tool in Java. In the Adobe XMP Specification from Jan 2004, under section 4, Extensibility of Schemas, it mentions that there might be future support for machine readable schema specifications. I was wondering if any work had been done on this so far. My idea on this is to use regular expressions to allow the computer to enforce the values for a property. This could be embedded as: <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:language type=Locale regex=[a-zA-Z]{1,8}(-[a-zA-Z]{1,8})*> <rdf:Bag> <rdf:li /> </rdf:Bag> </dc:language> <dc:coverage type=ProperName regex=.+ /> </rdf:Description> </rdf:RDF> The type attribute is used as a human readable type, which matches the type in the schema definition. The regex attribute is the machine readable part, a regular expression (regex) against which the input can be matched. Only matching input would be considered valid. For a ProperName, this is any text, and for a Locale, it follows the RFCI1766 specification. Of course, the attribute names could be changed. This is the way my program does it now, which seems to work. If anybody knows more about this, I would like to know, or if you want more examples, I can provide them. Thanks, Tuli Colorado School of Mines

I have a question about the custom panel language...
The document you provide seems to lack details on some features. Namely the icon and picture widgets. I see from looking at the examples and other vendor's web pages that these features exist, but I don't find any detailed descriptions of them in the documentation. Is there a more complete document describing these...
http://www.adobe.com/products/xmp/custompanel.html
Alternatively, can someone fill me in on the syntax and options for at least the icon and picture widget. For instance, how do you load external icon or pictures...
Tom

LR2 too problems: xmp autowrite and 1.1 previews

Hi,
after updating to LR2 from 1.4.1 and importing my catalogues i noticed two things that bug me:
1. even though i have "automatically write changes to xmp data" enabled it sometimes happens that when i open a raw file in CS3 bridge or ACR 4.5 the changes made in LR2 are simply not visible unless i choose to update metatdata manually in the appropriate LR2 menu.
2. even though i have selected to discard 1:1 previews after 30 days, sometimes it happens that when i zoom in on a picture that LR2 has definitely generated a 1:1 preview a day before, LR2 insists to generate the 1:1 preview AGAIN, it seems that the preview has not been stored...
Any hints on these problems?
Thank you!

Great to see your offer to help here, thanks!

All .XMP data gets automatically incorporated into DNGs, right? (Newbie question)

Dear Folks,
Just starting on converting my camera raw files to DNG. I've got lots of files I've edited in Bridge and ACR, so there are lots of associated XMP files. I just want to make doubly-sure that I don't have to do anything special to insure all that data gets incorporated into the DNG files that Adobe DNG Converter creates, and that once the conversions are done, I can remove the .xmp's from my hard drive along with the original raw files.(And, yes, everything is backed up and archived.)
Thanks!
Ctein

Dear PE and Jim,
Thanks for the hand-holding.
Yes, I ran an experiment first-thing, where I compared how Photoshop/ACR opened the original raw+xmp files to the derivative DNG files, and it looked like the xmp data got bundled in.
But with a coupla thousand files to convert, I didn't want to discover halfway thru that I'd missed something. Better to ask for definitive opinion.
Now I have it! Much thanks.
BTW, still on CS3 for Bridge/Photoshop, but running latest version of DNG Converter (5.2.0.65) as a stand-alone.
pax / Ctein

Convert CS3 XMP Panels to work with CS4

I have a series of custom XMP panels which we wrote to work with CS3. Now that we are about to migrate the balance of our users to CS4 and shortly everyone to CS5, I see that these panels no longer work. What is the easiest way to migrate these panels.
Thanks in advance,
Morgan

Hi,
we have made an experimental java tool to convert CS3 to CS4/5 panels.
Please find it attached and try it out if you like -- but I can offer no warranty :-)
Note that the approach is limited when it comes to the layout of the panel.
You need to adjust the generated MXML code.
It works as follows:
1. Find your CS3 panel (a txt file) and can call
java -jar EvePanelConverterApp.jar {Eve Input File} {MXML Output File}
The tool converts the panel based on an EVE (ZEVE) definition to an MXML file.
2. Use the XMP FileInfo SDK, create a new panel project using the "Custom Panel Wizard" and stuff the generated MXML file into it.
3. Adjust the design, compile and deploy.
Please let me know, if it worked for you or if you have questions or problems.
-- Stefan

XMP Toolkit compilation error under win32 + recent VC editions

Hi all,
I just downloaded the XMP plugin and tried to compile it under win xp with VC9 (express edition).
I get the following error a few times:
C:\Program Files\Microsoft Visual Studio 9.0\VC\include\stdio.h(358) : error C3163: '_vsnprintf': attributes inconsistent with previous declaration
1> C:\Program Files\Microsoft Visual Studio 9.0\VC\include\stdio.h(350) : see declaration of '_vsnprintf'
I'm not expert of win32 and/or VC environment, but I find quite strange that there is an error in stdio.h.
Maybe some duplicate definition in XMP toolkit? Any hint?
Thanks a lot,
Roberto

Thanks a lot!
Regards,
Roberto
2010/5/6 Joerg Ehrlich <[email protected]>:
Hi Roberto,
>
sorry for the late reply.
Unfortunately the compilation error is due to a certain combination of the VS compiler and the third-party ZLib library used in XMPFiles.
When compiling XMPFiles with the new Visual Studio 2008, certain definitions in the version 1.2.3 of ZLib collide with definitions in the CRT used in VS2008.
The solution is to get the latest version of ZLib which is 1.2.5. But you also need to adjust the XMPFiles VS project a little bit.
In that VS project you need to remove the file "gzio.c" from this folder: XMPFiles/Source Files/Third Party/zlib.
With those two changes, the toolkit should compile.
But you could also wait for the CS5 SDK which is about to be released pretty soon, which has this fixed as well.
>
If you have further questions, please let me know.
Kind Regards
Jörg
Adobe XMP
>

XMP definition in XMP

Similar Messages

Maybe you are looking for