The advantage of using XLIFF <note> is that XLIFF processor will be able to use it even if they don’t support ITS.
Maybe the solution then is to use <note> when the Locnote is not a reference, and use the ITS markup when it is a reference.
-ys
From: garfieldnate [mailto:notifications@github.com]
Sent: Tuesday, October 15, 2013 12:07 PM
To: w3c/its-2.0-testsuite
Cc: ysavourel
Subject: Re: [its-2.0-testsuite] Incorrect ITS in XLIFF files (#2)
Yes, I did notice the mapping note on locNoteRef. Whatever happens, though, I think it will be better to have separate places to put locNote and locNoteRef. Using special text content to differentiate two categories has the risk of hitting a corner case. Someday, someone, somewhere might begin their actual locNote with REF:, and they will be puzzled why it keeps being rendered as a locNoteRef. Or they'll figure it out pretty quickly, and you'll get an email asking how to begin a locNote with REF:.
—
Reply to this email directly or view it on GitHub <https://github.com/w3c/its-2.0-testsuite/issues/2#issuecomment-26358065> . <https://github.com/notifications/beacon/nvs-vse_AjE_52DIkMMQpiz-ed5h4E6Uf1W8aJCPT6srv-oBC5atmPC3SvkpXKVB.gif>