Re: its:span and withinText

That's a new use case, and a useful one. The main use case so far was to
have a "span" element if the markup language itself doesn't provide that.
That implied then also to add its:span to the existing schema definitions.

- Felix

2012/9/10 Dave Lewis <dave.lewis@cs.tcd.ie>

> Would I be correct that the main advantage of using its:span is that they
> can be more easily stripped out after the completion of a process that
> inserts ITS markup at a segment level, e.g. translation followed by QA?
>
> This seems an  important use case to me. Otherwise when it comes to
> removing ITS markup that is no longer required, it becomes difficult to
> differentiate spans added by an ITS-aware process from pre-existing spans
> to which ITS attributes were added.
>
> Should there be some mentioned therefore of its use in the spec, say in
> section where the its-span element is defined:
> http://www.w3.org/**International/multilingualweb/**
> lt/drafts/its20/its20.html#**selection-local<http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#selection-local>
>
> cheers,
> Dave
>
>
>
>
>
> On 10/09/2012 08:39, Jirka Kosek wrote:
>
>> On 8.9.2012 18:08, Shaun McCance wrote:
>>
>>  I thought surely this is redundant, that its:span should be
>>> within text by default. Otherwise we basically always have
>>> to add that attribute when we use it for anything else. But
>>> then I couldn't find that anywhere in the ITS spec, and I
>>> realized itstool doesn't currently do that.
>>>
>>> I think its:span should defined to be within text by default.
>>> Thoughts?
>>>
>> Hi Shaun,
>>
>> this seem reasonable. On the other hand it will break backward
>> compatibility. But probably we don't have to care -- I have never seen
>> its:span used except test files? Is anyone using it? Almost all XML
>> formats have their own element similar to span.
>>
>>                                 Jirka
>>
>>
>
>


-- 
Felix Sasaki
DFKI / W3C Fellow