search

oasis-tcs / xliff-omos-jliff

OASIS XLIFF OMOS TC: JSON serialization of the XLIFF Abstract Object Model
https://github.com/oasis-tcs/xliff-omos-jliff
Other
17 stars 4 forks source link

Long Property Names #51

Open philr-vistatec opened 3 years ago

philr-vistatec commented 3 years ago

I hate to add this given where we are in the process but best before we publish. Could we revisit property names like its_locQualityIssuesArray and consider abbreviating to its_lqiArray and its_locQualityIssueComment to its_lqiComment?

ysavourel commented 3 years ago

+1

DavidFatDavidF commented 2 years ago

I am not sure why the long property names are a problem? Is it a hard limit problem? or just don't feel comfortable around long property names? I don't think u handcode them.. is human readability of JLIFF files the issue u aim to address? I am worried that the short property names would be different compared to XLIFF attribute names and thus cause (another) roundtripping complexity..

philr-vistatec commented 2 years ago

It is primarily aesthetic and secondarily byte size in a heavily annotated document.

DavidFatDavidF commented 2 years ago

To review in November 23 meeting and decide on path ahead..

genivia-inc commented 2 years ago

I agree with @DavidFatDavidF opinion, sharing a concern that shortening the property names will no longer correspond to XLIFF attributes, which may likely increase roundtrip complexity. Changing the property names will require a complete JSON Schema overhaul and extensive JLIFF Spec amendment effort.