View Editor Prefix Doesn't Match XMP Output

[popeo]

Wasn't sure if this was a bug or working as intended but I used the view editor to setup custom fields (FbID and TouchType) initially using the prefix field "fb". I then changed this to "Attrib" and ever since, the XMP output showed a prefix of fb1, something I never set myself. I did get the prefix to read "fb" for some time before we made a change but I'm wondering why this seems to be stuck? Any tips would be hugely appreciated.

This is the setup of the View Editor which then yields the following:

fb1:FbID="764842784121952" fb1:TouchType="1"

[jameslockman]

The prefix is a shorthand used by the XMPLib to provide a quick way to get to a namespace. If you tag a document with a property with specific prefix, the XMPLib will always use that prefix when addressing the document. You can try to remove that tag completely from the document and then re-tag it, but the data will end up in the right place, as defined by the property and the namespace. This might have an impact on a DAM, however, if it is expecting a specific prefix, but if the DAM respects the XMP spec, it won't matter so long as the image is consistent in using one prefix to represent one namespace.

[popeo]

Thanks @jameslockman. To be clear, does this mean an asset tagged for the first time would retain Attrib: as the prefix whereas an asset incorrectly tagged (e.g. fb1) would never be able to drop that? I just want to be clear if this is an issue with the .json file or an issue with the tags in the image.

[jameslockman]

The XMPLib will target the namespace, not the prefix. It uses the prefix to know which namespace to target, so while the form itself uses Attrib, the prefix is irrelevant so long as it is consistent in your document. If you look at the raw XMP (via FileInfo), what does it say for the definition of http://attribution.com/ads/1.0/ ?