Xrefs in .fm files vs. .xml files

Hi all,

We have a doc set that we need to access by remote doc teams in various locales. All Frame documents are currently stored under version control as .xml files. Team A wants to retain the document set entirely in .xml files, open and edit them in Frame, and save them as .xml files.  Team B wants to open the .xml files in Frame as binary .fm files, edit them in Frame, and save to .xml only when needed, i.e. when committed back to our version control system.

It doesn't seem that there is a problem w/ this approach as the content will remain the same and the end result commited back to version control will be .xml.

However, xrefs specifically point to either .fm files or .xml files.  This means that, when Team A works on them in xml and adds an xref to another document in a book, it points to "document1.xml".  When Team B works on them in native Frame, this reference is broken because "document1.xml" does not exist; being instead "document1.fm".

Is there a workaround for this issue?

Thanks for your help,

Shelley

Shelley Hoose

RogueWave Software