Closed DavidFatDavidF closed 3 years ago
The three possible options are listed below. We agreed that @genivia-inc will implement option 3) by January meeting and we will review then..
That would also allow for having order and xml:lang on target and xml:lang on source. Solves order and xml:lang uniformly and the structure is very closely following XLIFF.
However, we felt that a wrapper is too big a hammer that would kill the elegance of the source and target arrays, where source and target are the heavy lifting elements in XLIFF and JLIFF that are processed the most.
order
object to lead the target array and be unique.Feels hacky
source-xml-lang
target-xml-lang
target-order
structure is different to XLIFF
keeps the source and target arrays elegantly accessible without syntactic sugar
In meeting on 23rd February, we realized that
source-xml-lang
target-xml-lang
target-order
should be introduced on segment as well as ignorable
agree using camelCase instead of hyphenation
sourceXmlLang
targetXmlLang
targetOrder
xmlLang
should be removed from segment
dF to implement in prose
The schema for target doesn't encode a property equivalent to XLIFF @order This has impact on how target is encoded. It seems it cannot be
"target" : [ array ]
because this way it cannot express the order property..I assigned this to the December meeting milestone to make sure that this will be reviewed..