RE: [xliff-users] Storing native data in inline codes

["Rodolfo M. Raya" <rmraya@maxprograms.com>]

On a second thought, data should be stored in the element or in the skeleton. 

The inline element could either be an empty placeholder (with data in the skeleton) or an element with real content, for easy manipulation. An attribute could be added to indicate that the actual data is stored in the skeleton.

Regards,
Rodolfo
--
Rodolfo M. Raya   <rmraya@maxprograms.com>
Maxprograms      http://www.maxprograms.com


> -----Original Message-----
> From: Yves Savourel [mailto:yves@opentag.com]
> Sent: Tuesday, February 22, 2011 7:31 PM
> To: xliff-users@lists.oasis-open.org
> Subject: [xliff-users] Storing native data in inline codes
> 
> Hello folks,
> 
> Over the past few weeks the inline markup sub-committee has been looking
> at ways to improve how to store the original data of inline codes for XLIFF 2.0.
> 
> We came up with a set of options that are illustrated here:
> 
> http://wiki.oasis-
> open.org/xliff/OneContentModel/Comparison#SummaryofthePossibleOptio
> nsforRepresentingNativeData
> 
> We would greatly appreciate feedback from XLIFF producers and consumers
> on those different representations: potential issues, additional suggestions,
> preferences, etc.
> 
> Thanks,
> -yves
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xliff-users-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: xliff-users-help@lists.oasis-open.org