> I think the cleaner option is to have no skeleton
> in the XLIFF document :) Just a pointer to it. Or
> even nothing at all (and let the tool work out the
> link using its package/manifest).
I recall this debate a few years ago. I think when the dust settled it was thought that the risk of the XLIFF file (accidentally) getting separated from its external skeleton file justified the internal skeleton option.
I can try to find this in the meeting minutes, or if any remember that debate, please feel free to chime in.
- Bryan
