XLIFF data representation in JSON

Hi all,

During the Vancouver FEISGILTT session, one of the topics that came a few times was the need for a JSON representation of the XLIFF
data. (An example use case would be the segment payload in a translation Web service).

At the end of the day, I think there was an action item (can't recall if it was for David or Bryan) to check with OASIS if this was
falling in the purview of the TC or not. Another, maybe simpler, way to approach this is to write a Note (it's akin to a mapping).

Cheers,
-yves