Re: [xliff] ITS scope with sm/em

[Felix Sasaki <felix@sasakiatcf.com>]

I agree with Fredrik. Processing of overlapping hierarchies is a task that cannot be solved in general and discarding non-hierarchical structures is a good strategy for XML / HTML content.


If people don’t want to specify an XSLT conversion we could also define the conversion process in an algorithmic way like this:

0) set current content to whole content to be processed.
1) is there an s tag in current content? 
	Then output text before s tag and do 2)
	else just output all text in current content.
2) has the s tag an e tag with corresponding id? 
	Then create a mrk node
	set the content between s and e to new current content
	do 1)
else discard s and go to 1)  
3) output rest of text 

and say: you can implement this as XSLT (example given) or in different programing languages. That would have the benefit to keep the door open to future non XML, API focsued XLIFF.

- Felix

Am 08.10.2014 um 18:41 schrieb Estreen, Fredrik <Fredrik.Estreen@lionbridge.com>:

> Hi Yves,
> 
>> Hi all,
>> 
>> Looking at the ITS mapping: In many case we put the ITS information on a
>> marker (<mrk> element).
>> 
>> But such element can be represented by <sm/>...<em/> when it's
>> overlapping another element.
>> In that case the normal ITS scope mechanism can't work because it applies to
>> the empty content of <sm/>, not the content between <sm/> and the
>> corresponding <em/>.
>> 
>> We can have provision for this in the XLIFF module. But I'm not sure it's
>> doable in the ITS rules, especially with inheritance when there are nested
>> annotations.
> 
> This is an interesting problem and I doubt it is solvable in a general way without additional steps. It might be solvable when the <sm/> and <em/> is in the same segment, but I doubt it is in the case where they start and end in different segments (ie. different sibling trees).
> 
> One potentially workable solution would be to apply an XSLT transform on the XLIFF that merges all segments in each unit. Discards any non ITS carrying marker (to reduce risk of overlapping markers) and finally normalize the remaining markers to  the <mrk></mrk> spanning form. Since ITS information will likely be coming from and going to an XML source there should not be any overlapping markers at that stage as they would be difficult to represent in the source format. It is not guaranteed but we could declare that ill-formed. ITS global rules could then be evaluated against the transformed version. Admittedly not the most beautiful solution but I think it could work.
> 
>> I vaguely recall that such topic was discussed at some point in the ITS-WG no?
>> Does anyone recall the outcome?
>> 
>> Cheers,
>> -ys
> 
> Regards,
> Fredrik Estreen
> 
> ---------------------------------------------------------------------
> 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
>