Hi all,
I'd like to discuss in the next call how to ensure that at least the most common extension prefixes to XLIFF 2.0 are registered.
I think that Lynx accepts its: but it doesn't accept tbx: that is used in our supposedly valid example files in the test suite.
Looking at our registry,
it is still empty, except for the example prefix.
Since the registry is empty, strictly speaking no extended XLIFF files using fragids to extensions should validate.
Cheers and thanks for your attention
dF
Dr. David Filip
===========
OASIS XLIFF OMOS TC Chair
OASIS XLIFF TC Secretary, Editor, Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122