RE: [xliff] XLIFF data representation in JSON

["chet.ensign" <chet.ensign@oasis-open.org>]

Interesting question. I just looked at your charter. It doesn't specifically rule such a step out of scope nor does it seem to explicitly limit your scope to xml. At least squinting at my cellphone. 

Your deliverables are more explicit on that point though. 

I'll give it another read tonight. It might be worth a conversation about how the scope statement should be interpretred.

/chet

Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------

From: "Schnabel, Bryan S"

Date:12/02/2014 2:59 PM (GMT-05:00)

To: chet.ensign@oasis-open.org

Cc: Yves Savourel , XLIFF Main List

Subject: RE: [xliff] XLIFF data representation in JSON

Hi Chet,

At the latest XLIFF Symposium we had discussion about the need to serialize XLIFF data in a number of transactional  scenarios. And we had a continuation of a conversation started at the previous symposium in Dublin around the XLIFF object model. At this stage of XLIFF's maturity, these topics are quite important as they relate to implementation and application.

Our question is how do these topics fit within the purview of the XLIFF TC given its current charter?

For example, if we wanted to provide a JSON representation of XLIFF data, would that be within our purview? Would it be appropriate to be included in a future version of the XLIFF specification, or perhaps a note? Or perhaps this would be more appropriate to stand on its own, in a sister TC, kind of like the DITA TC and the DITA Adoption TC?

I know you are busy with jury duty at the moment, so we will be happy to receive your advice whenever it is convenient for you.

Thanks,

Bryan

-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Tuesday, December 02, 2014 10:02 AM
To: XLIFF Main List
Subject: [xliff] 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





---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php