[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-omos] XLIFF OM diagrams
Hi,
I think for the abstract model it makes sense to have them in original data – if for JLIFF we decide to linearize as well that is different question. I do believe that this
small complexity is very valuable if you have heavily tagged content. Patrik www.sdl.com
From: xliff-omos@lists.oasis-open.org [mailto:xliff-omos@lists.oasis-open.org]
On Behalf Of Yves Savourel Thanks Lucian. It looks quite good. I have one comment, but it’s not anything fundamental: I’m trying to see which representation is better for the original data of the in-line codes. -
A separate table and dataRef property on each inline code object (like in the diagram) -
Or a data property directly on each inline code object. From a processing viewpoint it seems having the data part of the inline object makes add/delete/update operations easier. But there are also a few advantages with a
separate table. Anyone has opinions on this? Thanks, -yves From: xliff-omos@lists.oasis-open.org [mailto:xliff-omos@lists.oasis-open.org]
On Behalf Of Lucian Podereu Hi,
This message has been scanned for malware by Websense.
www.websense.com Click
here to report this email as spam. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]